docs(spec): the NV certify half of #432 has landed - #483
Merged
Conversation
Sections 4.3 and 7 still said the gateway measurement was an unsigned NV read and that TPM2_NV_Certify was the open half of #432, while section 5 in the same document said P2 is implemented. The document contradicted itself, and the two stale passages are the ones a reader reaches first. Both halves are closed and hardware-validated on an Azure Trusted Launch vTPM on 2026-08-01. Section 4.3 now describes the bracketing certify pair and the stateless post == H(pre || digest) check, section 7's row three names the pair, and the caveat under it is rewritten to the limit that actually remains: the appraisal proves what was extended, not that it was known-good, absent an expected value from the relying party. Host-dependent key provenance is unchanged and still stated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Sections 4.3 and 7 of the TPM security model still said the gateway measurement was an unsigned NV read and that
TPM2_NV_Certifywas the open half of #432, while section 5 of the same document said P2 is implemented. The document contradicted itself, and the two stale passages are the ones a reader reaches first.Both halves are closed and hardware-validated on an Azure Trusted Launch vTPM on 2026-08-01 (#459, #461), a run that found two defects in already-merged code.
post == H(pre || expected_gateway_digest)check, and points at P2 for why one certify is not enough.Host-dependent key provenance on Azure is unchanged and still stated in both places.
Docs only, no code or behaviour change.
🤖 Generated with Claude Code