From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregkh@linuxfoundation.org (Greg Kroah-Hartman) Date: Tue, 14 Nov 2017 13:38:56 +0100 Subject: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown In-Reply-To: <1510662098.3711.139.camel@linux.vnet.ibm.com> References: <20171108194626.GQ22894@wotan.suse.de> <20171109014841.GF7859@linaro.org> <1510193857.4484.95.camel@linux.vnet.ibm.com> <20171109044619.GG7859@linaro.org> <20171111023240.2398ca55@alans-desktop> <20171113174250.GA22894@wotan.suse.de> <20171113210848.4dc344bd@alans-desktop> <454.1510609487@warthog.procyon.org.uk> <1510662098.3711.139.camel@linux.vnet.ibm.com> Message-ID: <20171114123856.GA31142@kroah.com> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Tue, Nov 14, 2017 at 07:21:38AM -0500, Mimi Zohar wrote: > On Mon, 2017-11-13 at 14:09 -0800, Linus Torvalds wrote: > > On Mon, Nov 13, 2017 at 1:44 PM, David Howells 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. Then "verify" them with signatures that you generate yourself. Like dm-verify does for the partition that you put the firmware on. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html