Summary: SELinux is preventing /sbin/runuser "create" access . Detailed Description: SELinux denied access requested by runuser. It is not expected that this access is required by runuser and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:logrotate_t:s0-s0:c0.c1023 Target Context system_u:system_r:logrotate_t:s0-s0:c0.c1023 Target Objects None [ netlink_audit_socket ] Source runuser Source Path /sbin/runuser Port <Unknown> Host (removed) Source RPM Packages coreutils-8.4-5.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.11-1.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.33-1.fc13.i686.PAE #1 SMP Wed Feb 24 19:54:49 UTC 2010 i686 i686 Alert Count 1 First Seen Mon 08 Mar 2010 08:32:05 GMT Last Seen Mon 08 Mar 2010 08:32:05 GMT Local ID fe15bace-8702-44e0-b3b5-61d0a9c296e7 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1268037125.260:52): avc: denied { create } for pid=6464 comm="runuser" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tclass=netlink_audit_socket node=(removed) type=SYSCALL msg=audit(1268037125.260:52): arch=40000003 syscall=102 success=no exit=-13 a0=1 a1=bfc82630 a2=4700ff4 a3=83e4da0 items=0 ppid=6463 pid=6464 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="runuser" exe="/sbin/runuser" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) Hash String generated from catchall,runuser,logrotate_t,logrotate_t,netlink_audit_socket,create audit2allow suggests: #============= logrotate_t ============== allow logrotate_t self:netlink_audit_socket create;
I cannot add any further information about what was happening at the time. No-one was using, or anywhere near, the system at the time. It does appear from the above that logrotate may have been the cause, and indeed logs do appear to have been rotated at 08:32 GMT this morning, which is the time that the issue was reported.
I just saw the same thing on my machine. logrotate needs logging_send_audit_msgs(logrotate_t) When logrotate switches users, the runuser command attempts to send an audit message with the logrotate domain is not allowed. Fixed in selinux-policy-3.7.13-1.fc13.noarch
selinux-policy-3.7.14-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/selinux-policy-3.7.14-1.fc13
selinux-policy-3.7.14-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/selinux-policy-3.7.14-3.fc13
selinux-policy-3.7.14-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.