How to log GrSec to syslog?

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

How to log GrSec to syslog?

Postby sekko » Thu Aug 03, 2006 5:59 am

Hi all,
I'm using grsecurity after quite a long time (hem... I had a 2.4.26... so can imagine how long it is!).
I remember that any "deny" was logged via syslogd so that I could easily fix any ACL in few minutes. Now I'm using 2.4.33rc2 with latest grsec patch, but I cannot find the way to enable syslogging anymore: messages go only to console, but it's some KMs far from my workplace... so you can imagine that it not easy to debug/solve the situation! :roll:
Is there a new way to enable loggin of all grsec action? I read in latest changelog that it "should be" a sysctl-tunable action now... is it right? I cannot find nothing about it in official documentation.

Any help will be apreciated!
Thanks :lol:
sekko
 
Posts: 13
Joined: Mon Apr 05, 2004 5:52 am

Postby Thrawn » Thu Aug 03, 2006 7:01 am

Have you changed your syslog config? Does it log any other kernel messages?
Thrawn
 
Posts: 35
Joined: Wed Nov 23, 2005 9:54 am

Postby sekko » Thu Aug 03, 2006 8:00 am

Your hint about the kernel messages has been providential: I found that the syslogd script in init.d directory did _not_ start klogd. To solve the problem I simply had to start klogd.

Sorry for the stupid question. :roll:
sekko
 
Posts: 13
Joined: Mon Apr 05, 2004 5:52 am


Return to grsecurity support