Fedora Account System
Red Hat Associate
Red Hat Customer
Summary: SELinux is preventing /usr/bin/slim "write" access on /var/run/slim.lock. Detailed Description: SELinux denied access requested by slim. It is not expected that this access is required by slim 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:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:var_run_t:s0 Target Objects /var/run/slim.lock [ file ] Source slim Source Path /usr/bin/slim Port <Unknown> Host (removed) Source RPM Packages slim-1.3.1-9.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-78.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.12-174.2.3.fc12.i686 #1 SMP Mon Jan 18 20:22:46 UTC 2010 i686 i686 Alert Count 7 First Seen Wed 03 Feb 2010 09:07:42 PM GMT Last Seen Wed 03 Feb 2010 09:07:46 PM GMT Local ID 8700608a-82ae-4801-97e1-655aee67ae1f Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1265231266.341:47): avc: denied { write } for pid=2125 comm="slim" name="slim.lock" dev=dm-0 ino=3646 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 tclass=file node=(removed) type=SYSCALL msg=audit(1265231266.341:47): arch=40000003 syscall=5 success=no exit=-13 a0=99c395c a1=8241 a2=1b6 a3=d6a649 items=0 ppid=1 pid=2125 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="slim" exe="/usr/bin/slim" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-78.fc12,catchall,slim,xdm_t,var_run_t,file,write audit2allow suggests: #============= xdm_t ============== allow xdm_t var_run_t:file write;
*** This bug has been marked as a duplicate of bug 561539 ***