Repository navigation
docs(spec): make the TPM security model vendor-neutral - #440
Merged
Merged
Conversation
Rewrites the framing so the document does not read as directed at one external party. Section 6 becomes open ecosystem questions applying to any TPM vendor and any hosted attestation service, and the device framing generalises to devices without confidential compute. Wording only, no technical claim changes. Also corrects section 4.7, which said the claim-tiering change landed in #437. It did not once #437 was narrowed to the parser fix, so it now reads as proposed and records that it contradicts an existing test assertion. Refs #436, #439 Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
imran-siddique
added
documentation
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
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.
Follow-up to #439. Rewrites the TPM security model document so it is vendor-neutral and does not frame itself around any specific external conversation.
Changes are wording only. No technical claim, priority, or issue reference is altered.
Two accuracy fixes carried in the same commit:
tests/unit/test_tee_providers.pyand ships separately.Note for the record: the merge commit message on #439 also carries the earlier framing. Correcting that would mean rewriting main, which is not worth it; the document itself is what anyone reads.