x86: introduce /dev/mem restrictions with a config option
nice !
did you think about some boot-time param , e.g. "insecure-devmem" or something like that?
recompiling kernel is time consuming.....
From: Arjan van de Ven <[email protected]>
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.
The X server needs access to /dev/mem for the PCI space, but it doesn't need access to memory; both the file permissions and SELinux permissions of /dev/mem just make X effectively super-super powerful. With the exception of the BIOS area, there's just no valid app that uses /dev/mem on actual memory. Other popular users of /dev/mem are rootkits and the like.
(note: mmap access of memory via /dev/mem was already not allowed since a really long time)
People who want to use /dev/mem for kernel debugging can enable the config option.
The restrictions of this patch have been in the Fedora and RHEL kernels for at least 4 years without any problems.
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
Quoted 6 lines · On Thu, 31 Jan 2008 15:04:28 +0100 [email protected] wrote:
nice !
did you think about some boot-time param , e.g. "insecure-devmem" or something like that?
recompiling kernel is time consuming.....
given that this has been in fedora/rhel for 5 years with no complaints... it's extremely rare, and if you are someone who's going to use it to do some weird form of kernel debugging, you already know that way ahead of time, when you compile your kernel.
(Note: I don't know of any tools that do kernel debugging this way. At all)