| 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: <20130902062310.GA28598@console-pimps.org> Date: Mon, 2 Sep 2013 07:23:10 +0100 From: Matt Fleming <matt@...sole-pimps.org> To: David Woodhouse <dwmw2@...radead.org> Cc: James Bottomley <James.Bottomley@...senPartnership.com>, Matthew Garrett <mjg59@...f.ucam.org>, "John W. Linville" <linville@...driver.com>, linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org Subject: Re: UEFI Plugfest 2013 -- New Orleans On Mon, 19 Aug, at 09:09:54PM, David Woodhouse wrote: > 3. Even if we can't *remove* the code, sometimes we can disable it at > runtime if we detect the BIOS is new enough that it shouldn't be broken. Yes, this is definitely something we should be looking to implement. It seems likely to me that we're eventually going to start hitting issues supporting the latest UEFI firmware because of the workarounds we're currently carrying in the kernel. The EDKII folks are surprised time and time again to hear of the hoops we jump through in the kernel to support buggy implementations. It's only going to be a matter of time until we *have* to disable some our workarounds in order to boot the most recent incarantions of UEFI. Not least because carrying these workarounds unconditionally and indefinitely severely limits our ability to innovate. -- Matt Fleming, Intel Open Source Technology Center -- 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