All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "David R. Bild" <david.bild@xaptum.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	philip.b.tricca@intel.com, Jason Gunthorpe <jgg@ziepe.ca>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Huewe <peterhuewe@gmx.de>,
	linux-usb@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM
Date: Thu, 10 May 2018 04:44:33 +0300	[thread overview]
Message-ID: <20180510014433.GM6190@linux.intel.com> (raw)
In-Reply-To: <CAAi9uDvgd5+d5fNbSGEeEVvdHLzwid6SqC0BVA3BPXkFWR4ooQ@mail.gmail.com>

On Tue, May 08, 2018 at 10:29:41AM -0500, David R. Bild wrote:
> On Tue, May 8, 2018 at 10:25 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote:
> > [...]
> > > > In particular, it sets the credentials for the platform hierarchy.
> > > > The platform hierarchy is essentially the "root" account of the
> > > > TPM, so it's critical that those credentials be set before the TPM
> > > > is exposed to user-space.  (The platform credentials aren't
> > > > persisted in the TPM and must be set by the platform on every
> > > > boot.)  If the driver registers the TPM before doing
> > > > initialization, there's a chance that something else could access
> > > > the TPM before the platform credentials get set.
> >
> > I don't see any reason to set an unreachable password for the platform
> > hierarchy if the UEFI didn't.  If the desire is to disable the platform
> > hierarchy, then it should be disabled, not have a random password set.
> 
> "Set random password and throw away the key" was my way of disabling
> the platform hierarchy.  Is there a better way of doing that?
> 
> > I'd also say this is probably the job of early boot based on policy.
> 
> Agreed.  And since this card has no "early boot", the driver/kernel
> need to do it.
> 
> Best,
> David

Who is able to test these changes if we even consider pulling them?
I do not have such a card so it will be hard to accept also given
that it is more intrusive change than usual.

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "David R. Bild" <david.bild@xaptum.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	philip.b.tricca@intel.com, Jason Gunthorpe <jgg@ziepe.ca>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Huewe <peterhuewe@gmx.de>,
	linux-usb@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: [v3,2/2] usb: misc: xapea00x: perform platform initialization of TPM
Date: Thu, 10 May 2018 04:44:33 +0300	[thread overview]
Message-ID: <20180510014433.GM6190@linux.intel.com> (raw)

On Tue, May 08, 2018 at 10:29:41AM -0500, David R. Bild wrote:
> On Tue, May 8, 2018 at 10:25 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote:
> > [...]
> > > > In particular, it sets the credentials for the platform hierarchy.
> > > > The platform hierarchy is essentially the "root" account of the
> > > > TPM, so it's critical that those credentials be set before the TPM
> > > > is exposed to user-space.  (The platform credentials aren't
> > > > persisted in the TPM and must be set by the platform on every
> > > > boot.)  If the driver registers the TPM before doing
> > > > initialization, there's a chance that something else could access
> > > > the TPM before the platform credentials get set.
> >
> > I don't see any reason to set an unreachable password for the platform
> > hierarchy if the UEFI didn't.  If the desire is to disable the platform
> > hierarchy, then it should be disabled, not have a random password set.
> 
> "Set random password and throw away the key" was my way of disabling
> the platform hierarchy.  Is there a better way of doing that?
> 
> > I'd also say this is probably the job of early boot based on policy.
> 
> Agreed.  And since this card has no "early boot", the driver/kernel
> need to do it.
> 
> Best,
> David

Who is able to test these changes if we even consider pulling them?
I do not have such a card so it will be hard to accept also given
that it is more intrusive change than usual.

