From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <mjg59@google.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>, Petr Vorel <pvorel@suse.cz>,
linux-integrity <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: Fri, 2 Aug 2019 22:36:00 +0300 [thread overview]
Message-ID: <20190802193600.prsjeyuagojnxk72@linux.intel.com> (raw)
In-Reply-To: <CACdnJuuL=fHp8uiaUf+Z8Pgaj7pm5J5LmKaFsVpU=_rgj_UDGA@mail.gmail.com>
On Thu, Aug 01, 2019 at 12:58:44PM -0700, Matthew Garrett wrote:
> On Thu, Aug 1, 2019 at 10:35 AM Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> > What is meant by TPM 2.0 PCRs support?
>
> You can read TPM 1.2 PCR values directly through sysfs. There's no
> equivalent mechanism for obtaining the TPM 2 PCR banks - you have to
> talk to the TPM yourself.
OK, when I did the TPM 2.0 support originally the conclusion was then
that since you can easily get what you need through /dev/tpm0, we don't
need such sysfs file.
That does mean that it cannot be added if there are legit reasons to
do so...
/Jarkko
prev parent reply other threads:[~2019-08-02 19:36 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
2019-08-01 19:58 ` Matthew Garrett
2019-08-02 19:36 ` Jarkko Sakkinen [this message]
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=20190802193600.prsjeyuagojnxk72@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=bmeneg@redhat.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--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).