From: Petr Gotthard <petr.gotthard@centrum.cz>
To: tpm2@lists.linuxfoundation.org
Subject: [Tpm2] [RELEASE CANDIDATE] tpm2-openssl 1.2.0-rc1
Date: Wed, 03 May 2023 13:43:18 +0200 [thread overview]
Message-ID: <20230503134318.423136D0@centrum.cz> (raw)
In-Reply-To: <20230304111257.FBBD1E80@centrum.cz>
Hello,
I would like to announce the release of tpm2-openssl 1.2.0-rc1: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.2.0-rc1
This fixes some warnings displayed when building on Fedora Linux and improves tests to work also on FC38.
Petr
______________________________________________________________
> Komu: "tpm2@lists.linuxfoundation.org" <tpm2@lists.linuxfoundation.org>
> Datum: 04.03.2023 11:20
> Předmět: [Tpm2] [RELEASE CANDIDATE] tpm2-openssl 1.2.0-rc0
>
>Hello,
>
>I would like to announce the release of tpm2-openssl 1.2.0-rc0: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.2.0-rc0
>
>
>Added
>- Added support for ECDH with a KDF, which is used by ECC-based CMS (S/MIME).
>
>Changed
>- Symmetric operations are disabled by default. In most situations these are not needed and cause a huge performance penalty.
> To enable configure with `--enable-op-digest` or `--enable-op-cipher`.
>
>Removed
>- Removed unofficial support for tpm2-tss < 3.2.0, which do not support the openssl 3.x.
>
>Fixed
>- Fixed OSSL_FUNC_KEYMGMT_HAS operations with NULL keys
>- Modified documentation: the user-space resource manager (abrmd) is almost mandatory for complex scenarios such as SSL or X.509 operations.
>
>
>Kind Regards,
>Petr
next parent reply other threads:[~2023-05-03 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230304111257.FBBD1E80@centrum.cz>
2023-05-03 11:43 ` Petr Gotthard [this message]
2023-10-07 20:36 ` [Tpm2] [RELEASE CANDIDATE] tpm2-openssl 1.2.0-rc2 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=20230503134318.423136D0@centrum.cz \
--to=petr.gotthard@centrum.cz \
--cc=tpm2@lists.linuxfoundation.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