How do I implement grsecurity?

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

How do I implement grsecurity?

Postby neverclear » Sun Oct 03, 2004 4:40 pm

I want to implement it but there arent any real instructions for how to patch it on the site anywhere. Can anyone point me in the right direction?
neverclear
 
Posts: 6
Joined: Sun Oct 03, 2004 4:38 pm

Postby neverclear » Sun Oct 03, 2004 8:01 pm

k i figured it out on my own
but my kernel is hanging at "Uncompressing Linux...Ok, booting the kernel"

I checked syslog and it gives this error....

Oct 3 17:14:48 slack10 kernel: VFS: Mounted root (ext3 filesystem) readonly.
Oct 3 17:14:48 slack10 kernel: Warning: unable to open an initial console.
Oct 3 17:14:48 slack10 kernel: grsec: time set by /sbin/hwclock[hwclock:26705] uid/euid:0/0 gid/egid:0/0, parent /etc/rc.d/$
Oct 3 17:14:48 slack10 kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
Oct 3 17:14:48 slack10 kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg>$
Oct 3 17:14:57 slack10 modprobe: modprobe: Can't locate module char-major-4
Oct 3 17:14:57 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:15444] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:14:57 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:14:57 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:445] uid/euid:0/0 gid/egid:0/0, paren$
Oct 3 17:14:57 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:14:57 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:20578] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:14:57 slack10 kernel: grsec: more alerts, logging disabled for 10 seconds
Oct 3 17:15:07 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:16492] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:15:07 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:15:07 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:17273] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:15:07 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:7390] uid/euid:0/0 gid/egid:0/0, pare$
Oct 3 17:15:07 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:15:07 slack10 kernel: grsec: more alerts, logging disabled for 10 seconds
Oct 3 17:15:17 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:4021] uid/euid:0/0 gid/egid:0/0, pare$
Oct 3 17:15:17 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:15:17 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:16025] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:15:17 slack10 kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by /sb$
Oct 3 17:15:17 slack10 kernel: grsec: signal 11 sent to /sbin/insmod.old[modprobe.old:13612] uid/euid:0/0 gid/egid:0/0, par$
Oct 3 17:15:17 slack10 kernel: grsec: more alerts, logging disabled for 10 seconds


some of the line is cut off because the line is so long but im stumped is to what im suppose to do to fix this.

i setup the .config for grsecurity at HIGH security.
neverclear
 
Posts: 6
Joined: Sun Oct 03, 2004 4:38 pm


Return to grsecurity support

cron