From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Petr Vorel <pvorel@suse.cz>,
linux-integrity@vger.kernel.org,
Vitaly Chikunov <vt@altlinux.org>,
"Bruno E . O . Meneguele" <bmeneg@redhat.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: Re: Exposing the tpm 2.0 PCRs? (renamed subject)
Date: Thu, 1 Aug 2019 20:34:54 +0300 [thread overview]
Message-ID: <20190801173454.4zjrndyxkn2mokzo@linux.intel.com> (raw)
In-Reply-To: <1563976601.4245.32.camel@linux.ibm.com>
On Wed, Jul 24, 2019 at 09:56:41AM -0400, Mimi Zohar wrote:
> [Cc'ing Jarkko]
>
> On Wed, 2019-07-24 at 09:24 +0200, Petr Vorel wrote:
> > > > > The kernel does not expose the crypto agile TPM 2.0 PCR banks to
> > > > > userspace like it exposes PCRs for TPM 1.2. As a result, a userspace
> > > > > application is required to read PCRs.
> > > > OT: anyone aware why TPM 2.0 does not expose PCR banks to userspace via sysfs?
> >
> > > TPM 2.0 support is slowly being upstreamed in stages. Initially the
> > > TPM 2.0 event log was not exported. Assuming that support for
> > > exposing the TPM 2.0 PCRs is upstreamed, it doesn't necessarily
> > > guarantee that it will be backported to stable.
>
> > Thanks for info. I'm glad it's being addressed :).
> > IMHO it'd be backporting it (once upstreamed), let's see.
>
> Clarification, I'm not working on exposing the TPM 2.0 PCRs. Too much
> else to do.
>
> Jarkko, in case you missed this thread, is there any reason why the
> TPM 2.0 PCRs can not be exposed to userspace?
What is meant by TPM 2.0 PCRs support?
/Jarkko
next prev parent reply other threads:[~2019-08-01 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 21:14 [PATCH v1] ima-evm-utils: use tsspcrread to read the TPM 2.0 PCRs Mimi Zohar
2019-07-22 21:55 ` Bruno E. O. Meneguele
2019-07-23 7:15 ` Petr Vorel
2019-07-23 13:27 ` Bruno E. O. Meneguele
2019-07-23 15:14 ` Mimi Zohar
2019-07-24 7:24 ` Petr Vorel
2019-07-24 13:56 ` Exposing the tpm 2.0 PCRs? (renamed subject) Mimi Zohar
2019-08-01 17:34 ` Jarkko Sakkinen [this message]
2019-08-01 19:58 ` Matthew Garrett
2019-08-02 19:36 ` Jarkko Sakkinen
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=20190801173454.4zjrndyxkn2mokzo@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=bmeneg@redhat.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=vt@altlinux.org \
--cc=zohar@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).