[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191028204005.GD8279@linux.intel.com>
Date: Mon, 28 Oct 2019 22:40:05 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Mimi Zohar <zohar@...ux.ibm.com>
Cc: David Howells <dhowells@...hat.com>, Petr Vorel <pvorel@...e.cz>,
shuah <shuah@...nel.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
linux-integrity@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test
On Mon, Oct 28, 2019 at 10:30:14PM +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@...ux.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.
For TPM 2.0 I did write a smoke test for TPM2 trusted keys:
https://github.com/jsakkine-intel/tpm2-scripts
What you need to do is to make a lightweight library for TPM 1.x e.g.
tpm1.py, and use that to implement the test.
For TPM 2.0 I would peek at the tpm2-pcr-policy and keyctl-smoke.sh on
how to implement the without 3rd party deps.
/Jarkko
Powered by blists - more mailing lists