Draft
Conversation
…t-dirty, the rest of the version still has to match
…me from a TPM do not Err out This gets certify.rs some steps further: it then runs into an authorization error
…interactions with swtpm
mcr
force-pushed
the
certify-multiple
branch
from
0202201 to
5cea35b
Compare
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
1 participant
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.
With some questionable changes to ek.rs, it is now possible to run the certify example with RSA-2048 and
ECDSA P384 algorithms, but the P256 ones still do not work.
Deep reading of TPM Family 2.0; Level 0 Version 2.6 December 4, 2024, has not yet revealed what is going on.
Using AUTHPOLICY_A_SHA256 works by using PolicyA as the "OR" part for PolicyB, but that ought to work for P256 as well.
Unless some of the template is wrong.
The "certify" example now takes an argument:
0 - RSAS-2048
1 - ECDSA P384
2 - ECDSA P256