| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 May 2015 20:46:23 +0200 From: "Luis R. Rodriguez" <mcgrof@...e.com> To: "Luis R. Rodriguez" <mcgrof@...not-panic.com> Cc: ming.lei@...onical.com, rusty@...tcorp.com.au, torvalds@...ux-foundation.org, dhowells@...hat.com, seth.forshee@...onical.com, linux-kernel@...r.kernel.org, pebolle@...cali.nl, linux-wireless@...r.kernel.org, gregkh@...uxfoundation.org, jlee@...e.com, tiwai@...e.de, casey@...aufler-ca.com, keescook@...omium.org, mjg59@...f.ucam.org, akpm@...ux-foundation.org, Kyle McMartin <kyle@...nel.org> Subject: Re: [RFC v2 6/6] firmware: add firmware signature checking support On Wed, May 13, 2015 at 11:23:56AM -0700, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <mcgrof@...e.com> > > As with module signing, we do a very simple search for a > particular string appended to the firmware. There's both a > config option and a boot parameter which control whether we > accept or fail with unsigned firmware and firmware that are > signed with an unknown key. > > If firmware signing is enabled, the kernel will be tainted > if a firmware is loaded that is unsigned or has a signature > for which we don't have the key. Sorry this commit log is obviously still from the v1, the cover letter addresses the changes best... Luis -- 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