Description of problem: While running RHTS tests. We see some AVC denials reported by tests. After looking into the issue it is the test running causing the AVC denials. It is a background cron job I believe it is logwatch. Version-Release number of selected component (if applicable): logwatch-7.3-6.el5 How reproducible: Seemingly random Steps to Reproduce: 1. Not sure Actual results: Saw this first with RHEL5.3-Server-20081203.0 /sbin/ausearch -sv no -m AVC -m USER_AVC -m SELINUX_ERR -ts 12/9/2008 1:1:32 ---- time->Tue Dec 9 01:01:42 2008 type=SYSCALL msg=audit(1228802502.831:24): arch=14 syscall=5 success=no exit=-13 a0=1005c948 a1=10241 a2=1b6 a3=0 items=0 ppid=30662 pid=30665 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="perl" exe="/usr/bin/perl" subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1228802502.831:24): avc: denied { write } for pid=30665 comm="perl" name="services" dev=dm-0 ino=2785761 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=dir This avc shows logwatch trying to write to a directory named services that is labeled etc_t. This would indicate that it is somewhere under /etc. During Don's kernel testing last night we saw this again. RHEL5.4-Server-20090526.nightly time->Wed May 27 00:27:40 2009 type=SYSCALL msg=audit(1243398460.748:15): arch=14 syscall=5 success=no exit=-13 a0=1005c550 a1=10241 a2=1b6 a3=0 items=0 ppid=32608 pid=32611 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="perl" exe="/usr/bin/perl" subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1243398460.748:15): avc: denied { write } for pid=32611 comm="perl" name="services" dev=dm-0 ino=8741914 scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=dir Expected results: Additional info: Spoke with Dan briefly he thinks this is possibly a leaked file descriptor.
Hello, please could you add me the id of the test you have done. I want to reproduce the problem myself to find out where the problem is. Thanks.
*** This bug has been marked as a duplicate of bug 475562 ***
*** Bug 507622 has been marked as a duplicate of this bug. ***
*** Bug 508012 has been marked as a duplicate of this bug. ***