[grsec] followup about expand_stack
Carlos Carvalho
carlos at fisica.ufpr.br
Sun Jan 21 18:59:46 EST 2007
Brad Spengler (spender at grsecurity.net) wrote on 20 January 2007 15:07:
>On Sat, Jan 20, 2007 at 04:41:38PM -0200, Carlos Carvalho wrote:
>> What I should have added in the previous msg. is that I don't know if
>> the segfault is due to a failure in the kernel or in the poc code. I
>> don't know how to decipher the addresses... They show a kdb stack
>> trace that seems to point to the kernel. It must be checked if it's
>> true.
>
>The POC should have a signal handler in it for SIGSEGV. Once this is
>added, it'll execute fully.
I put signal(SIGSEGV, SIG_IGN); right above signal (SIGBUS, mouarf);
and it still just segfaults. How can a process be aborted by segfault
if it's ignored??? No BUG().
I'm using uderef, is it related?
More information about the grsecurity
mailing list