public inbox for tpm2@lists.linux.dev
 help / color / mirror / Atom feed
From: Painololo at protonmail.com
To: tpm2@lists.01.org
Subject: [tpm2] Re: [RELEASE CANDIDATE] tpm2-pytss 1.1.0-rc0
Date: Fri, 03 Jun 2022 13:41:37 +0000	[thread overview]
Message-ID: <20220603134137.2010.86100@ml01.vlan13.01.org> (raw)
In-Reply-To: SN6PR11MB3437B000343FD4944FDDA4DAB80F9@SN6PR11MB3437.namprd11.prod.outlook.com

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

> Hello,
> 
> I would like to announce the release of tpm2-pytss version 1.1.0-rc0 which can be found on
> pypi at:
>   - https://pypi.org/project/tpm2-pytss/1.1.0rc0/
> 
> With the following CHANGELOG:
> ## 1.1.0-rc0 - 2022-03-14
> ### Fixed
> - Spelling of "Enhanced" in CHANGELOG for 1.0.0 release.
> - Ensure that TPM2_GENERATED.VALUE is encoded the same way as other constants.
> - Add support to unmarshal simple TPM2B types (such as TPM2B_ATTEST and TPM2B_NAME)
> directly using the 
>   unmarshal method
> 
> ### Changed
> - Drop pkgconfig from runtime dependencies, thus no longer need dev packages of built
> bindings at runtime.
>   - NOTE: Version information is cached, a change in the TSS libraries requires a rebuild
> of the bindings.
> 
> ### Added
> - Support session contexts from tpm2-tools as well as function to marshal context to
> tpm2-tools format.
> - Support two new encoding/decoding classes to go to/from hex or json representation of
> objects.
> - Support for creating EK from templates and optionally NV index based templates.
> - Binding to `Esys_TR_GetTpmHandle` as `ESAPI` method `tr_get_tpm_handle`.
> 
> Thanks,
> Bill
Thank you very much, it helped.

             reply	other threads:[~2022-06-03 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 13:41 Painololo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 13:44 [tpm2] Re: [RELEASE CANDIDATE] tpm2-pytss 1.1.0-rc0 painololo
2022-06-01 10:39 dsnou849

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=20220603134137.2010.86100@ml01.vlan13.01.org \
    --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