Repository navigation
Mirror production PCR approval for the reviewed Maple backend - #365
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Mirror the production PCR approval from Maple #1049, exact signed source
db19d8447318d47bd0761978df7fbb5ff4d45c36, so installed clients using the legacy history URL can trust the same approved production EIF.The native PCR compatibility helper verified all signatures, snapshot membership, and preservation of every existing history entry against legacy baseline
bba0abbb70aa137fc696f50f8c506808622f96c6. OnlypcrProd.jsonandpcrProdHistory.jsonchange; DEV files remain byte-identical. Production history grows from154 to155 approvals, and DEV remains157.PCR0:
1d73b62ac52780efb61b9f889f53dbe9b45609bb0cc11d10fcb09339ad06dbfd43a9a49667aacab2ea3cebdf0e51ab10This publishes compatibility metadata only; it does not deploy or change signing keys.