From: Joshua Lock <joshua.g.lock at linux.intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tools 3.1.2 release candidate
Date: Tue, 14 Aug 2018 23:19:13 +0100 [thread overview]
Message-ID: <2338d010c774aedbf9de6fab5222a3f3a43965ba.camel@linux.intel.com> (raw)
In-Reply-To: 773b2ba7-4b6e-b1d7-8d17-ffa955aacaa4@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Mon, 2018-08-13 at 13:20 +0200, Javier Martinez Canillas wrote:
> Hi Joshua,
>
> On 08/01/2018 12:09 PM, Joshua Lock wrote:
> > On 16/07/2018 21:22, Joshua Lock wrote:
> > > Hello all,
> > >
> > > I've just tagged and signed rc0 for tpm2-tools 3.1.2:
> > >
https://github.com/tpm2-software/tpm2-tools/releases/tag/3.1.2-rc0
> > >
> > >
> > > Javier noticed that we had a behavioural change in 3.1 (compared
> > > to 3.0)
> > > that was inappropriate for a minor version bump, that is we were
> > > using
> > > user supplied object attributes exclusively (instead of ORing
> > > them with
> > > the defaults). 3.1.2 reverts the change:
> > >
> > >
https://github.com/tpm2-software/tpm2-tools/commit/352908f7470338aba858a9ac20c1c5ec608b661c
> > >
> >
> > I just tagged 3.1.2-rc1 to include an additional fix from Javier to
> > use
> > better object attribute defaults in tpm2_create:
> >
> > https://github.com/tpm2-software/tpm2-tools/releases/tag/3.1.2-rc1
> >
>
> I think is time to cut a final 3.1.2 release?
Absolutely, I'm working on it now. Apologies for the delay, I was away
on leave.
Joshua
next reply other threads:[~2018-08-14 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 22:19 Joshua Lock [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-13 11:20 [tpm2] tpm2-tools 3.1.2 release candidate Javier Martinez Canillas
2018-08-01 10:09 Joshua Lock
2018-07-16 20:22 Joshua Lock
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=2338d010c774aedbf9de6fab5222a3f3a43965ba.camel@linux.intel.com \
--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