linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: David Howells <dhowells@redhat.com>, Petr Vorel <pvorel@suse.cz>,
	shuah <shuah@kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-integrity@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test
Date: Tue, 29 Oct 2019 11:25:16 +0200	[thread overview]
Message-ID: <20191029092516.GA13848@linux.intel.com> (raw)
In-Reply-To: <20191029091535.GB9896@linux.intel.com>

On Tue, Oct 29, 2019 at 11:15:35AM +0200, Jarkko Sakkinen wrote:
> On Mon, Oct 28, 2019 at 04:45:13PM -0400, Mimi Zohar wrote:
> > On Mon, 2019-10-28 at 22:30 +0200, Jarkko Sakkinen wrote:
> > > On Thu, Oct 24, 2019 at 03:14:27PM -0400, Mimi Zohar wrote:
> > > > Create, save and load trusted keys test
> > > > 
> > > > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> > > > 
> > > > Change log v1:
> > > > - Replace the directions for using Trousers to take ownership of the TPM
> > > > with directions for using the IBM TSS.
> > > > - Differentiate between different types of errors.  Recent bug is causing
> > > > "add_key: Timer expired".
> > > > ---
> > > 
> > > Is not really usable as a selftest because of 3rd party dependencies.
> > 
> > As part of diagnosing trusted keys failure, there is some
> > hints/directions as to how to take TPM 1.2 ownership, but it does not
> > take ownership.  The previous version included directions for using
> > Trousers.  This version provides directions for using the IBM TSS.
> >  Feel free to include additional hints/directions.
> 
> You must write your own minimal user space that can be included
> to the kernel. Otherwise, we cannot take it.

I'll anyway try to setup user space with TrouSerS so that I can try
it out. BuildRoot has recipe for that but not for IBM TSS 2.0 so I'll
skip that and use my own test script for TPM2 trusted keys.

/Jarkko

  reply	other threads:[~2019-10-29  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 19:14 [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test Mimi Zohar
2019-10-24 19:24 ` Mimi Zohar
2019-10-28 20:35   ` Jarkko Sakkinen
2019-10-28 20:30 ` Jarkko Sakkinen
2019-10-28 20:40   ` Jarkko Sakkinen
2019-10-28 20:45   ` Mimi Zohar
2019-10-29  9:15     ` Jarkko Sakkinen
2019-10-29  9:25       ` Jarkko Sakkinen [this message]
2019-10-29 11:45         ` Jarkko Sakkinen
2019-10-29 11:49           ` 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=20191029092516.GA13848@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dhowells@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pvorel@suse.cz \
    --cc=shuah@kernel.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).