From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Petr Vorel" <pvorel@suse.cz>, Nayna <nayna@linux.vnet.ibm.com>,
"Mimi Zohar" <zohar@linux.ibm.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
ltp@lists.linux.it, "Piotr Król" <piotr.krol@3mdeb.com>,
"Peter Huewe" <peterhuewe@gmx.de>
Subject: Re: [LTP] [PATCH] ima: skip verifying TPM 2.0 PCR values
Date: Mon, 28 Oct 2019 22:51:22 +0200 [thread overview]
Message-ID: <20191028205122.GG8279@linux.intel.com> (raw)
In-Reply-To: <20191024233602.GF23952@ziepe.ca>
On Thu, Oct 24, 2019 at 08:36:02PM -0300, Jason Gunthorpe wrote:
> On Thu, Oct 24, 2019 at 10:14:02PM +0300, Jarkko Sakkinen wrote:
> > On Thu, Oct 24, 2019 at 03:20:05PM -0300, Jason Gunthorpe wrote:
> > > On Thu, Oct 24, 2019 at 08:20:23PM +0300, Jarkko Sakkinen wrote:
> > > > Also replicants for durations and timeouts files would make sense for
> > > > TPM 2.0.
> > >
> > > These ones don't meet the sysfs standard of one value per file, which
> > > is why they didn't make it to tpm2
> >
> > They would be still useful to have available in some form as there is
> > no way deduce them from the user space.
>
> Why? Userspace doesn't refer to these values since the kernel handles
> all the timeouts, right?
For debugging at least would be definitely a nice to have what
values the driver ended up setting.
/Jarkko
next prev parent reply other threads:[~2019-10-28 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 21:12 [PATCH] ima: skip verifying TPM 2.0 PCR values Mimi Zohar
2019-05-17 6:51 ` Petr Vorel
2019-05-17 11:19 ` Mimi Zohar
2019-05-17 11:28 ` Petr Vorel
2019-05-17 13:50 ` Nayna
2019-05-17 15:04 ` Petr Vorel
2019-10-24 12:18 ` [LTP] " Petr Vorel
2019-10-24 17:20 ` Jarkko Sakkinen
2019-10-24 18:20 ` Jason Gunthorpe
2019-10-24 19:14 ` Jarkko Sakkinen
2019-10-24 23:36 ` Jason Gunthorpe
2019-10-28 20:51 ` Jarkko Sakkinen [this message]
2019-10-24 21:38 ` Jerry Snitselaar
2019-10-24 23:26 ` Jason Gunthorpe
2019-10-25 0:47 ` Mimi Zohar
2019-10-25 2:11 ` Jerry Snitselaar
2019-10-25 8:56 ` Petr Vorel
2019-10-25 12:52 ` Serge E. Hallyn
2019-10-25 13:22 ` Mimi Zohar
2019-10-25 13:25 ` Petr Vorel
2019-10-25 14:13 ` Jerry Snitselaar
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=20191028205122.GG8279@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=nayna@linux.vnet.ibm.com \
--cc=peterhuewe@gmx.de \
--cc=piotr.krol@3mdeb.com \
--cc=pvorel@suse.cz \
--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).