Summary: SELinux is preventing cupsd "create" access on cups. Detailed Description: SELinux denied access requested by cupsd. It is not expected that this access is required by cupsd 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 unconfined_u:system_r:cupsd_t:s0-s0:c0.c1023 Target Context unconfined_u:object_r:cupsd_log_t:s0 Target Objects cups [ dir ] Source cupsd Source Path cupsd Port <Unknown> Host X Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.7.19-13.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name X Platform Linux X 2.6.33.3-79.fc13.x86_64 #1 SMP Mon May 3 22:37:18 UTC 2010 x86_64 x86_64 Alert Count 1 First Seen Sat 08 May 2010 22:16:46 CEST Last Seen Sat 08 May 2010 22:16:46 CEST Local ID X Line Numbers Raw Audit Messages node=X type=AVC msg=audit(1273349806.916:411): avc: denied { create } for pid=6304 comm="cupsd" name="cups" scontext=unconfined_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:cupsd_log_t:s0 tclass=dir
Fixed in selinux-policy-3.7.19-15.fc13.noarch
selinux-policy-3.7.19-15.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/selinux-policy-3.7.19-15.fc13
selinux-policy-3.7.19-15.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.19-15.fc13
selinux-policy-3.7.19-15.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.