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.

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

Open
mwiseman-byid opened this issue Jul 21, 2024 · 4 comments
Open

Add to tpm2_certify #3415

mwiseman-byid opened this issue Jul 21, 2024 · 4 comments

Comments

@mwiseman-byid
Copy link

No description provided.

@mwiseman-byid
Copy link
Author

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.

@AndreasFuchsTPM
Copy link
Member

Which exact tool are you referring to ?
tpm2_quote has -q, --qualification=HEX_STRING_OR_PATH

@mwiseman-byid mwiseman-byid changed the title Add to tpm2_ Add to tpm2_certify Jul 25, 2024
@mwiseman-byid
Copy link
Author

mwiseman-byid commented Jul 25, 2024

Oops, I "fat fingered" the issue title. Just changed the title (my finger must have slipped off). This applies to tpm2_certify.

@mwiseman-byid
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants