From: Petr Gotthard <petr.gotthard at centrum.cz>
To: tpm2@lists.01.org
Subject: [tpm2] [RELEASE CANDIDATE] tpm2-openssl 1.1.1-rc0
Date: Fri, 23 Sep 2022 15:12:48 +0200 [thread overview]
Message-ID: <20220923151248.7F2585CC@centrum.cz> (raw)
In-Reply-To: 20220114161914.F16B8401@centrum.cz
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hello,
I made a tpm2-openssl 1.1.1-rc0: https://github.com/tpm2-software/tpm2-openssl/releases/tag/1.1.1-rc0
This is bugfix release that provides:
- Support for older TPM chips that do not support the CreateLoaded operation.
- Loading of NV index objects larger than TPM2_PT_NV_BUFFER_MAX.
- Loading of PEM certificates from the NV index.
- Support for the 'openssl cms' command for RSA keys.
- Building of tpm2-openssl on Windows (thanks to @mhummels).
- Ability to run autoreconf on the release tarball.
Kind Regards,
Petr
reply other threads:[~2022-09-23 13:12 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=20220923151248.7F2585CC@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