6:54 p.m.
Release 2.1.0 is available at: https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
v2.1.0 - 2017-7-24
* Fix readx and writex on multiple EINTR returns.
* Add support for the tabrmd TCTI. This is the new default.
* Change default socket port from 2323 (the old resourcemgr) to 2321 (default
simulator port).
* Cherry-pick fix for CVE-2017-7524.
* Fix tpm2_listpcr command line option handling.
* Fix tpm2_getmanufec memory issues.
11:04 a.m.
Hello folks,
On 07/24/2017 07:54 PM, Roberts, William C wrote:
Release 2.1.0 is available at:
https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
v2.1.0 - 2017-7-24
I've some questions about the release process that were not answered by reading
the RELEASE document in the repository (it would be nice to add the answers for
these in the doc as well).
1- What's the expected time after a release for the next branch to be created?
2- What's the expected time after a branch is created for a -rc to be released?
I'm asking because there is a bunch of new stuff and fixes currently in master,
so it would be nice to start thinking on the next release:
$ git lg 2.1.0..master | wc -l
221
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
3:43 p.m.
On 08/02/2017 12:04 PM, Javier Martinez Canillas wrote:
Hello folks,
On 07/24/2017 07:54 PM, Roberts, William C wrote:
> Release 2.1.0 is available at:
https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
>
> v2.1.0 - 2017-7-24
I've some questions about the release process that were not answered by reading
the RELEASE document in the repository (it would be nice to add the answers for
these in the doc as well).
1- What's the expected time after a release for the next branch to be created?
2- What's the expected time after a branch is created for a -rc to be released?
I'm asking because there is a bunch of new stuff and fixes currently in master,
so it would be nice to start thinking on the next release:
$ git lg 2.1.0..master | wc -l
221
Any comments on this?
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
8:38 p.m.
-----Original Message-----
From: Javier Martinez Canillas [mailto:javierm@redhat.com]
Sent: Thursday, August 10, 2017 7:43 AM
To: Roberts, William C <william.c.roberts(a)intel.com>; 'tpm2(a)lists.01.org'
<tpm2(a)lists.01.org>
Cc: Desai, Imran <imran.desai(a)intel.com>; Tricca, Philip B
<philip.b.tricca(a)intel.com>
Subject: Re: tpm2.0-tools: Release 2.1.0 is available
On 08/02/2017 12:04 PM, Javier Martinez Canillas wrote:
> Hello folks,
>
> On 07/24/2017 07:54 PM, Roberts, William C wrote:
>> Release 2.1.0 is available at:
>> https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
>>
>> v2.1.0 - 2017-7-24
>
> I've some questions about the release process that were not answered
> by reading the RELEASE document in the repository (it would be nice to
> add the answers for these in the doc as well).
>
> 1- What's the expected time after a release for the next branch to be created?
I want to use milestones to track releases, next 3.0 will be on:
https://github.com/01org/tpm2-tools/milestone/4
It's currently called next, but considering its not "api compatible" with
2.X, it
will get another major bump, per semantic versioning guidelines.
When we get ready for release, the project will branch off of master and
I'll cut an rc, if an rc sits with no changes, complaints or moans for a week,
then it will be cut as a release.
I'll send an email to the mailing list highlighting this activity so folks can prod
and poke
RCs and provide feedback.
> 2- What's the expected time after a branch is created for a
-rc to be released?
1 week, ill start with rc0 as soon as the branch is created.
>
> I'm asking because there is a bunch of new stuff and fixes currently
> in master, so it would be nice to start thinking on the next release:
>
> $ git lg 2.1.0..master | wc -l
> 221
>
Any comments on this?
Sorry I missed this, somehow. 3.0 is tentatively scheduled in Sept/Oct, but I want to
Coordinate this with the next version of tss, so I can pull in any of the API
incompatible
changes. So I am actually going to block the next major release of tools on tss based on
my understanding with Phillip.
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement Red Hat
10:45 a.m.
Hello Bill,
On 08/14/2017 09:38 PM, Roberts, William C wrote:
> -----Original Message-----
> From: Javier Martinez Canillas [mailto:javierm@redhat.com]
> Sent: Thursday, August 10, 2017 7:43 AM
> To: Roberts, William C <william.c.roberts(a)intel.com>;
'tpm2(a)lists.01.org'
> <tpm2(a)lists.01.org>
> Cc: Desai, Imran <imran.desai(a)intel.com>; Tricca, Philip B
> <philip.b.tricca(a)intel.com>
> Subject: Re: tpm2.0-tools: Release 2.1.0 is available
>
> On 08/02/2017 12:04 PM, Javier Martinez Canillas wrote:
>> Hello folks,
>>
>> On 07/24/2017 07:54 PM, Roberts, William C wrote:
>>> Release 2.1.0 is available at:
>>> https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
>>>
>>> v2.1.0 - 2017-7-24
>>
>> I've some questions about the release process that were not answered
>> by reading the RELEASE document in the repository (it would be nice to
>> add the answers for these in the doc as well).
>>
>> 1- What's the expected time after a release for the next branch to be
created?
I want to use milestones to track releases, next 3.0 will be on:
https://github.com/01org/tpm2-tools/milestone/4
It's currently called next, but considering its not "api compatible" with
2.X, it
will get another major bump, per semantic versioning guidelines.
When we get ready for release, the project will branch off of master and
I'll cut an rc, if an rc sits with no changes, complaints or moans for a week,
then it will be cut as a release.
I'll send an email to the mailing list highlighting this activity so folks can prod
and poke
RCs and provide feedback.
>> 2- What's the expected time after a branch is created for a -rc to be
released?
1 week, ill start with rc0 as soon as the branch is created.
>>
>> I'm asking because there is a bunch of new stuff and fixes currently
>> in master, so it would be nice to start thinking on the next release:
>>
>> $ git lg 2.1.0..master | wc -l
>> 221
>>
>
> Any comments on this?
Sorry I missed this, somehow. 3.0 is tentatively scheduled in Sept/Oct, but I want to
Coordinate this with the next version of tss, so I can pull in any of the API
incompatible
changes. So I am actually going to block the next major release of tools on tss based on
my understanding with Phillip.
Ok, thanks a lot for the answers.
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
12:26 p.m.
Hello Bill and Philip,
On 08/16/2017 11:45 AM, fmartine(a)redhat.com wrote:
On 08/14/2017 09:38 PM, Roberts, William C wrote:
[snip]
>>>
>>> I'm asking because there is a bunch of new stuff and fixes currently
>>> in master, so it would be nice to start thinking on the next release:
>>>
>>> $ git lg 2.1.0..master | wc -l
>>> 221
>>>
>>
>> Any comments on this?
>
> Sorry I missed this, somehow. 3.0 is tentatively scheduled in Sept/Oct, but I want
to
> Coordinate this with the next version of tss, so I can pull in any of the API
incompatible
> changes. So I am actually going to block the next major release of tools on tss based
on
> my understanding with Phillip.
>
Do you have a better idea about when the next tpm2-tss and tpm2-tools releases
may happen? The reason why of the nagging, is because as mentioned I have a PR
for the Clevis project [0] that is using the latest stuff from tpm2-tools next.
But the problem is that we can't merge it until there's a release of tpm2-tools
that contains those changes.
[0]: https://github.com/latchset/clevis/pull/17
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
11:28 p.m.
On Fri, 2017-09-22 at 13:26 +0200, Javier Martinez Canillas wrote:
Hello Bill and Philip,
On 08/16/2017 11:45 AM, fmartine(a)redhat.com wrote:
> On 08/14/2017 09:38 PM, Roberts, William C wrote:
[snip]
> > > >
> > > > I'm asking because there is a bunch of new stuff and fixes
> > > > currently
> > > > in master, so it would be nice to start thinking on the next
> > > > release:
> > > >
> > > > $ git lg 2.1.0..master | wc -l
> > > > 221
> > > >
> > >
> > > Any comments on this?
> >
> > Sorry I missed this, somehow. 3.0 is tentatively scheduled in
> > Sept/Oct, but I want to
> > Coordinate this with the next version of tss, so I can pull in
> > any of the API incompatible
> > changes. So I am actually going to block the next major release
> > of tools on tss based on
> > my understanding with Phillip.
> >
Do you have a better idea about when the next tpm2-tss and tpm2-tools
releases
may happen? The reason why of the nagging, is because as mentioned I
have a PR
for the Clevis project [0] that is using the latest stuff from tpm2-
tools next.
I had a chance to talk to some of the RedHat folks about Clevis @ the
plumbers conference earlier this month. Interesting & exciting stuff.
The next release of the tools doesn't depend on a new release of the
TSS libraries so that should be off the critical path. The tools
release is however blocked on a bug in the tabrmd. This is my next work
item.
But the problem is that we can't merge it until there's a
release of
tpm2-tools
that contains those changes.
With the tools blocked on the tabrmd we'll be doing a release of the
two in tandem. I'm expecing that the work I've signed up for there to
be on the order of "a few weeks". So while I'm always hesitant to state
release goals publicly I think this can be ready for a release toward
the end of October. Can't make any guarantees but that's our goal.
Best,
Philip
[0]: https://github.com/latchset/clevis/pull/17
Best regards,
9:09 p.m.
On 09/26/2017 12:28 AM, Philip Tricca wrote:
On Fri, 2017-09-22 at 13:26 +0200, Javier Martinez Canillas wrote:
> On 08/16/2017 11:45 AM, fmartine(a)redhat.com wrote:
>> On 08/14/2017 09:38 PM, Roberts, William C wrote:
[snip]
> Do you have a better idea about when the next tpm2-tss and
tpm2-tools
> releases
> may happen? The reason why of the nagging, is because as mentioned I
> have a PR
> for the Clevis project [0] that is using the latest stuff from tpm2-
> tools next.
I had a chance to talk to some of the RedHat folks about Clevis @ the
plumbers conference earlier this month. Interesting & exciting stuff.
Cool, someone also mentioned talking with you about TPM stuff (Peter or
Nathaniel I believe).
The next release of the tools doesn't depend on a new release of
the
TSS libraries so that should be off the critical path. The tools
I don't think that's true. At least when I try to build tpm2-tools master
with tpm2-tss 1.2.0, I get the following build errors:
https://pastebin.com/raw/6V4HBQPh
But it does build with tpm2-tss master of course. I haven't dig deeper to
see if the changes that break the build could be cherry-picked to the 1.X
branch though.
release is however blocked on a bug in the tabrmd. This is my next
work
item.
Yes, I've been following the discussion but had remained silent lately
because I need to re-read/study the context management part of the specs
to better understand what the problem is and the suggested solutions.
> But the problem is that we can't merge it until there's a
release of
> tpm2-tools
> that contains those changes.
With the tools blocked on the tabrmd we'll be doing a release of the
two in tandem. I'm expecing that the work I've signed up for there to
be on the order of "a few weeks". So while I'm always hesitant to state
release goals publicly I think this can be ready for a release toward
the end of October. Can't make any guarantees but that's our goal.
Another problem is what would happen when the kernel resource manager is used,
since AFAIK there's no agreement yet on what the tools should do in that case.
Best,
Philip
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
1736
days inactive
1800
days old
7 comments
3 participants
participants (3)
-
Javier Martinez Canillas -
Philip Tricca -
Roberts, William C