Markus Gutschke wrote (in a message from Monday 9)
> [EMAIL PROTECTED] wrote:
> > Sep 9 18:36:13 [kernel] PAX: terminating task:
> > /usr/X11R6/bin/XFree86(XFree86):23363, uid/euid: 0/0, EIP: 08247BB8, ESP:
> > BFF31D0C
> > o
> >
> > So it IS the kernel's fault. Google says PAX controls security. I have
> > someplace to start now, but feel free to shout out the quick fix if you see
> > one.
>
> This is what is says in the PAX patch file:
>
> + Enabling this feature will enforce the non-executable flag on
> + memory pages thereby making it harder to execute 'foreign' code
> + in a program. This will also break programs that rely on the
> + old behaviour and expect that dynamically allocated memory via
> + the malloc() family of functions is executable (which it is not).
> + Notable examples are the XFree86 4.x server, the java runtime
> + and wine.
> +
Do the PAX patches allow mprotect() calls to make the allocated pages
executable ?
The XFree86 ELF loader currently miss a few mprotect() calls, but I've
a patch that adds the missing calls and make the loader happy again on
OpenBSD architectures that have non-executable heap now. It should
work too with PAX if it implements mprotect().
Matthieu
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
