From: David Safford <safford@watson.ibm.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
linux-crypto@vger.kernel.org, David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
Rajiv Andrade <srajiv@linux.vnet.ibm.com>,
Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH v1.2 3/4] keys: add new trusted key-type
Date: Mon, 08 Nov 2010 13:18:33 -0500 [thread overview]
Message-ID: <1289240313.6060.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20101108170937.GA31501@obsidianresearch.com>
On Mon, 2010-11-08 at 10:09 -0700, Jason Gunthorpe wrote:
> On Mon, Nov 08, 2010 at 10:30:45AM -0500, Mimi Zohar wrote:
>
> > pcrlock=n extends the designated PCR 'n' with a random value,
> > so that a key sealed to that PCR may not be unsealed
> > again until after a reboot.
>
> Nice, but this seems very strange to me, since it has nothing to do
> with the key and could be done easially in userspace?
>
> Jason
This is strictly for convenience in initramfs, so that the trusted
key can be loaded and locked in a single command, with no need for
an additional application to extend a PCR. As the the TPM driver
already has support for extend, it's a trivial addition.
dave
next prev parent reply other threads:[~2010-11-08 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 15:30 [PATCH v1.2 0/4] keys: trusted and encrypted keys Mimi Zohar
2010-11-08 15:30 ` [PATCH v1.2 1/4] lib: hex2bin converts ascii hexadecimal string to binary Mimi Zohar
2010-11-08 15:30 ` [PATCH v1.2 2/4] key: add tpm_send command Mimi Zohar
2010-11-08 15:30 ` [PATCH v1.2 3/4] keys: add new trusted key-type Mimi Zohar
2010-11-08 17:09 ` Jason Gunthorpe
2010-11-08 18:18 ` David Safford [this message]
2010-11-09 6:40 ` Jason Gunthorpe
2010-11-09 15:17 ` David Safford
2010-11-09 16:02 ` Roberto Sassu
2010-11-09 16:25 ` David Safford
2010-11-09 16:46 ` Roberto Sassu
2010-11-08 15:30 ` [PATCH v1.2 4/4] keys: add new key-type encrypted Mimi Zohar
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=1289240313.6060.10.camel@localhost.localdomain \
--to=safford@watson.ibm.com \
--cc=dhowells@redhat.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=srajiv@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
--cc=zohar@us.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