From: Petr Gotthard <petr.gotthard@centrum.cz>
To: <tpm2@lists.linux.dev>
Subject: [RELEASE] tpm2-openssl 1.3.0
Date: Sat, 25 Jan 2025 19:30:07 +0100 [thread overview]
Message-ID: <20250125193007.8AA5669C@centrum.cz> (raw)
Hello,
I would like to announce the final release of tpm2-openssl 1.3.0: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.3.0
This is a feature release with few new functions, but most notably it should work in multi-thread and multi-process applications.
Added
- Added support for RSA-OAEP decryption.
- Added 'xof' and 'algid-absent' parameters to digests.
- Added Parent to textual information printed by 'openssl pkey -text'.
Fixed
- Fixed multi-threaded operation, preventing the 'Esys called in bad sequence' errors (thanks to @Danigaralfo, @famez, and @AndreasFuchsTPM).
- Fixed retrieval of OSSL_PKEY_PARAM_MAX_SIZE for RSA keys. The exact value is returned instead of a fixed TPM2_MAX_RSA_KEY_BYTES.
- Fixed handling of absent emptyAuth value in the TSS2 PRIVATE KEY file.
- Set authorization value of newly generated keys. This allows users of the C API to direcly use just generated EVP_PKEY.
Kind Regards,
Petr
reply other threads:[~2025-01-25 18:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250125193007.8AA5669C@centrum.cz \
--to=petr.gotthard@centrum.cz \
--cc=tpm2@lists.linux.dev \
/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