-
Notifications
You must be signed in to change notification settings - Fork 379
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
tpm2 verifysignature --format is no longer supported #2169
Comments
@osresearch I ran your test and am getting a slightly different output:
tpm2 rc_decode 0x9000b
mu:A parameter has a bad value My tss version is: pkg-config --modversion tss2-esys
3.1.0-dev
$ git describe
3.0.0-16-g76be63d641e0 Is that what you're seeing? If not, whats your tpm2-tss version? |
I'm using tpm2-tss @ 76be63d641e01e7a3fcdb987fedadf98e970ba8b and my initial report had a library skew issue, so it was picking up the wrong version of ESYS/MU/RC. With that fixed it produces the same error as yours. The guide has the policy signature file generated as a raw RSA signature with OpenSSL, not a
It looks like the |
--format was changed to --scheme in e275ba5. However, the option for --format was set to '0' (ASCII 0) in the selector char. However, the case statement was set to 0, thus --format was being silently ignored. Fix this by setting the getopt selector charactar to 0. Fixes: tpm2-software#2169 Signed-off-by: William Roberts <[email protected]>
--format was changed to --scheme in e275ba5. However, the option for --format was set to '0' (ASCII 0) in the selector char. However, the case statement was set to 0, thus --format was being silently ignored. Fix this by setting the getopt selector charactar to 0. Fixes: tpm2-software#2169 Signed-off-by: William Roberts <[email protected]>
--format was changed to --scheme in e275ba5. However, the option for --format was set to '0' (ASCII 0) in the selector char. However, the case statement was set to 0, thus --format was being silently ignored. Fix this by setting the getopt selector charactar to 0. Fixes: #2169 Signed-off-by: William Roberts <[email protected]>
I'm attempting to follow the Intel guide for signing PCRs with an RSA key. However,
tpm2 verifysignature
fails with "the TPM was unable to unmarshall a value because there were not enough octets in the input buffer
".This is using https://github.com/tpm2-software/tpm2-tools/tree/c643ff688834d573772c9cc57fcbdf48a7e7735e and https://github.com/tpm2-software/tpm2-tss/tree/76be63d641e01e7a3fcdb987fedadf98e970ba8b
As a minimal test case:
The text was updated successfully, but these errors were encountered: