linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: James Bottomley
	<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] x86/efi: pull NV+BS variables out before we exit boot services
Date: Wed, 20 Mar 2013 11:47:45 +0000	[thread overview]
Message-ID: <20130320114745.GA448@srcf.ucam.org> (raw)
In-Reply-To: <1363766403.2373.3.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>

On Wed, Mar 20, 2013 at 08:00:03AM +0000, James Bottomley wrote:

> I agree with this.  But I do think the volatile secret key scheme, where
> you discard the key immediately after use is the more secure one because
> it relies on fewer secrets (and, indeed, no secrets at all after the
> event).  It's a case where transparency encourages better security
> architecture.

That somewhat depends what you're securing against. There's an argument 
that reusing this key is actually sufficiently secure so long as the 
only way to obtain it is with physical access to the machine - that way 
you don't have an nvram update cycle every boot. Exposing these 
variables to userspace doesn't make it impossible to produce a secure 
system, but it does remove some choices that were previously available.

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org

  parent reply	other threads:[~2013-03-20 11:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18  8:40 [PATCH] x86/efi: pull NV+BS variables out before we exit boot services James Bottomley
     [not found] ` <1363596014.2412.8.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19  1:48   ` Matthew Garrett
     [not found]     ` <20130319014850.GA28934-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-19  8:14       ` James Bottomley
     [not found]         ` <1363680885.2377.11.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19 16:35           ` Matthew Garrett
2013-03-19 17:17             ` James Bottomley
     [not found]               ` <1363713447.2377.60.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19 17:25                 ` Matthew Garrett
     [not found]                   ` <20130319172506.GA11969-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-19 18:23                     ` James Bottomley
     [not found]                       ` <1363717411.2377.68.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19 18:28                         ` Matthew Garrett
     [not found]                           ` <20130319182810.GA13003-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-19 18:40                             ` James Bottomley
     [not found]                               ` <1363718456.2377.71.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19 18:50                                 ` Matthew Garrett
     [not found]                                   ` <20130319185003.GA13301-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-19 23:00                                     ` James Bottomley
     [not found]                                       ` <1363734031.2377.77.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-19 23:17                                         ` Matthew Garrett
     [not found]                                           ` <20130319231756.GA21071-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-03-20  8:00                                             ` James Bottomley
     [not found]                                               ` <1363766403.2373.3.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-20 11:47                                                 ` Matthew Garrett [this message]
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=20130320114745.GA448@srcf.ucam.org \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
    --cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).