From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH] selftest/trustedkeys: TPM 1.2 trusted keys test
Date: Tue, 22 Oct 2019 17:43:20 +0300 [thread overview]
Message-ID: <20191022144320.GA3758@linux.intel.com> (raw)
In-Reply-To: <20191014195725.GL15552@linux.intel.com>
On Mon, Oct 14, 2019 at 10:57:25PM +0300, Jarkko Sakkinen wrote:
> On Fri, Oct 11, 2019 at 09:21:33AM -0400, Mimi Zohar wrote:
> > On Fri, 2019-10-11 at 16:01 +0300, Jarkko Sakkinen wrote:
> > > On Tue, Sep 10, 2019 at 07:18:31PM -0400, Mimi Zohar wrote:
> > > > Create, save and load trusted keys test
> > > >
> > > > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> > >
> > > Also can be used to test Sumit's patches i.e. there is an immediate
> > > application for this one. I'll use this check TPM 1.x and TPM 2.0
> > > trusted keys code.
> > >
> > > You could sanity check your script for sending with my master, which
> > > already has those patches.
> >
> > Sure, but due to the holidays that won't happen until the middle of
> > next week.
>
> There is no immediate rush, or more like, this should not be rushed.
>
> I'm also waiting v8 now because of sparse issues.
OK, so you must get rid of TrouSerS dependency. Otherwise this
is unsuitable for kernel selftests. Please do TPM 1.x with the
raw TPM device.
A legit selftest should be implemented only with POSIX assets.
/Jarkko
prev parent reply other threads:[~2019-10-22 14:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 23:18 [PATCH] selftest/trustedkeys: TPM 1.2 trusted keys test Mimi Zohar
2019-09-10 23:24 ` Mimi Zohar
2019-09-11 12:00 ` Mimi Zohar
2019-09-13 14:08 ` Jarkko Sakkinen
2019-09-15 20:52 ` Mimi Zohar
2019-09-16 3:27 ` Mimi Zohar
2019-09-16 7:35 ` Jarkko Sakkinen
2019-09-16 7:48 ` Jarkko Sakkinen
2019-09-16 11:36 ` Mimi Zohar
2019-09-16 7:42 ` Jerry Snitselaar
2019-09-16 10:44 ` Sumit Garg
2019-09-16 14:00 ` Jerry Snitselaar
2019-09-16 11:52 ` Mimi Zohar
2019-09-16 14:28 ` Jerry Snitselaar
2019-09-16 7:15 ` Jarkko Sakkinen
2019-10-11 12:34 ` Jarkko Sakkinen
2019-10-11 13:01 ` Jarkko Sakkinen
2019-10-11 13:21 ` Mimi Zohar
2019-10-14 19:57 ` Jarkko Sakkinen
2019-10-22 14:43 ` 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=20191022144320.GA3758@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--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).