| 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
| ||
|
Message-ID: <10137.1432225434@warthog.procyon.org.uk> Date: Thu, 21 May 2015 17:23:54 +0100 From: David Howells <dhowells@...hat.com> To: Seth Forshee <seth.forshee@...onical.com> Cc: dhowells@...hat.com, "Luis R. Rodriguez" <mcgrof@...e.com>, linux-security-module@...r.kernel.org, james.l.morris@...cle.com, serge@...lyn.com, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, Kyle McMartin <kyle@...nel.org>, David Woodhouse <david.woodhouse@...el.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Joey Lee <jlee@...e.de>, Rusty Russell <rusty@...tcorp.com.au>, zohar@...ux.vnet.ibm.com, mricon@...nel.org Subject: Re: [RFD] linux-firmware key arrangement for firmware signing Seth Forshee <seth.forshee@...onical.com> wrote: > > Relying on UEFI presents three problems, though: (1) the system admin has to > > manually, as far as I'm aware, inform the BIOS; (2) the UEFI storage is > > limited; and (3) not all systems have UEFI. > > Yeah, that doesn't really sound like a good solution. Not all users are > sys admins. Yeah. We don't really want to recommend they go meddling lest they brick their machine by triggering a bug in their BIOS. Not that there *are* any buggy BIOSes of course;-) David -- 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