On Tuesday, December 20, 2011 12:55:49 PM Max Williams wrote: One piece of information is missing. The enforcement of the audit policy is done by the kernel. What do you get for uname -r? -Steve

On Wednesday, December 21, 2011 07:17:01 AM Max Williams wrote: Initial assessment, the kernel patch that discards events might only work on open(2). Eric is looking to see if this can be safely broadened. -Steve

Hi All, Sorry to bug you but is this issue I'm having a bug or have I made a mistake in the rules? Is there another way I could exclude this directory from auditd? We have licenses for these servers so I could open a case if need be. Many thanks, Max -----Original Message----- From: linux-audit-bounces(a)redhat.com [mailto:linux-audit-bounces@redhat.com] On Behalf Of Max Williams Sent: 06 January 2012 17:26 To: linux-audit(a)redhat.com Subject: RE: Path ignored but syscall event still logged Any update on this Steve? The other ignore rules seem to work, just not that one. Thanks, Max -----Original Message----- From: Steve Grubb [mailto:sgrubb@redhat.com] Sent: 21 December 2011 19:25 To: linux-audit(a)redhat.com Cc: Max Williams Subject: Re: Path ignored but syscall event still logged On Wednesday, December 21, 2011 07:17:01 AM Max Williams wrote: Initial assessment, the kernel patch that discards events might only work on open(2). Eric is looking to see if this can be safely broadened. -Steve ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________ -- Linux-audit mailing list Linux-audit(a)redhat.com https://www.redhat.com/mailman/listinfo/linux-audit ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________

OK, thanks for clarifying Steve. I'll open a support case with RH. Cheers, Max -----Original Message----- From: Steve Grubb [mailto:sgrubb@redhat.com] Sent: 12 January 2012 15:04 To: linux-audit(a)redhat.com Cc: Max Williams Subject: Re: Path ignored but syscall event still logged On Thursday, January 12, 2012 09:45:59 AM Max Williams wrote: The preliminary investigation was its a kernel bug. It needs to be checked in more detail to see what the fix is. -Steve ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________

Hi Steve, Thanks for the reply. Yes and yes: [root@host1 ~]# mount|grep ab /dev/mapper/VolGroupCF00-abf_graph on /naab2 type ext4 (rw) /dev/mapper/VolGroupCF01-abf_icff on /naab1 type ext4 (rw) [root@host1 ~]# ll /|grep ab lrwxrwxrwx 1 root root 6 May 9 2011 ab1 -> /naab1 lrwxrwxrwx 1 root root 6 May 9 2011 ab2 -> /naab2 drwxrwx--- 5 root ab_users 4096 May 20 2011 naab1 drwxrwx--- 6 root ab_users 4096 Jun 29 2011 naab2 [root@host1 ~]# How does that affect the the rule, which was for the actual mount point, not the sym link? LIST_RULES: exit,never dir=/naab1 (0x6) syscall=all Cheers, Max -----Original Message----- From: Steve Grubb [mailto:sgrubb@redhat.com] Sent: 13 January 2012 14:46 To: linux-audit(a)redhat.com Cc: Max Williams Subject: Re: Path ignored but syscall event still logged On Thursday, January 12, 2012 09:45:59 AM Max Williams wrote: Looking back at the original... /naab1/serial/data/dir1/serial/dir2/abc_load/temp/some-app/.WORK- serial/1568280a-4eef7e3f-3873 Are there any mount points in that path? Or any symlinks pointing to other disk devices? Thanks, -Steve ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________

