| 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: Tue, 19 May 2015 13:40:38 -0700 From: "Luis R. Rodriguez" <mcgrof@...e.com> To: linux-security-module <linux-security-module@...r.kernel.org>, James Morris <james.l.morris@...cle.com>, serge@...lyn.com Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-wireless <linux-wireless@...r.kernel.org>, David Howells <dhowells@...hat.com>, Kyle McMartin <kyle@...nel.org>, David Woodhouse <david.woodhouse@...el.com>, Seth Forshee <seth.forshee@...onical.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Joey Lee <jlee@...e.de>, Rusty Russell <rusty@...tcorp.com.au>, zohar@...ux.vnet.ibm.com, Konstantin Ryabitsev <mricon@...nel.org> Subject: Re: [RFD] linux-firmware key arrangement for firmware signing On Tue, May 19, 2015 at 1:02 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote: > Other than this last nitpick, any other concerns or recommendations ? Oh one more thing. I think we should decide on a digest algorithm we'd wish to be used for linux-firmware signing, distributions likely will want to just have this enabled =y in their kernel unless of course proper care is taken to also make sure such module is available early for initramfs uses. The digest algorithm can be different than what any distribution uses for their own module signing digest. 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