strange behavior of grsecurity

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

strange behavior of grsecurity

Postby msw » Sun Nov 07, 2004 10:04 pm

hello.

on my system, i use a 2.4.27-kernel with the grsecurity-2.0.1 patch (compiled with gcc 2.95.4).
i'm using one default rule for all users on the system.
recently i noticed that it was possible for a regular user to send signals to the sshd process, which is owned by root. this behavior seems only to apply on processes which have the p-flag (protected process) set. also only if the acl-system is activated via gradm -E regular users can kill such protected root-processes without any restriction, otherwise "operation not permitted" error occurs. +CAP_KILL has not been defined in the acl.
further i noticed that root can kill any protected process even if the acl-system is active.
i've been working with grsecurity in earlier kernels and never faced such a behavior.

maybe i configured it in a wrong way?

thank you for any hint.
msw
 
Posts: 8
Joined: Sat Sep 20, 2003 9:36 pm

Postby spender » Tue Nov 09, 2004 4:56 pm

The fix has been applied to kernel/signal.c in current CVS.

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


Return to grsecurity support

cron