From: Patrick Ohly <patrick.ohly at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] using TPM2 NVRAM for storing LUKS password
Date: Mon, 27 Nov 2017 11:03:32 +0100 [thread overview]
Message-ID: <1511777012.5979.72.camel@intel.com> (raw)
In-Reply-To: e8b1c8c5-6ec1-5a91-7eb9-2ece61d1c8f7@linux.vnet.ibm.com
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Fri, 2017-11-10 at 10:27 -0500, Stefan Berger wrote:
> On 11/10/2017 07:53 AM, Patrick Ohly wrote:
> > Perhaps it would help to advertise some versions of the tpm2-
> > preview
> > code as "ready for testing", for example by tagging them?
>
> I'll do that next week, after some changes/fixes, and post here and
> on the QEMU devel mailing list.
How is it going with that?
FWIW, I updated my build recipes to your latest snapshots
(adf9b3fe5d4df6708e9f801b8c9dcfdf7274d457 for swtpm,
42a5d1ca4680b1caba67c06fe2011fdc5b253785 for libswtpm) and it continued
to work for me.
--
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.
next reply other threads:[~2017-11-27 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 10:03 Patrick Ohly [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-27 11:50 [tpm2] using TPM2 NVRAM for storing LUKS password Stefan Berger
2017-11-10 15:27 Stefan Berger
2017-11-10 12:53 Patrick Ohly
2017-11-10 12:44 Patrick Ohly
2017-11-10 12:04 Stefan Berger
2017-11-10 11:53 Stefan Berger
2017-11-10 9:07 Patrick Ohly
2017-11-09 20:43 Patrick Ohly
2017-11-09 20:40 Patrick Ohly
2017-11-09 19:51 Patrick Ohly
2017-11-09 15:25 flihp
2017-11-09 15:17 Stefan Berger
2017-11-09 15:10 Patrick Ohly
2017-11-09 14:12 Javier Martinez Canillas
2017-11-09 12:53 Patrick Ohly
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=1511777012.5979.72.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.