Bug 382361 - SELinux blocks dund (F7, F8)
SELinux blocks dund (F7, F8)
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
8
All Linux
high Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-14 08:25 EST by Gilboa Davara
Modified: 2008-01-30 14:06 EST (History)
0 users

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-30 14:06:36 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)
F8 selalert log (2.06 KB, text/plain)
2007-11-14 08:25 EST, Gilboa Davara
no flags Details

  None (edit)
Description Gilboa Davara 2007-11-14 08:25:23 EST
Description of problem:
Trying to start dund. (bluez-utils)
SELinux generates the following error. (sealert log attached)

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

F8: $ rpm -qa | egrep 'policy-targeted|bluez-utils' | sort
bluez-utils-3.20-4.fc8.x86_64
bluez-utils-alsa-3.20-4.fc8.x86_64
bluez-utils-cups-3.20-4.fc8.x86_64
bluez-utils-gstreamer-3.20-4.fc8.x86_64
selinux-policy-targeted-3.0.8-47.fc8.noarch

F7: $ rpm -qa | egrep 'policy-targeted|bluez-utils' | sort
bluez-utils-3.9-2.fc7.x86_64
bluez-utils-cups-3.9-2.fc7.x86_64
selinux-policy-targeted-2.6.4-49.fc7.noarch

How reproducible:
Always
Comment 1 Gilboa Davara 2007-11-14 08:25:23 EST
Created attachment 258021 [details]
F8 selalert log
Comment 2 Daniel Walsh 2007-11-14 10:20:58 EST
Fixed in selinux-policy-3.0.8-54.fc8
Comment 3 Gilboa Davara 2007-11-14 11:26:01 EST
Thanks.

Back port to F7?

- Gilboa
Comment 4 Gilboa Davara 2007-11-14 11:27:19 EST
P.S. koji link?
Comment 5 Daniel Walsh 2008-01-30 14:06:36 EST
Bulk closing a old selinux policy bugs that were in the modified state.  If the
bug is still not fixed.  Please reopen.

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