[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130226023332.GA29282@srcf.ucam.org>
Date: Tue, 26 Feb 2013 02:33:32 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: David Howells <dhowells@...hat.com>,
Florian Weimer <fw@...eb.enyo.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Josh Boyer <jwboyer@...hat.com>,
Peter Jones <pjones@...hat.com>,
Vivek Goyal <vgoyal@...hat.com>,
Kees Cook <keescook@...omium.org>, keyrings@...ux-nfs.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Load keys from signed PE binaries
On Mon, Feb 25, 2013 at 04:59:55PM -0800, Greg KH wrote:
> Wait right here. This is NOT mandated by UEFI, nor by anyone else. It
> might be a nice thing that some people and companies want to implement,
> but please don't think that some external entity is requiring that Linux
> implement this, that is not true.
Oh, come on Greg. Allowing unsigned modules allows loading arbitrary
code into the kernel, and allowing arbitrary code into the kernel means
that the kernel can be used to directly boot a modified copy of the
Windows kernel. Avoiding that scenario is *explicitly* mandated by
Microsoft. We can avoid it by either not using Microsoft as the root of
trust or by requiring explicit key installation during the OS install
process, but both of those make OS installation more difficult. If we
want Linux to Just Work out of the box on Microsoft-certified hardware,
this is one of the rules we have to live by.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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