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: Wed, 27 Apr 2022 19:37:32 +0200 [thread overview]
Message-ID: <20220427193732.704789D2@centrum.cz> (raw)
In-Reply-To: DS7PR03MB557663142DFF081829F097179AFA9@ds7pr03mb5576.namprd03.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
>CMS encryption fails as follows:
>
>$ openssl cms -encrypt -provider tpm2 -provider base -in file.txt -recip handle:0x01000013
>WARNING:esys:src/tss2-esys/api/Esys_CreateLoaded.c:368:Esys_CreateLoaded_Finish() Received TPM Error
>ERROR:esys:src/tss2-esys/api/Esys_CreateLoaded.c:129:Esys_CreateLoaded() Esys Finish ErrorCode (0x000b0143)
>40FCFCC0017F0000:error:4000000B:tpm2::cannot create key::-1:721219 rmt:error(2.0): command code not supported
>
>This looks like https://github.com/tpm2-software/tpm2-openssl/issues/29.
> For my use case, support for TPMs without the CreateLoaded command will be essential. My machines have an OPTIGA TPM2.
The CreateLoaded issue should be fixed now (in the latest master branch).
Petr
next reply other threads:[~2022-04-27 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:37 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 15:20 Sievert, James
2022-04-27 14:46 Petr Gotthard
2022-04-26 21:54 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=20220427193732.704789D2@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