[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1510662098.3711.139.camel@linux.vnet.ibm.com>
Date: Tue, 14 Nov 2017 07:21:38 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
David Howells <dhowells@...hat.com>
Cc: Alan Cox <gnomes@...rguk.ukuu.org.uk>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
"AKASHI, Takahiro" <takahiro.akashi@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jan Blunck <jblunck@...radead.org>,
Julia Lawall <julia.lawall@...6.fr>,
Marcus Meissner <meissner@...e.de>, Gary Lin <GLin@...e.com>,
LSM List <linux-security-module@...r.kernel.org>,
linux-efi <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Matthew Garrett <mjg59@...gle.com>
Subject: Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel
lockdown
On Mon, 2017-11-13 at 14:09 -0800, Linus Torvalds wrote:
> On Mon, Nov 13, 2017 at 1:44 PM, David Howells <dhowells@...hat.com> wrote:
> >
> > Whilst that may be true, we either have to check signatures on every bit of
> > firmware that the appropriate driver doesn't say is meant to be signed or not
> > bother.
>
> I vote for "not bother".
>
> Seriously, if you have firmware in /lib/firmware, and you don't trust
> it, what the hell are you doing?
I might "trust" the files in /lib/firmware, but I also want to make
sure that they haven't changed. File signatures provide file
provenance and integrity guarantees.
Mimi
Powered by blists - more mailing lists