2.6.18.3

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

2.6.18.3

Postby Raf256 » Wed Nov 22, 2006 5:31 am

Hi,
did anyone tested yet if the last grsec patch works fine with 2.6.18.3 kernel?
Raf256
 
Posts: 72
Joined: Mon Sep 19, 2005 8:38 pm

Re: 2.6.18.3

Postby kolargol » Wed Nov 22, 2006 7:18 am

Raf256 wrote:Hi,
did anyone tested yet if the last grsec patch works fine with 2.6.18.3 kernel?


yes it is working but grsec set to high still kills init (even when used with nosep kernel option)
kolargol
 
Posts: 36
Joined: Thu Sep 23, 2004 5:19 am

Postby tosh » Wed Nov 22, 2006 12:40 pm

2.6.18.3 and grsecurity-2.1.9-2.6.18.2-200611100917 - no problems here.

kolargol, I doubt it is PaX problem. Test yourself:
Code: Select all
readelf -e /sbin/init | grep STACK

this should return something like:
Code: Select all
GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RW  0x4

but if you get RWX in place RW from my output you will have your answer.

PaX deny stack been read, write and executable in programs.
tosh
 
Posts: 19
Joined: Mon Apr 10, 2006 9:13 pm

Postby Raf256 » Fri Nov 24, 2006 10:24 am

If patch works with 2.6.8.13 then perhaps the file in ~spender should be renamed officially?
Raf256
 
Posts: 72
Joined: Mon Sep 19, 2005 8:38 pm

Postby kolargol » Sat Nov 25, 2006 12:27 pm

tosh wrote:2.6.18.3 and grsecurity-2.1.9-2.6.18.2-200611100917 - no problems here.

kolargol, I doubt it is PaX problem. Test yourself:
Code: Select all
readelf -e /sbin/init | grep STACK

this should return something like:
Code: Select all
GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RW  0x4

but if you get RWX in place RW from my output you will have your answer.

PaX deny stack been read, write and executable in programs.


actually i got:
Code: Select all
GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RW  0x4


so no X flag there...
kolargol
 
Posts: 36
Joined: Thu Sep 23, 2004 5:19 am


Return to grsecurity support