Bug 470718 - Selinux denials when trying to change bluetooth name from the applet.
Selinux denials when trying to change bluetooth name from the applet.
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-09 07:15 EST by You
Modified: 2008-11-10 09:29 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-10 09:29:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Selinux message when trying to change friendly name of bluetooth device. (2.97 KB, text/plain)
2008-11-09 07:15 EST, You
no flags Details
Second SElinux denial for the above event. (2.76 KB, text/plain)
2008-11-09 07:16 EST, You
no flags Details

  None (edit)
Description You 2008-11-09 07:15:43 EST
Created attachment 323000 [details]
Selinux message when trying to change friendly name of bluetooth device.

Description of problem:


Version-Release number of selected component (if applicable):

selinux-policy-3.5.13-11.fc10
bluez-4.17-2.fc10

Steps to Reproduce:
1. Right click the Bluetooth icon on the desktop
2. Go to preferences
3. Type in friendly name
  
Actual results:

Two Selinux denials

Expected results:

No selinux problems, and the name to stick.

Additional info:

I am using bluetooth through a USB dongle.

PS - probably a bad place to put this, but thanks for all the hard work on SElinux - it really pays off and I am sure most that benefit are silent in their eternal thanks.
Comment 1 You 2008-11-09 07:16:25 EST
Created attachment 323001 [details]
Second SElinux denial for the above event.
Comment 2 Daniel Walsh 2008-11-10 09:29:35 EST
Fixed in selinux-policy-3.5.13-18.fc10

Note You need to log in before you can comment on or make changes to this bug.