From: Robert Evans <bob.evans@jhuapl.edu>
To: linux-audit@redhat.com
Subject: Why aren't SYSCALLS being logged in CentOS kernel (any ideas?)
Date: Fri, 31 Aug 2007 11:40:07 -0400 [thread overview]
Message-ID: <46D83657.1060503@jhuapl.edu> (raw)
Hi,
I'm using CentOS, kernel 2.6.18-8.el5. I've compiled audit-1.5.6-1 and I'm
getting USER_AUTH events (logins, su, etc...) but I'm not seeing any syscall events.
My test audit.rules works fine in RHEL4, Suse10 and Fedora, but doesn't seem to
generate any syscall events in CentOS 5. For testing purposes, I'm using the
following in audit.rules:
# Log execute failures
-a exit,always -S execve -F success!=1 -F exit!=-2 -F exit!=-20 -F exit!=-17 -F
exit!=-6
# Log administrative functions
-a exit,always -S reboot -S clock_settime -S settimeofday -S adjtimex -S
setdomainname -S sethostname -S reboot -S mount -S umount2
-a exit,always -S swapon -S swapoff -S create_module -S delete_module -S
quotactl -F success!=1
# Log Read/Write functions
-a exit,always -S open -S creat -S link -S symlink -S truncate -S ftruncate -S
mknod -S rename -F success!=1 -F exit!=-2 -F exit!=-20 -F exit!=-17 -F exit!=-6
# Log file removal failures
-a exit,always -S unlink -S rmdir -F success!=1 -F exit!=-2 -F exit!=-20 -F
exit!=-17 -F exit!=-6
# Log file modification failures
-a exit,always -S chmod -S chown -S lchown -S fchmod -S fchown -F success!=1 -F
exit!=-2 -F exit!=-20 -F exit!=-17 -F exit!=-6
# Add watches for reboot stuff...
-w /sbin/init -p x -k runlevel
-w /sbin/telinit -p x -k runlevel
-w /sbin/halt -p x -k runlevel
-w /sbin/poweroff -p x -k runlevel
-w /sbin/reboot -p x -k runlevel
-w /sbin/shutdown -p x -k runlevel
Any ideas?
Bob
next reply other threads:[~2007-08-31 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 15:40 Robert Evans [this message]
2007-08-31 16:02 ` Why aren't SYSCALLS being logged in CentOS kernel (any ideas?) Steve Grubb
2007-08-31 17:35 ` Robert Evans
2007-08-31 17:40 ` Steve Grubb
2007-08-31 17:51 ` Robert Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46D83657.1060503@jhuapl.edu \
--to=bob.evans@jhuapl.edu \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox