Kernel 2.6.7

Discuss and suggest new grsecurity features

Kernel 2.6.7

Postby Hal9000 » Wed Jun 16, 2004 2:42 am

Ok, there's no patch for 2.6.6, and 2.6.7 fixes a security issue (2.6.6 fixes some too afaik).
Will there be a grsec patch soon or should i stick onto a patched 2.4.26-grsec? (don't even know if that's possible, given that the patch is for vanilla and not grsec kernel)
greetings
hal
Hal9000
 
Posts: 78
Joined: Wed Jun 16, 2004 2:40 am

Postby To » Wed Jun 16, 2004 10:47 pm

I'm still with 2.6.5 you can allways try it if you wish to go for a 2.6.

Tó
To
 
Posts: 22
Joined: Thu Dec 05, 2002 8:26 am

Postby Hal9000 » Wed Jun 16, 2004 11:37 pm

well, 2.6.5 has that security bug too...
so if i'm going for a 2.6 i'm gonna wait for a grsec patch for 2.6.7
if it doesn't come out then duh... i'm gonna have to stick with a 2.4.6-grsec+clear_cpu-patch (http://linux.bkbits.net:8080/linux-2.4/ ... Q7r9uDRvJQ)
Hal9000
 
Posts: 78
Joined: Wed Jun 16, 2004 2:40 am

2.6.5+Bug

Postby c0ldbyte » Fri Jun 25, 2004 11:50 pm

Hal9000 wrote:well, 2.6.5 has that security bug too...
so if i'm going for a 2.6 i'm gonna wait for a grsec patch for 2.6.7
if it doesn't come out then duh... i'm gonna have to stick with a 2.4.6-grsec+clear_cpu-patch (http://linux.bkbits.net:8080/linux-2.4/ ... Q7r9uDRvJQ)


There is a patch that was released that fixes the specific bug that you are talking about. In order to fix this, you should first apply the grsec patch and then apply the patch that changes the include files to fix the bug just to be sure that you arent overwriting any of grsec's changes. A comment on the bug can be found with links to the patch at http://www.kerneltrap.org/. yes thats the patch above.
c0ldbyte
 
Posts: 3
Joined: Fri Mar 14, 2003 8:57 pm

Postby spender » Sat Jun 26, 2004 9:06 am

http://grsecurity.net/~spender/grsecuri ... .6.7.patch

try that for now, official version will be released soon.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm

Postby FloFri » Mon Jun 28, 2004 2:38 am

thank you spender, now i can migrate to 2.6, too :)
FloFri
 
Posts: 5
Joined: Wed Jun 16, 2004 4:46 am

sparc64 compile error

Postby androsyn » Mon Jun 28, 2004 9:20 am

Got a compile error on sparc64 with the patch from above, not sure if this is a grsecurity issue or just a brokeness with 2.6.7 on sparc64. Below is part of the errors from the compile.

-Aaron

fs/compat.c: In function `compat_do_execve':
fs/compat.c:1134: warning: implicit declaration of function `gr_learn_resource'
fs/compat.c:1134:90: macro "atomic_read" passed 2 arguments, but takes just 1
fs/compat.c:1134: error: `atomic_read' undeclared (first use in this function)
fs/compat.c:1134: error: (Each undeclared identifier is reported only once
fs/compat.c:1134: error: for each function it appears in.)
fs/compat.c:1134: error: parse error before ';' token
fs/compat.c:1116: warning: unused variable `bprm'
fs/compat.c:1119: warning: unused variable `i'
fs/compat.c:1121: warning: unused variable `old_exec_file'
fs/compat.c:1122: warning: unused variable `old_acl'
fs/compat.c:1123: warning: unused variable `old_rlim'
fs/compat.c: At top level:
androsyn
 
Posts: 10
Joined: Mon Jun 28, 2004 9:02 am

Postby spender » Mon Jun 28, 2004 3:52 pm

I've uploaded a new patch that should resolve your problem.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm

more sparc64 issues..

Postby androsyn » Thu Jul 01, 2004 4:15 pm

It looks like pte_exprotect doesn't exist in inclue/asm-sparc64/pgtable.h, nor does it exist on sparc32. It's getting called from mm/mremap.c:136

-Aaron
androsyn
 
Posts: 10
Joined: Mon Jun 28, 2004 9:02 am

Postby spender » Thu Jul 01, 2004 4:37 pm

I've uploaded a new patch that corrects that problem. PaX was just recently ported to the 2.6 series, so non-i386 archs may not even compile. Any problems you run into however I'll be sure to pass on to the PaX team to fix.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm

Re: more sparc64 issues..

Postby PaX Team » Thu Jul 01, 2004 4:41 pm

androsyn wrote:It looks like pte_exprotect doesn't exist in inclue/asm-sparc64/pgtable.h, nor does it exist on sparc32. It's getting called from mm/mremap.c:136
change the #ifdef to depend on CONFIG_ARCH_TRACK_EXEC_LIMIT instead and it will compile.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Postby androsyn » Thu Jul 01, 2004 11:06 pm

That fixed it.

-Aaron
androsyn
 
Posts: 10
Joined: Mon Jun 28, 2004 9:02 am

Postby Cyrus » Sun Jul 04, 2004 11:45 am

Got this error on two different machines:

# gradm -E
Could not open /dev/grsec.
open: No such device or address

And the /dev/grsec is there, I made make install to gradm:

# ls -l /dev/grsec
crw--w--w- 1 root root 1, 10 Jul 4 18:10 /dev/grsec

I'm using 2.6.7 with the latest grsecurity-2.0.1
Cyrus
 
Posts: 7
Joined: Mon Mar 17, 2003 3:31 pm

Postby spender » Sun Jul 04, 2004 1:37 pm

You need to grab the newest CVS of gradm2. I had to change the device number for /dev/grsec so that it would not conflict with a device created by UML.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm

Postby Cyrus » Sun Jul 04, 2004 2:42 pm

Thanks a lot. Its working now
Cyrus
 
Posts: 7
Joined: Mon Mar 17, 2003 3:31 pm

Next

Return to grsecurity development