-
Notifications
You must be signed in to change notification settings - Fork 61
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.
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
Verify TPM attestation certificate trustworthiness #253
Verify TPM attestation certificate trustworthiness #253
Conversation
2d1dc41
to
5f64d45
Compare
…e for known manufacturer Found via https://github.com/abergs/fido2-net-lib/blob/b44db521ee487f7d29b2de34f8c6b57f1bc9700e/Src/Fido2/AttestationFormat/Tpm.cs#L506-L540 https://www.trustedcomputinggroup.org/wp-content/uploads/Credential_Profile_EK_V2.0_R14_published.pdf specifies how and what exactly must be encoded.
…icate trustworthiness Hat-tip to Alex Seigler for pointing me to https://docs.microsoft.com/en-us/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-install-trusted-tpm-root-certificates Downloaded version of TrustedTpm.cab has "22-May-2019" as last changelog entry.
5f64d45
to
13ed764
Compare
For the record, this branch doesn't pass the tpm FIDO tests because of the extra verification. I guess it we'll need the |
Given this is part of #66 we are planning to merge into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
Need to look at the test failures before merging.
Similar in spirit to #208 but the MDS does not have any TPM root certificates last time I checked, so we'll need to bring our own.
Huge thanks to the maintainers of the .NET library that pointed me in the right direction 🙌
See commit messages for more details.