Red Hat Bugzilla – Bug 220667
SELinux blocks dund access to /var/run/sdp
Last modified: 2007-11-30 17:11:52 EST
Description of problem:
I am setting up dund to provide my Palm PDA with network access using my Fedora
Core 6 laptop as a gateway. I am following the instructions given at
<http://howto.pilot-link.org/bluesync/ga.html>. I have created an
"/etc/ppp/peers/dun" file as suggested on that page, and have edited
"/etc/sysconfig/dund" to set DUNDARGS to '--listen --persist --msdun call dun'.
As root, I run "service dund start" to start the Bluetooth dial-up networking
daemon. SELinux reports "SELinux is preventing /usr/bin/dund (bluetooth_t)
"connectto" access to /var/run/sdp (bluetooth_t)."
Version-Release number of selected component (if applicable):
How reproducible: 100% reproducible.
Steps to Reproduce:
1. Create an "/etc/ppp/peers/dun" file as suggested by
<http://howto.pilot-link.org/bluesync/ga.html>. (optional step?)
2. Edit "/etc/sysconfig/dund" so that it contains the following text on a single
DUNDARGS='--listen --persist --msdun call dun'
3. As root, run "service dund start".
SELinux blocks access to "/var/run/sdp" and reports this action in the system
logs and/or to the SELinux troubleshooting browser.
Presumably, dund should be allowed to communicate with sdpd without triggering
SELinux policy violations. (I'm assuming that this inter-daemon communication
is, in fact, correct behavior. But I don't really know what the different
pieces of the puzzle do here.)
See attached record with more detailed diagnostic information from the SELinux
Created attachment 144313 [details]
detailed diagnostic information from SELinux troubleshooting browser
This has been fixed for a long time in the latest-selinux policy
yum update selinux-policy
should pull it.