Re: grsecurity interfering with the parrot JIT/build

2004-10-19 Thread Christian Jaeger
At 14:47 Uhr +0200 16.10.2004, Leopold Toetsch wrote: Anyway, JIT memOk. There is a test in config/auto/jit/test_exec_openbsd.in, Ok, I've looked at the test_exec_linux source, and tried it out separately; it's clear what happens to me now: I've enabled the following GrSecurity option, which make

Re: grsecurity interfering with the parrot JIT/build

2004-10-19 Thread Leopold Toetsch
Christian Jaeger wrote: Ok, I've looked at the test_exec_linux source, and tried it out separately; it's clear what happens to me now: I've enabled the following GrSecurity option, which makes the mprotect system call fail with a permission error - the test even outputs this as the line "failur

Re: grsecurity interfering with the parrot JIT/build

2004-10-16 Thread Leopold Toetsch
Christian Jaeger <[EMAIL PROTECTED]> wrote: > Hello > I'm using Linux/x86 with the Grsecurity.org patch applied, which is > enforcing page execution permissions (PAX) unless you turn them off > on a binary using the "chpax" userspace tool. [ ... ] > The correct solution would be to mark the resp

grsecurity interfering with the parrot JIT/build

2004-10-16 Thread Christian Jaeger
Hello I'm using Linux/x86 with the Grsecurity.org patch applied, which is enforcing page execution permissions (PAX) unless you turn them off on a binary using the "chpax" userspace tool. This means - unless you turn it off - an executable that is executing code in a page which is not marked as