[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101108170937.GA31501@obsidianresearch.com>
Date: Mon, 8 Nov 2010 10:09:37 -0700
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
linux-crypto@...r.kernel.org, David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
David Safford <safford@...son.ibm.com>,
Rajiv Andrade <srajiv@...ux.vnet.ibm.com>,
Mimi Zohar <zohar@...ibm.com>
Subject: Re: [PATCH v1.2 3/4] keys: add new trusted key-type
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists