From: Petr Gotthard <petr.gotthard at centrum.cz>
To: tpm2@lists.01.org
Subject: [tpm2] Re: {External} Re: OpenSSL 3 and tpm2 provider... / openssl cms
Date: Tue, 26 Apr 2022 23:54:40 +0200 [thread overview]
Message-ID: <20220426235440.9B2351AF@centrum.cz> (raw)
In-Reply-To: DS7PR03MB5576A61EBF01CE46694CE3B79AFB9@ds7pr03mb5576.namprd03.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
>> Debugging openssl is tricky when it fails without any error message
>
>Sorry about that. ☹
No problem. I am glad you are trying the tpm2 provider in your environment. :-)
>> If you create e.g. a RSA-PSS key restricted to a specific hash-algorithm you shouldn't need this extra argument
>
>I was under the impression that the key was created using the sha256 hashing algorithm. Here's the command used for creating the key:
>
>tpm2_create -C /run/user/201/platform.ctx -G ecc256:ecdsa-sha256 -r /run/user/201/private -u /run/user/201/public -a 'fixedtpm|fixedparent|sensitivedataorigin|sign|userwithauth|noda'
>
>Here's the result:
>
>$ tpm2_readpublic -c 0x81800002
>scheme:
> value: ecdsa
> raw: 0x18
>scheme-halg:
> value: sha256
> raw: 0xb
Yeah. What I wrote was apparently true for RSA keys only. The EC keys do not correctly supply the hash algorithm. That is a bug that will be fixed in the coming days: https://github.com/tpm2-software/tpm2-openssl/issues/34
Petr
next reply other threads:[~2022-04-26 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:54 Petr Gotthard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-28 17:39 [tpm2] Re: {External} Re: OpenSSL 3 and tpm2 provider... / openssl cms Petr Gotthard
2022-04-28 16:33 Sievert, James
2022-04-28 16:26 Petr Gotthard
2022-04-28 15:46 Sievert, James
2022-04-28 15:10 Petr Gotthard
2022-04-28 15:07 Sievert, James
2022-04-28 14:42 Sievert, James
2022-04-27 17:37 Petr Gotthard
2022-04-27 15:20 Sievert, James
2022-04-27 14:46 Petr Gotthard
2022-04-26 21:43 Sievert, James
2022-04-26 20:22 Petr Gotthard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220426235440.9B2351AF@centrum.cz \
--to=tpm2@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox