From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-efi@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/efi: pull NV+BS variables out before we exit boot services
Date: Tue, 19 Mar 2013 23:00:31 +0000 [thread overview]
Message-ID: <1363734031.2377.77.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20130319185003.GA13301@srcf.ucam.org>
On Tue, 2013-03-19 at 18:50 +0000, Matthew Garrett wrote:
> On Tue, Mar 19, 2013 at 06:40:56PM +0000, James Bottomley wrote:
> > On Tue, 2013-03-19 at 18:28 +0000, Matthew Garrett wrote:
> > > It requires the key to survive the system being entirely powered down,
> > > which means it needs to be BS+NV. It shouldn't be possible for userspace
> > > to access this key.
> >
> > It requires the *public* key to survive power down, certainly. The
> > private key can be thrown away once the hibernate image is signed. I
> > think the scheme can be constructed so the private key is never in NV
> > storage ... that also makes it more secure against tampering.
>
> Well, that somewhat complicates implementation - we'd be encrypting the
> entire contents of memory except for the key that we're using to encrypt
> memory. Keeping the public key away from userspace avoids having to care
> about that.
I don't quite understand what you're getting at: the principle of public
key cryptography is that you can make the public key, well public. You
only need to guard the private key.
James
next prev parent reply other threads:[~2013-03-19 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 8:40 James Bottomley
2013-03-19 1:48 ` Matthew Garrett
2013-03-19 8:14 ` James Bottomley
2013-03-19 16:35 ` Matthew Garrett
2013-03-19 17:17 ` James Bottomley
2013-03-19 17:25 ` Matthew Garrett
2013-03-19 18:23 ` James Bottomley
2013-03-19 18:28 ` Matthew Garrett
2013-03-19 18:40 ` James Bottomley
2013-03-19 18:50 ` Matthew Garrett
2013-03-19 23:00 ` James Bottomley [this message]
2013-03-19 23:17 ` Matthew Garrett
2013-03-20 8:00 ` James Bottomley
2013-03-20 11:47 ` Matthew Garrett
2013-03-20 11:26 ` Matt Fleming
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=1363734031.2377.77.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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
all inboxes | Powered by JetHome®