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 17:17:27 +0000 [thread overview]
Message-ID: <1363713447.2377.60.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20130319163531.GA10879@srcf.ucam.org>
On Tue, 2013-03-19 at 16:35 +0000, Matthew Garrett wrote:
> On Tue, Mar 19, 2013 at 08:14:45AM +0000, James Bottomley wrote:
>
> > Any security assumptions that rely on inability to read certain
> > information aren't really going to be that secure. Inability to modify,
> > sure, but inability to read, not really.
>
> Well, I guess that's public/private key cryptography screwed.
Well, OK, it's ex-BIOS writers we're dealing with, so I won't say no-one
would be stupid enough to come up with a security scheme embedding
Private Keys in BS+NV variables, but I would have thought the fact that
Linux would blow the lid off it might be a good incentive not to do it
and thus a plus point for this patch.
James
next prev parent reply other threads:[~2013-03-19 17:17 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 [this message]
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
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=1363713447.2377.60.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®