[DO NOT MERGE] [PROTOTYPE] Stabilizing PCR4 Measurements #637
+0
−46
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
github-actions
bot
added
impact:breaking-change
6 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
This is an effort to stabilize PCR4 measurements.
There are a few known issues with PCR4 measurements that need to be addressed.
Applications that originate from a measured FV and are an extension of the BDS environment should not signal ready to boot nor be measured into PCR4.
File paths that do not exist should not be loaded thus should not signal ready to boot nor should they be measured into PCR4.
Applications that originate from a measured FV should not be measured into PCR4
(microsoft/mu_tiano_plus#330)
How This Was Tested
Various Boot Paths
Integration Instructions
TODO