From: Petr Gotthard <petr.gotthard@centrum.cz>
To: <tpm2@lists.linux.dev>
Subject: [RELEASE CANDIDATE] tpm2-openssl 1.3.1-rc1
Date: Mon, 27 Apr 2026 00:27:58 +0200 [thread overview]
Message-ID: <20260427002758.28B63070@centrum.cz> (raw)
In-Reply-To: <20260419155640.BD3BD5A6@centrum.cz>
Hello,
we had to release tpm2-openssl 1.3.1-rc1: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.3.1-rc1
This includes two new fixes:
- Fixed parent handle issues with signed representation in the TSS2 PRIVATE KEY files (thanks to @thomkopp).
- Fixed memory and handle leaks (thanks to @hyperfinitism).
Kind Regards,
Petr
______________________________________________________________
> Od: "Petr Gotthard" <petr.gotthard@centrum.cz>
> Komu: tpm2@lists.linux.dev
> Datum: 19.04.2026 15:56
> Předmět: [RELEASE CANDIDATE] tpm2-openssl 1.3.1-rc0
>
>Hello,
>
>I would like to announce the release of tpm2-openssl 1.3.1-rc0: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.3.1-rc0
>
>This is a bugfix release:
> - Fixed compatibility with OpenSSL 4.0.
> - Fixed the ECDSA signature algorithm to omit the parameters field (thanks to @smhmeier).
> - Fixed cipher padding validation according to PKCS#5/PKCS#7, so zero padding is now rejected (thanks to @hyperfinitism).
> - Fixed buffer indexing for block ciphers without padding (thanks to @hyperfinitism).
> - Fixed cleansing of sensitive data upon buffer deallocation and fixed buffer allocator consistency (thanks to @hyperfinitism).
> - Fixed missing NULL checks and harmless type cast errors in RSA and ECDSA algorithms (thanks to @hyperfinitism).
> - Fixed semaphore destruction (thanks to @Deadolus).
>
>
>Kind Regards,
>Petr
>
>
prev parent reply other threads:[~2026-04-26 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 21:36 [RELEASE CANDIDATE] tpm2-openssl 1.3.0-rc0 Petr Gotthard
2026-04-19 13:56 ` [RELEASE CANDIDATE] tpm2-openssl 1.3.1-rc0 Petr Gotthard
2026-04-26 22:27 ` Petr Gotthard [this message]
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=20260427002758.28B63070@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