Re: Xfree 4.2.x Radeon and gr security linux kernel

2003-03-09 Thread Klaus Kusche
[snip] * Are the r/w accesses to the BIOS and to the first page really necessary, or could they be eliminated or at least made optional? I would be willing to trade in e.g. some autoconfiguration features like DDC for the additional security! All /dev/mem mappings appear to be r/w simply

Re: Xfree 4.2.x Radeon and gr security linux kernel

2003-03-09 Thread Klaus Kusche
Klaus Kusche wrote: I analyzed Xfree's behaviour with strace. In addition to the two kinds of mmap listed above (which are allowed), Xfree makes many r/w mmap calls to the following two areas of memory (which are blocked by grsec and make Xfree fail): * r/w mmaps of the BIOS (0xf /

Re: Xfree 4.2.x Radeon and gr security linux kernel

2003-03-08 Thread Dr. David Alan Gilbert
* Klaus Kusche ([EMAIL PROTECTED]) wrote: I analyzed Xfree's behaviour with strace. In addition to the two kinds of mmap listed above (which are allowed), Xfree makes many r/w mmap calls to the following two areas of memory (which are blocked by grsec and make Xfree fail): * r/w mmaps of

Re: Xfree 4.2.x Radeon and gr security linux kernel

2003-03-08 Thread Marc Aurele La France
On Sat, 8 Mar 2003, Klaus Kusche wrote: I use a Sony notebook with an ATI M7 chip, Xfree 4.2.x with the radeon driver, and a linux kernel 2.4.20 with the gr security patches 1.9.8. When the /dev/kmem protection in grsec is enabled, Xfree fails to start. This protection disables all writes