From: Mimi Zohar <zohar@linux.ibm.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Jordan Hand" <jorhand@linux.microsoft.com>,
"Tadeusz Struk" <tadeusz.struk@intel.com>,
"Piotr Król" <piotr.krol@3mdeb.com>,
linux-integrity@vger.kernel.org,
"Alexey Dobriyan" <adobriyan@gmail.com>
Subject: Re: TPM 2.0 Linux sysfs interface
Date: Wed, 04 Sep 2019 16:26:51 -0400 [thread overview]
Message-ID: <1567628811.4937.57.camel@linux.ibm.com> (raw)
In-Reply-To: <20190904194348.GA3757@ziepe.ca>
On Wed, 2019-09-04 at 16:43 -0300, Jason Gunthorpe wrote:
> On Wed, Sep 04, 2019 at 07:30:58AM -0400, Mimi Zohar wrote:
> > On Wed, 2019-09-04 at 02:58 -0300, Jason Gunthorpe wrote:
> > > On Tue, Sep 03, 2019 at 07:29:43PM -0400, Mimi Zohar wrote:
> > >
> > > > This discussion is going around in circles. There are enough people
> > > > asking that the kernel provide at least the TPM version (eg. TPM 1.2
> > > > or TPM 2.0). Userspace applications/regression tests shouldn't have
> > > > to figure out the TPM version by sending a TPM command and seeing if
> > > > it fails. That really isn't asking a lot.
> > >
> > > A single version number could be appropriate for sysfs
> > >
> > > > I would also prefer not having to be dependent on a userspace
> > > > application to read the TPM PCRs in order to verify the IMA
> > > > measurement list.
> > >
> > > Why?
> >
> > Being dependent on a userspace application implies a level of trust,
> > that might not be warranted, depending on the system's
> > configuration.
>
> Surely if you can trust 'cat' you can trust something that does ioctl?
Ok, you've agreed with the kernel exporting the TPM information. How
it is exported remains to be defined.
Mimi
next prev parent reply other threads:[~2019-09-04 20:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 23:24 TPM 2.0 Linux sysfs interface Piotr Król
2019-08-27 1:05 ` Jason Gunthorpe
2019-08-28 15:53 ` Mimi Zohar
2019-08-28 16:15 ` Jason Gunthorpe
2019-08-30 21:20 ` Tadeusz Struk
2019-09-02 19:26 ` Jason Gunthorpe
2019-09-02 21:35 ` Mimi Zohar
2019-09-03 5:55 ` Jason Gunthorpe
2019-09-03 11:49 ` Mimi Zohar
2019-09-03 13:07 ` Jason Gunthorpe
2019-09-03 13:23 ` Mimi Zohar
2019-09-03 16:21 ` Jarkko Sakkinen
2019-09-03 16:23 ` Tadeusz Struk
2019-09-03 22:40 ` Jordan Hand
2019-09-03 23:29 ` Mimi Zohar
2019-09-04 5:58 ` Jason Gunthorpe
2019-09-04 11:30 ` Mimi Zohar
2019-09-04 19:43 ` Jason Gunthorpe
2019-09-04 20:26 ` Mimi Zohar [this message]
2019-09-06 17:53 ` Serge E. Hallyn
2019-08-28 15:03 ` Mimi Zohar
2019-08-28 17:15 ` Petr Vorel
2019-08-28 23:22 ` Piotr Król
2019-08-29 7:32 ` Petr Vorel
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=1567628811.4937.57.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=adobriyan@gmail.com \
--cc=jgg@ziepe.ca \
--cc=jorhand@linux.microsoft.com \
--cc=linux-integrity@vger.kernel.org \
--cc=piotr.krol@3mdeb.com \
--cc=tadeusz.struk@intel.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).