TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tss 1.3.0-rc0 available
Date: Thu, 07 Dec 2017 18:45:13 +0100	[thread overview]
Message-ID: <1512668713.5979.157.camel@intel.com> (raw)
In-Reply-To: 0dc5a8e2-eeb8-1975-a90c-227393562696@twobit.us

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

On Wed, 2017-12-06 at 08:50 -0800, Philip Tricca wrote:
> There's now an RC3 tag for 1.3.0 & tarballs on github:
> https://github.com/intel/tpm2-tss/releases/tag/1.3.0-rc3
> 
> There has only been a single commit added since RC2 and it only
> affects
> the test code.

I prepared a fork of meta-measured which builds the release candidate
code and successfully tested it with the refkit TPM2-enabled whole-disk 
encryption:
https://github.com/pohly/meta-measured/tree/tpm2-tools-3.0

So from my perspective, the release is good to go. But admittedly my
testing is fairly limited ;-}

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



             reply	other threads:[~2017-12-07 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 17:45 Patrick Ohly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-07 23:38 [tpm2] tpm2-tss 1.3.0-rc0 available Philip Tricca
2017-12-06 16:50 Philip Tricca
2017-11-21 21:45 Philip Tricca
2017-11-14 20:43 Philip Tricca
2017-11-02  3:29 philip.b.tricca

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=1512668713.5979.157.camel@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