Bug 570815
Summary: | selinux-policy-targeted doesn't allow /usr/sbin/bluetoothd to access /dev/rfcomm0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Leonid Kanter <leon> |
Component: | bluez | Assignee: | Bastien Nocera <bnocera> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | atigro, bnocera, dwalsh, dwmw2, marcel, plautrba |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-05 14:46:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leonid Kanter
2010-03-05 14:15:08 UTC
The problem is rfcomm0 did not get labeled correctly. matchpathcon /dev/rfcomm0 /dev/rfcomm0 system_u:object_r:tty_device_t:s0 If this device was created by udev, it would be labeled correctly. If this device is being created by bluetooth or a bluetooth script, it needs to make sure the labelling is correct. *** This bug has been marked as a duplicate of bug 566332 *** |