From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "David R. Bild" <david.bild@xaptum.com>,
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:42:10 +0300 [thread overview]
Message-ID: <20180510014210.GK6190@linux.intel.com> (raw)
In-Reply-To: <20180506150229.jvbkvq7hlxbgmsgn@ziepe.ca>
On Sun, May 06, 2018 at 09:02:29AM -0600, Jason Gunthorpe wrote:
> On Fri, May 04, 2018 at 03:19:21PM -0500, David R. Bild wrote:
> > Setting the platform hierarchy password to a random discarded value
> > (and the dictionary lockout reset) is really the only special work
> > done here. The other steps (startup, self test, etc.) are done by the
> > TPM subsystem if needed.
> >
> > So easy option would be for the TPM subsystem to set the platform
> > hierarchy password to a random value during device registration, if
> > needed. It could either
>
> This would probably make more sense, I'm not opposed at least
>
> > This wouldn't require a significant change to the TPM subsystem
> > internals and would let me drop nearly the entire second patch from
> > this series. (I think the dictionary lockout reset can be done via
> > the already exported "tpm_send(...)" function.)
>
> Sounds like a much better approach to me.
>
> Jason
Yes this part but I have absolutely zero understanding about what was
explained before this part (the *longer* part in the email).
/Jarkko
next prev parent reply other threads:[~2018-05-10 1:42 UTC|newest]
Thread overview: 35+ 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-07 9:58 ` Oliver Neukum
2018-05-07 13:31 ` David R. Bild
2018-05-08 9:09 ` 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 19:06 ` Jason Gunthorpe
2018-05-04 19:56 ` David R. Bild
2018-05-04 20:19 ` David R. Bild
2018-05-06 15:02 ` Jason Gunthorpe
2018-05-10 1:42 ` Jarkko Sakkinen [this message]
2018-05-08 10:55 ` Jarkko Sakkinen
2018-05-08 15:25 ` James Bottomley
2018-05-08 15:29 ` David R. Bild
2018-05-08 15:36 ` James Bottomley
2018-05-10 1:59 ` Jarkko Sakkinen
2018-05-10 14:31 ` David R. Bild
2018-05-13 8:51 ` Jarkko Sakkinen
2018-05-25 20:31 ` Ken Goldman
2018-05-10 14:25 ` David R. Bild
2018-05-10 14:47 ` James Bottomley
2018-05-10 15:17 ` David R. Bild
2018-05-25 20:23 ` Ken Goldman
2018-05-10 1:44 ` Jarkko Sakkinen
2018-05-10 14:29 ` David R. Bild
2018-05-10 1:42 ` Jarkko Sakkinen
2018-05-10 14:41 ` David R. Bild
2018-05-13 8:46 ` Jarkko Sakkinen
2018-05-14 19:31 ` Jason Gunthorpe
2018-05-14 19:59 ` David R. Bild
2018-05-14 20:08 ` Jason Gunthorpe
2018-05-14 20:12 ` David R. Bild
2018-05-07 14:12 ` EXTERNAL: " Jeremy Boone
2018-05-08 10:47 ` Jarkko Sakkinen
2018-05-10 14:09 ` 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=20180510014210.GK6190@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.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 \
/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).