1 |
Hi! |
2 |
|
3 |
On Thu, Apr 02, 2009 at 11:17:10PM +0200, pageexec@××××××××.hu wrote: |
4 |
> can you strace bash/etc to see what happens? probably we'll see what runs |
5 |
|
6 |
how do I can strace process N1? |
7 |
PaX doesn't kill bash if it executed not as process N1. |
8 |
|
9 |
> against the MPROTECT restricions. my guess is either textrels or gnu_stack |
10 |
> (compare scanelf -lpqRte on your systems). |
11 |
|
12 |
it's same on all servers: |
13 |
|
14 |
# scanelf -lpqRte |
15 |
TEXTREL /usr/lib/perl5/site_perl/5.8.8/i686-linux/auto/Math/Pari/Pari.so |
16 |
RWX --- --- /usr/lib/paxtest/writetext |
17 |
RWX --- --- /usr/lib/paxtest/shlibbss |
18 |
RWX --- --- /usr/lib/paxtest/mprotanon |
19 |
RWX --- --- /usr/lib/paxtest/mprotdata |
20 |
RWX --- --- /usr/lib/paxtest/mprotheap |
21 |
RWX --- --- /usr/lib/paxtest/rettofunc1 |
22 |
RWX --- --- /usr/lib/paxtest/rettofunc2 |
23 |
RWX --- --- /usr/lib/paxtest/execbss |
24 |
RWX --- --- /usr/lib/paxtest/execstack |
25 |
RWX --- --- /usr/lib/paxtest/mprotshbss |
26 |
RWX --- --- /usr/lib/paxtest/mprotstack |
27 |
RWX --- --- /usr/lib/paxtest/mprotbss |
28 |
RWX --- --- /usr/lib/paxtest/anonmap |
29 |
RWX --- --- /usr/lib/paxtest/mprotshdata |
30 |
RWX --- --- /usr/lib/paxtest/execdata |
31 |
RWX --- --- /usr/lib/paxtest/execheap |
32 |
RWX --- --- /usr/lib/paxtest/rettofunc1x |
33 |
RWX --- --- /usr/lib/paxtest/rettofunc2x |
34 |
RWX --- --- /usr/lib/paxtest/shlibdata |
35 |
RWX --- --- /usr/inferno/Linux/386/bin/emu |
36 |
RWX --- --- /usr/inferno/Linux/386/bin/emu-g |
37 |
|
38 |
> btw, why are you using SEGMEXEC on your core2? |
39 |
|
40 |
Hmm. You think I should use PAGEEXEC instead? According to help in linux |
41 |
kernel SEGMEXEC looks more suitable for Core2Duo and Xeon E5310... |
42 |
|
43 |
In help for PAGEEXEC it doesn't recommended for P4 and there is nothing |
44 |
about newest processors, so I suppose PAGEEXEC may not be a good choice. |
45 |
|
46 |
After your question I've re-read help, and notice "i386 with hardware |
47 |
non-executable bit support" item at end of list with less usual archs like |
48 |
avr32, sparc, etc. If that was said about Core/Xeon too, then there |
49 |
probably little usability issue with that help. ;-) |
50 |
|
51 |
-- |
52 |
WBR, Alex. |