Hi Steve, There are no mount points anywhere in that path apart from at the top level. I'm 99% sure there were no sym links either but that path has since been removed so I can't be completely sure. To make things a bit simpler I can reproduce it with a much shorter path and definitely no sym links within the path: [root@hostb001 ~]# auditctl -l LIST_RULES: exit,always dir=/etc/audit (0xa) perm=wa key=auditd_configuration LIST_RULES: exit,always dir=/etc/audisp (0xb) perm=wa key=auditd_configuration LIST_RULES: exit,always watch=/etc/libaudit.conf perm=wa key=auditd_configuration LIST_RULES: exit,always watch=/etc/sysconfig/auditd perm=wa key=auditd_configuration LIST_RULES: exit,never dir=/etc/lvm/cache (0xe) syscall=all LIST_RULES: exit,never dir=/opt (0x4) syscall=all LIST_RULES: exit,never dir=/tmp (0x4) syscall=all LIST_RULES: exit,never dir=/naab1 (0x6) syscall=all LIST_RULES: exit,never dir=/naab2 (0x6) syscall=all LIST_RULES: exit,never dir=/ab1 (0x4) syscall=all LIST_RULES: exit,never dir=/ab2 (0x4) syscall=all LIST_RULES: exit,never dir=/usr/openv/netbackup (0x14) syscall=all LIST_RULES: exit,always perm=a key=file_attributes LIST_RULES: exit,always arch=3221225534 (0xc000003e) a1=1074292226 (0x40086602) key=file_attributes syscall=ioctl LIST_RULES: exit,always arch=3221225534 (0xc000003e) a1=-2146933247 (0x80086601) key=file_attributes syscall=ioctl LIST_RULES: exit,always arch=3221225534 (0xc000003e) exit=-13 (0xfffffff3) key=invalid_logical_access syscall=open LIST_RULES: exit,always dir=/bin (0x4) perm=wa key=bin_modification LIST_RULES: exit,always dir=/boot (0x5) perm=wa key=boot_modification LIST_RULES: exit,always dir=/etc (0x4) perm=wa key=etc_modification LIST_RULES: exit,always dir=/home (0x5) perm=wa key=home_modification LIST_RULES: exit,always dir=/lib (0x4) perm=wa key=lib_modification LIST_RULES: exit,always dir=/lib64 (0x6) perm=wa key=lib64_modification LIST_RULES: exit,always dir=/root (0x5) perm=wa key=root_modification LIST_RULES: exit,always dir=/sbin (0x5) perm=wa key=sbin_modification LIST_RULES: exit,always dir=/usr (0x4) perm=wa key=usr_modification LIST_RULES: exit,always dir=/var/spool/at (0xd) perm=wa key=misc_var LIST_RULES: exit,always dir=/var/spool/cron (0xf) perm=wa key=misc_var LIST_RULES: exit,never dir=/var (0x4) syscall=all LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=dir_operations syscall=mkdir,rmdir,unlinkat LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=link_operation syscall=rename,link,unlink,symlink LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=special_device_creation syscall=mknod,mknodat LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=mount_operation syscall=mount,umount2 LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=kernel_module syscall=create_module,init_module,delete_module LIST_RULES: exclude,always msgtype=CRED_ACQ (0x44f) LIST_RULES: exclude,always msgtype=CRED_DISP (0x450) LIST_RULES: exclude,always msgtype=CRYPTO_KEY_USER (0x964) LIST_RULES: exclude,always msgtype=CRYPTO_SESSION (0x967) LIST_RULES: exclude,always msgtype=LOGIN (0x3ee) LIST_RULES: exclude,always msgtype=USER_ACCT (0x44d) LIST_RULES: exclude,always msgtype=USER_AUTH (0x44c) LIST_RULES: exclude,always msgtype=USER_CMD (0x463) LIST_RULES: exclude,always msgtype=USER_END (0x452) LIST_RULES: exclude,always msgtype=USER_LOGIN (0x458) LIST_RULES: exclude,always msgtype=USER_START (0x451) [root@hostb001 ~]# [root@hostb001 ~]# mount|grep naab1 /dev/mapper/VolGroupB01-abb_landing on /naab1 type ext4 (rw) [root@hostb001 ~]# [root@hostb001 ~]# ls -l /|grep naab1 lrwxrwxrwx 1 root root 6 Jun 6 2011 ab1 -> /naab1 drwxr-x--- 6 app app_users 4096 Aug 23 13:23 naab1 [root@hostb001 ~]# [root@hostb001 ~]# touch /naab1/temp-file [root@hostb001 ~]# chmod 600 /naab1/temp-file [root@hostb001 ~]# [root@hostb001 ~]# tail -3 /var/log/audit/audit.log node=hostb001.domain type=SYSCALL msg=audit(1326711394.421:3737872): arch=c000003e syscall=268 success=yes exit=0 a0=ffffffffffffff9c a1=60d1d0 a2=180 a3=0 items=1 ppid=20688 pid=32510 auid=7382 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=49941 comm="chmod" exe="/bin/chmod" key="file_attributes" node=hostb001.domain type=CWD msg=audit(1326711394.421:3737872): cwd="/root" node=hostb001.domain type=PATH msg=audit(1326711394.421:3737872): item=0 name="/naab1/temp-file" inode=12 dev=fd:0d mode=0100600 ouid=0 ogid=0 rdev=00:00 [root@hostb001 ~]# Does this make it a bit clearer? I look forward to your reply. Many thanks, Max -----Original Message----- From: Steve Grubb [mailto:sgrubb@redhat.com] Sent: 13 January 2012 18:52 To: linux-audit(a)redhat.com Cc: Max Williams Subject: Re: Path ignored but syscall event still logged On Friday, January 13, 2012 11:46:58 AM Max Williams wrote: Its OK for the top level dir to be a mount point. However, what about everything under it? /naab1/serial/data/dir1/serial/dir2/abc_load/temp/some-app/.WORK-serial/1568280a-4eef7e3f-3873 Could data or dir1 be a mount point? If anything under /naab1 is a mount point, then you have to tell the kernel to treat it as equivalent to the parent dir that you have the rule on. For example, suppose data was in fact a moint point and you mounted /dev/sda1 onto it. You would need to add the follwoing to your audit rules: -q /naab1/serial/data,/dev/sda1 As for symlinks, I'm not sure that a recursive watch will follow the symlink. If for example, some-app was a symlink to /opt/some-app, I am pretty sure the watch will not follow over to the other device. You would have to add a watch on /opt/some-app to get events. The same thing applies for suppressing events. -Steve > Linux-audit@redhat.com<mailto:Linux-audit@redhat.com ________________________________________________________________________ In order to protect our email recipients, Betfair Group use SkyScan from MessageLabs to scan all Incoming and Outgoing mail for viruses. ________________________________________________________________________