-
Notifications
You must be signed in to change notification settings - Fork 381
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
Add to tpm2_certify #3415
Comments
This is currently "hard coded" within the tools. The qualifyingData may be used by some applications for anti-reply. Add a parameter to input data. If parameter is not provided continue to use the existing "hard coded" value. |
Which exact tool are you referring to ? |
Oops, I "fat fingered" the issue title. Just changed the title (my finger must have slipped off). This applies to tpm2_certify. |
Rationale: While Certify may not need a nonce (freshness not really needed) there are some cases where the same set of RP's may share an Attestation Key. This would provide unique evidence for each RP. |
No description provided.
The text was updated successfully, but these errors were encountered: