Fedora Account System
Red Hat Associate
Red Hat Customer
Summary: SELinux is preventing /usr/sbin/bluetoothd "write" access . Detailed Description: [SELinux is in permissive mode. This access was not denied.] SELinux denied access requested by bluetoothd. It is not expected that this access is required by bluetoothd 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:bluetooth_t:s0-s0:c0.c1023 Target Context system_u:object_r:unlabeled_t:s0 Target Objects None [ socket ] Source bluetoothd Source Path /usr/sbin/bluetoothd Port <Unknown> Host (removed) Source RPM Packages bluez-4.64-1.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.19-51.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.36-rc1+ #25 SMP Fri Sep 10 12:34:48 BST 2010 x86_64 x86_64 Alert Count 1 First Seen Fri 10 Sep 2010 14:12:13 BST Last Seen Fri 10 Sep 2010 14:12:13 BST Local ID cb499c58-95be-457b-aff7-b195da79609f Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1284124333.962:40): avc: denied { write } for pid=1261 comm="bluetoothd" scontext=system_u:system_r:bluetooth_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=socket node=(removed) type=SYSCALL msg=audit(1284124333.962:40): arch=c000003e syscall=44 success=yes exit=672 a0=18 a1=7f39deccb200 a2=2a0 a3=0 items=0 ppid=1 pid=1261 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="bluetoothd" exe="/usr/sbin/bluetoothd" subj=system_u:system_r:bluetooth_t:s0-s0:c0.c1023 key=(null) Hash String generated from catchall,bluetoothd,bluetooth_t,unlabeled_t,socket,write audit2allow suggests: #============= bluetooth_t ============== allow bluetooth_t unlabeled_t:socket write;
*** This bug has been marked as a duplicate of bug 633424 ***