SELinux is preventing khidpd_045e0700 from 'write' accesses on the socket Unknown. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that khidpd_045e0700 should be allowed write access on the Unknown socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep khidpd_045e0700 /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:kernel_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects Unknown [ socket ] Source khidpd_045e0700 Source Path khidpd_045e0700 Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.9.16-15.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.2-9.fc15.i686 #1 SMP Wed Mar 30 16:54:01 UTC 2011 i686 i686 Alert Count 21868 First Seen Tue 19 Apr 2011 06:39:57 PM CEST Last Seen Wed 20 Apr 2011 10:11:52 AM CEST Local ID f2ef9384-1728-4f8c-ae51-cfab48f93850 Raw Audit Messages type=AVC msg=audit(1303287112.451:2734): avc: denied { write } for pid=2185 comm="khidpd_045e0700" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=socket Hash: khidpd_045e0700,kernel_t,unlabeled_t,socket,write audit2allow #============= kernel_t ============== allow kernel_t unlabeled_t:socket write; audit2allow -R #============= kernel_t ============== allow kernel_t unlabeled_t:socket write;
I don't know what this is for, but my guess is it has something to do with bluetooth. Because the standard gnome-bluetooth package didn't work for me I installed Blueman. The thing is all seems oke, bluetooth shows enabled but when you look for the settings on the bar, it shows off! Now with a hciconfig -a output I get [code]hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:558826 acl:36892 sco:0 events:583 errors:0 TX bytes:538 acl:9 sco:0 commands:24 errors:0 Features: 0xff 0xff 0x8b 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'fedra.localdomain-0' Class: 0x480100 Service Classes: Capturing, Telephony Device Class: Computer, Uncategorized HCI Version: 2.0 (0x3) Revision: 0x77b LMP Version: 2.0 (0x3) Subversion: 0x77b Manufacturer: Cambridge Silicon Radio (10[/code] BD Address: 00:00:00:00:00:00=a fake ;) With a [code]# dmesg | grep Blue [ 23.923710] Bluetooth: Core ver 2.15 [ 23.923746] Bluetooth: HCI device and connection manager initialized [ 23.923750] Bluetooth: HCI socket layer initialized [ 24.002283] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 31.095484] Bluetooth: L2CAP ver 2.15 [ 31.095487] Bluetooth: L2CAP socket layer initialized# dmesg | grep Blue [ 23.923710] Bluetooth: Core ver 2.15 [ 23.923746] Bluetooth: HCI device and connection manager initialized [ 23.923750] Bluetooth: HCI socket layer initialized [ 24.002283] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 31.095484] Bluetooth: L2CAP ver 2.15 [ 31.095487] Bluetooth: L2CAP socket layer initialized [ 31.154666] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 31.154670] Bluetooth: BNEP filters: protocol multicast [ 31.233768] Bluetooth: SCO (Voice Link) ver 0.6 [ 31.233771] Bluetooth: SCO socket layer initialized [ 662.740734] Bluetooth: RFCOMM TTY layer initialized [ 662.740743] Bluetooth: RFCOMM socket layer initialized [ 662.740745] Bluetooth: RFCOMM ver 1.11 [ 663.131712] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 667.145062] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/bluetooth/hci0/hci0:42/input10 [ 667.148655] generic-bluetooth 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:1A:92:C5:7A:02 [ 31.154666] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 31.154670] Bluetooth: BNEP filters: protocol multicast [ 31.233768] Bluetooth: SCO (Voice Link) ver 0.6 [ 31.233771] Bluetooth: SCO socket layer initialized [ 662.740734] Bluetooth: RFCOMM TTY layer initialized [ 662.740743] Bluetooth: RFCOMM socket layer initialized [ 662.740745] Bluetooth: RFCOMM ver 1.11 [ 663.131712] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 667.145062] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/bluetooth/hci0/hci0:42/input10 [ 667.148655] generic-bluetooth 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:00:00:00:00:00[/code] BD Address: 00:00:00:00:00:00=a fake ;) Now when I install blueman I seem to get bluetooth working, but hope there comes a fix for gnome-bluetooth. [code] In my case there seems to be a problem with bluetooth but haven't figured what it is exactly. Hope it helps you (and me) in some way, thanks. Note: when I try to delete the message, I get hundreds of this one, so something is definitively failing ;)
Miroslav we should just allow unconfined domains to write to unlabeled_t sockets for F15.
*** Bug 698265 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 741703 ***