Bug 210282 - config-cups-dae makes selinux fill logs with error messages
config-cups-dae makes selinux fill logs with error messages
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
5
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-11 06:06 EDT by Matěj Cepl
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-14 10:16:16 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)

  None (edit)
Description Matěj Cepl 2006-10-11 06:06:53 EDT
Description of problem:
I have installed fresh Fedora Core 5 on my computer from the official 
installation DVD. Then I have upgraded with yum update and since the update I 
have had filled both my console and /var/log/message with error messages like 
this:

Oct 11 11:41:45 localhost kernel: audit(1160559705.086:2889): avc:  denied  { 
search } for  pid=2162 comm="cups-config-dae" name="dbus" dev=dm-1 ino=412674 
scontext=system_u:system_r:cupsd_config_t:s0 
tcontext=system_u:object_r:named_conf_t:s0 tclass=dir

File with inode 412674 is /var/run/dbus

When applied restorecon /var/run/dbus selinux is silent now.

Version-Release number of selected component (if applicable):
dbus-0.61-3.fc5.1
selinux-policy-2.3.7
cups-1.2.4-1.1
hal-cups-utils-0.5.5-1.2.fc5.2

How reproducible:


Steps to Reproduce:
1. Install Fedora Core 5 on the fresh computer
2. run yum update
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Walsh 2006-10-16 11:15:41 EDT
Looks like you had a labeling problem on initial install.

touch /.autorelabel
reboot
should guarantee your labeleing.  I have no idea why your labeleing was screwed up>?
Comment 2 Daniel Walsh 2007-02-14 10:16:16 EST
All of these bugs should be fixed in FC6,  You could attempt to use the FC6
policy on FC5 or upgrade.  Or you could use 

audit2allow -M mypolicy -i /var/log/audit/audit.log 
and build local customized policy

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