From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
Stefan Berger <stefanb@linux.ibm.com>,
keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Extend trusted keys documentation for TPM 2.0
Date: Fri, 30 Nov 2018 15:46:46 -0800 [thread overview]
Message-ID: <20181130234646.GB3792@linux.intel.com> (raw)
In-Reply-To: <20181130234507.GA3792@linux.intel.com>
On Fri, Nov 30, 2018 at 03:45:07PM -0800, Jarkko Sakkinen wrote:
> On Tue, Nov 06, 2018 at 01:17:34PM -0500, Mimi Zohar wrote:
> > On Tue, 2018-11-06 at 09:46 -0700, Jerry Snitselaar wrote:
> > > On Fri Oct 19 18, Stefan Berger wrote:
> > > >Extend the documentation for trusted keys with documentation for how to
> > > >set up a key for a TPM 2.0 so it can be used with a TPM 2.0 as well.
> > > >
> > > >Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> > > >Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> > >
> > > Acked-by: Jerry Snitselaar <jsnitsel@redhat.com>
> >
> > Thanks! This patch is now staged in the #next-integrity-queued
> > branch.
> >
> > Mimi
>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Brings to mind, in the long run where the backend code for trusted keys
should reside.
/Jarkko
next prev parent reply other threads:[~2018-11-30 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 10:17 [PATCH] docs: Extend trusted keys documentation for TPM 2.0 Stefan Berger
2018-10-19 23:07 ` Randy Dunlap
2018-11-05 16:57 ` Dan Williams
2018-11-05 20:42 ` Jerry Snitselaar
2018-11-06 16:00 ` Jerry Snitselaar
2018-11-06 16:14 ` Joshua Lock
2018-11-07 0:53 ` Roberts, William C
2018-11-06 16:46 ` Jerry Snitselaar
2018-11-06 18:17 ` Mimi Zohar
2018-11-30 23:45 ` Jarkko Sakkinen
2018-11-30 23:46 ` Jarkko Sakkinen [this message]
2018-12-02 15:10 ` Mimi Zohar
2018-12-02 23:04 ` 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=20181130234646.GB3792@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jsnitsel@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.ibm.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).