shim: ensure vendor_db gets logged into db
#717
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
README.tpm claims that `vendor_db` is logged into `db`, however the actual measurement was done towards `vendor_db` with the `check_db_hash_in_ram` function. This causes some unexpected issues like in keylime/keylime#1725 Signed-off-by: Morten Linderud <morten@linderud.pw>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
README.tpm claims that
vendor_dbis logged intodb, however the actual measurement was done towardsvendor_dbwith thecheck_db_hash_in_ramfunction.This causes some unexpected issues like in keylime/keylime#1725