/Jarkko
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-05-10  1:44 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180430125418.31344-1-david.bild@xaptum.com>
2018-05-04 13:00 ` [PATCH v3 0/2] Add driver for Xaptum ENF Access card (XAP-EA-00x) David R. Bild
2018-05-04 13:00 ` [PATCH v3 1/2] usb: misc: xapea00x: add driver for Xaptum ENF Access Card David R. Bild
2018-05-04 13:00   ` [v3,1/2] " David R. Bild
2018-05-07  9:58   ` [PATCH v3 1/2] " Oliver Neukum
2018-05-07  9:58     ` [v3,1/2] " Oliver Neukum
2018-05-07 13:31     ` [PATCH v3 1/2] " David R. Bild
2018-05-07 13:31       ` [v3,1/2] " David R. Bild
2018-05-08  9:09       ` [PATCH v3 1/2] " Oliver Neukum
2018-05-08  9:09         ` [v3,1/2] " Oliver Neukum
2018-05-04 13:00 ` [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM David R. Bild
2018-05-04 13:00   ` [v3,2/2] " David R. Bild
2018-05-04 19:06   ` [PATCH v3 2/2] " Jason Gunthorpe
2018-05-04 19:06     ` [v3,2/2] " Jason Gunthorpe
2018-05-04 19:56     ` [PATCH v3 2/2] " David R. Bild
2018-05-04 19:56       ` [v3,2/2] " David R. Bild
2018-05-04 20:19       ` [PATCH v3 2/2] " David R. Bild
2018-05-04 20:19         ` [v3,2/2] " David R. Bild
2018-05-06 15:02         ` [PATCH v3 2/2] " Jason Gunthorpe
2018-05-06 15:02           ` [v3,2/2] " Jason Gunthorpe
2018-05-10  1:42           ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-10  1:42             ` [v3,2/2] " Jarkko Sakkinen
2018-05-08 10:55       ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-08 10:55         ` [v3,2/2] " Jarkko Sakkinen
2018-05-08 15:25         ` [PATCH v3 2/2] " James Bottomley
2018-05-08 15:25           ` [v3,2/2] " James Bottomley
2018-05-08 15:29           ` [PATCH v3 2/2] " David R. Bild
2018-05-08 15:29             ` [v3,2/2] " David R. Bild
2018-05-08 15:36             ` [PATCH v3 2/2] " James Bottomley
2018-05-08 15:36               ` [v3,2/2] " James Bottomley
2018-05-10  1:59               ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-10  1:59                 ` [v3,2/2] " Jarkko Sakkinen
2018-05-10 14:31                 ` [PATCH v3 2/2] " David R. Bild
2018-05-10 14:31                   ` [v3,2/2] " David R. Bild
2018-05-13  8:51                   ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-13  8:51                     ` [v3,2/2] " Jarkko Sakkinen
2018-05-25 20:31                   ` [PATCH v3 2/2] " Ken Goldman
2018-05-25 20:31                     ` [v3,2/2] " Ken Goldman
2018-05-10 14:25               ` [PATCH v3 2/2] " David R. Bild
2018-05-10 14:25                 ` [v3,2/2] " David R. Bild
2018-05-10 14:47                 ` [PATCH v3 2/2] " James Bottomley
2018-05-10 14:47                   ` [v3,2/2] " James Bottomley
2018-05-10 15:17                   ` [PATCH v3 2/2] " David R. Bild
2018-05-10 15:17                     ` [v3,2/2] " David R. Bild
2018-05-25 20:23               ` [PATCH v3 2/2] " Ken Goldman
2018-05-25 20:23                 ` [v3,2/2] " Ken Goldman
2018-05-10  1:44             ` Jarkko Sakkinen [this message]
2018-05-10  1:44               ` Jarkko Sakkinen
2018-05-10 14:29               ` [PATCH v3 2/2] " David R. Bild
2018-05-10 14:29                 ` [v3,2/2] " David R. Bild
2018-05-10  1:42           ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-10  1:42             ` [v3,2/2] " Jarkko Sakkinen
2018-05-10 14:41         ` [PATCH v3 2/2] " David R. Bild
2018-05-10 14:41           ` [v3,2/2] " David R. Bild
2018-05-13  8:46           ` [PATCH v3 2/2] " Jarkko Sakkinen
2018-05-13  8:46             ` [v3,2/2] " Jarkko Sakkinen
2018-05-14 19:31           ` [PATCH v3 2/2] " Jason Gunthorpe
2018-05-14 19:31             ` [v3,2/2] " Jason Gunthorpe
2018-05-14 19:59             ` [PATCH v3 2/2] " David R. Bild
2018-05-14 19:59               ` [v3,2/2] " David R. Bild
2018-05-14 20:08               ` [PATCH v3 2/2] " Jason Gunthorpe
2018-05-14 20:08                 ` [v3,2/2] " Jason Gunthorpe
2018-05-14 20:12                 ` [PATCH v3 2/2] " David R. Bild
2018-05-14 20:12                   ` [v3,2/2] " David R. Bild
2018-05-07 14:12   ` EXTERNAL: [PATCH v3 2/2] " Jeremy Boone
2018-05-07 14:12     ` Jeremy Boone
2018-05-08 10:47   ` Jarkko Sakkinen
2018-05-08 10:47     ` [v3,2/2] " Jarkko Sakkinen
2018-05-10 14:09     ` [PATCH v3 2/2] " David R. Bild
2018-05-10 14:09       ` [v3,2/2] " David R. Bild

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=20180510014433.GM6190@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=david.bild@xaptum.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=philip.b.tricca@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.