Skip to content

Conversation

@THS-on
Copy link
Member

@THS-on THS-on commented Dec 7, 2022

The main function also had a local variable called uuid. This variable
contained either the provided uuid or when "hash_ek" was set the sha256 hash
of the EK. We never updated the KeylimeConfig struct which caused a mismatch
between uuids used in the program. Instead we now mutate the KeylimeConfig
when "hash_ek" is set to the correct value.

@kkaarreell
Copy link
Contributor

I have tried to implement reproducer for this issue in keylime-tests but my test scenario is failing even with this fix.
RedHat-SP-Security/keylime-tests#272

@THS-on
Copy link
Member Author

THS-on commented Dec 9, 2022

The issue was with the reproducer and not the fix, if I see that correctly.

@kkaarreell
Copy link
Contributor

I have tried to implement reproducer for this issue in keylime-tests but my test scenario is failing even with this fix. RedHat-SP-Security/keylime-tests#272

Yes, false alarm. I am sorry for that

The main function also had a local variable called uuid. This variable
contained either the provided uuid or when "hash_ek" was set the sha256 hash
of the EK. We never updated the KeylimeConfig struct which caused a mismatch
between uuids used in the program. Instead we now mutate the KeylimeConfig
when "hash_ek" is set to the correct value.

Signed-off-by: Thore Sommer <mail@thson.de>
@ansasaki ansasaki merged commit e80c67a into keylime:master Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants