| 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: <20080131090839.7f610a6a@laptopd505.fenrus.org> Date: Thu, 31 Jan 2008 09:08:39 -0800 From: Arjan van de Ven <arjan@...radead.org> To: Jan Engelhardt <jengelh@...putergmbh.de> Cc: linux-kernel@...r.kernel.org, davej@...hat.com, mingo@...e.hu, tglx@...x.de, hpa@...or.com Subject: Re: [PATCH] x86: introduce /dev/mem restrictions with a config option On Thu, 31 Jan 2008 17:53:04 +0100 (CET) Jan Engelhardt <jengelh@...putergmbh.de> wrote: > > On Jan 30 2008 12:48, Arjan van de Ven wrote: > >Subject: [PATCH] x86: introduce /dev/mem restrictions with a config > >option > > > >This patch introduces a restriction on /dev/mem: Only non-memory can > >be read or written unless the newly introduced config option is set. > > Would not it be nicer to add a /dev/pcimem that implements the given > restrictive semantics? > > Maybe it's just wishful thinking, but I am dreaming of an > unprivileged X, and /dev/pcimem (owned by an 'x11' user or so) would > be a step in that direction. /dev/pcimem is wrong; X can use the exact bar in sysfs already. This is more for compatibility with legacy X -- If you want to reach me at my work email, use arjan@...ux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.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