All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
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 01:48:50 +0000	[thread overview]
Message-ID: <20130319014850.GA28934@srcf.ucam.org> (raw)
In-Reply-To: <1363596014.2412.8.camel@dabdike.int.hansenpartnership.com>

On Mon, Mar 18, 2013 at 08:40:14AM +0000, James Bottomley wrote:

> The object here is to make the NV+BS variables accessible (at least read only)
> at runtime so we can get a full picture of the state of the EFI variables for
> debugging and secure boot purposes.

I'd really prefer not to do this - the reason these aren't flagged as RT 
is that they're not supposed to be visible at runtime and may break 
certain security assumptions. If there's a real development purpose to 
this then it ought to be guarded as a config option.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

WARNING: multiple messages have this Message-ID (diff)
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: Tue, 19 Mar 2013 01:48:50 +0000	[thread overview]
Message-ID: <20130319014850.GA28934@srcf.ucam.org> (raw)
In-Reply-To: <1363596014.2412.8.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>

On Mon, Mar 18, 2013 at 08:40:14AM +0000, James Bottomley wrote:

> The object here is to make the NV+BS variables accessible (at least read only)
> at runtime so we can get a full picture of the state of the EFI variables for
> debugging and secure boot purposes.

I'd really prefer not to do this - the reason these aren't flagged as RT 
is that they're not supposed to be visible at runtime and may break 
certain security assumptions. If there's a real development purpose to 
this then it ought to be guarded as a config option.

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

  reply	other threads:[~2013-03-19  1:48 UTC|newest]

Thread overview: 29+ 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
2013-03-18  8:40 ` James Bottomley
2013-03-19  1:48 ` Matthew Garrett [this message]
2013-03-19  1:48   ` Matthew Garrett
2013-03-19  8:14   ` James Bottomley
2013-03-19  8:14     ` James Bottomley
2013-03-19 16:35     ` Matthew Garrett
2013-03-19 16:35       ` Matthew Garrett
2013-03-19 17:17       ` James Bottomley
2013-03-19 17:25         ` Matthew Garrett
2013-03-19 17:25           ` Matthew Garrett
2013-03-19 18:23           ` James Bottomley
2013-03-19 18:23             ` James Bottomley
2013-03-19 18:28             ` Matthew Garrett
2013-03-19 18:28               ` Matthew Garrett
2013-03-19 18:40               ` James Bottomley
2013-03-19 18:40                 ` James Bottomley
2013-03-19 18:50                 ` Matthew Garrett
2013-03-19 18:50                   ` Matthew Garrett
2013-03-19 23:00                   ` James Bottomley
2013-03-19 23:00                     ` James Bottomley
2013-03-19 23:17                     ` Matthew Garrett
2013-03-19 23:17                       ` Matthew Garrett
2013-03-20  8:00                       ` James Bottomley
2013-03-20  8:00                         ` James Bottomley
2013-03-20 11:47                         ` Matthew Garrett
2013-03-20 11:47                           ` Matthew Garrett
2013-03-20 11:26 ` Matt Fleming
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=20130319014850.GA28934@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.