public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
Cc: Kenneth Goldman <kgoldman@us.ibm.com>,
	"moderated list:TPM DEVICE DRIVER" 
	<tpmdd-devel@lists.sourceforge.net>,
	open list <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org
Subject: Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log
Date: Wed, 1 Feb 2017 00:31:06 +0200	[thread overview]
Message-ID: <20170131223106.faap5tfrd4qquhqv@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1702010842220.28891@namei.org>

On Wed, Feb 01, 2017 at 08:46:32AM +1100, James Morris wrote:
> On Tue, 31 Jan 2017, Jarkko Sakkinen wrote:
> 
> > James,
> > 
> > The discussion is about two features:
> > 
> > 1. Extension to tpm_pcr_extend() (used by IMA) to extend all PCR banks
> >    instead of just SHA-1 banks. It is recommended by TCG to do so in
> >    order to prevent malicious use of PCRs.
> > 2. TPM 2.0 event log with backend support for OF device tree (for
> >    getting address where you can grab it).
> > 
> > These are required as baseline to implement full TPM 2.0 support for
> > IMA. The commits are fairly well baked and went through many iterations.
> > I've tested tpm_pcr_extend() patches. I haven't tested event log patches
> > but have extensively reviewed them and Ken Goldman has tested them with
> > POWER hardware.
> > 
> > I don't believe that there is major risk to put them already into 4.11
> > but it is fairly late so I just want a second opinion before putting
> > them into pull request.
> > 
> 
> I'll take this for 4.11.  IMA + TPM 2.0 is still developmental and not in 
> wide use, afaik.
> 
> 
> 
> -- 
> James Morris
> <jmorris@namei.org>

Great! I'll prepare the pull request tomorrow (it's now 12:30AM in
Finland). Thank you.

/Jarkko

  reply	other threads:[~2017-01-31 22:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 21:22 [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log Ken Goldman
2017-01-25 23:06 ` Jarkko Sakkinen
     [not found] ` <CALAzByG474T_qSJ0Kry1LiNSsCQAHUagqcqtR_CnpporicZrdg@mail.gmail.com>
2017-01-30  9:38   ` Fwd: " Nayna
2017-01-30 21:49     ` Jarkko Sakkinen
2017-01-31 17:46     ` Jarkko Sakkinen
2017-01-31 18:44       ` Nayna
2017-01-31 20:50         ` Jarkko Sakkinen
2017-02-01  7:31           ` Nayna
2017-02-01 18:27             ` Jarkko Sakkinen
2017-02-01 14:48           ` Jarkko Sakkinen
2017-02-01 14:54             ` Jarkko Sakkinen
2017-02-01 19:25               ` Nayna
2017-02-01 19:50                 ` Jarkko Sakkinen
2017-01-31 20:34       ` Jarkko Sakkinen
2017-01-31 21:46         ` James Morris
2017-01-31 22:31           ` Jarkko Sakkinen [this message]
2017-01-31 22:31           ` Mimi Zohar
2017-02-01 10:30             ` Jarkko Sakkinen
2017-02-01 13:49               ` Mimi Zohar
2017-02-01 18:23                 ` Jarkko Sakkinen
2017-01-31 13:13 ` [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support, for " 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=20170131223106.faap5tfrd4qquhqv@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jmorris@namei.org \
    --cc=kgoldman@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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