| 1 |
On 29 Sep 2008 at 19:57, Alex Efros wrote: |
| 2 |
|
| 3 |
> Didn't you think it's good idea to trace this issue? It may be a bug in |
| 4 |
> grsec... anyway, usual hardened system shouldn't produce such a warnings |
| 5 |
> in logs just because somebody call exec() from perl script or use qmail. |
| 6 |
|
| 7 |
sorry, i was busy with everything, didn't have time to look into this. now |
| 8 |
that i did, i don't quite get what happens here. thing is, if RLIMIT_STACK |
| 9 |
is overstepped, the given process should get a segfault on all execution |
| 10 |
paths that i checked yet it clearly hasn't happened according to the strace. |
| 11 |
so that leaves one option open, some bug/misreporting by grsec (or maybe PaX?) |
| 12 |
but then looking at the code, i don't see how that would happen either... can |
| 13 |
you tell me which kernel this happened on (or more precisely, which grsec |
| 14 |
version it was) and whether you can still reproduce it with the latest grsec |
| 15 |
(or PaX) test patch? |
Archives