Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tpm attestation fields clarification #791

Merged
merged 4 commits into from
Feb 9, 2018
Merged

Tpm attestation fields clarification #791

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
45caac2
Tpm attestation fields clarifications
Feb 8, 2018
cdf234d
added reference to the Standard Attestation Structure table as it is …
rlin1 Feb 8, 2018
d1e2d1a
added reference for TPMS_CERTIFY_INFO
Feb 8, 2018
1f51afe
NitBit: Incorporate comments from Alex, Mike
Feb 9, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3200,9 +3200,13 @@ engine.
- Verify that `magic` is set to `TPM_GENERATED_VALUE`.
- Verify that `type` is set to `TPM_ST_ATTEST_CERTIFY`.
- Verify that `extraData` is set to the hash of |attToBeSigned| using the hash algorithm employed in "alg".
- Verify that `attested` contains a `TPMS_CERTIFY_INFO` structure, whose `name` field contains a valid Name for |pubArea|,
- Verify that `attested` contains a `TPMS_CERTIFY_INFO` structure as specified in [[TPMv2-Part2]] section 10.12.3,
whose `name` field contains a valid Name for |pubArea|,
as computed using the algorithm in the `nameAlg` field of |pubArea| using the procedure specified in [[TPMv2-Part1]]
section 16.
- Note that the remaining fields in the "Standard Attestation Structure" [[TPMv2-Part1]]
section 31.2, i.e., `qualifiedSigner`, `clockInfo` and `firmwareVersion` are ignored.
These fields MAY be used as an input to risk engines.

If |x5c| is present, this indicates that the attestation type is not [=ECDAA=]. In this case:
- Verify the |sig| is a valid signature over |certInfo| using the attestation public key in |x5c| with the
Expand Down