| 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, 4 Sep 2012 17:16:58 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, linux-efi@...r.kernel.org Subject: Re: [PATCH 03/11] x86: Lock down IO port access in secure boot environments On Tue, Sep 04, 2012 at 05:16:03PM +0100, Alan Cox wrote: > On Tue, 4 Sep 2012 11:55:09 -0400 > Matthew Garrett <mjg@...hat.com> wrote: > > > IO port access would permit users to gain access to PCI configuration > > registers, which in turn (on a lot of hardware) give access to MMIO register > > space. This would potentially permit root to trigger arbitrary DMA, so lock > > it down by default. > > You've missed a load of others, all over the kernel, let alone getting > into devices with other paths to firmware reprogramming of which there > are many. > > You need to enforce signing on request_firmware for example, and sign > every firmware. Sure, but that's going to depend on the module signing code which hasn't landed yet. But for the most part, devices that are designed for these platforms will only accept signed firmware at the device level. -- Matthew Garrett | mjg59@...f.ucam.org -- 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