Bug 227704
Summary: | SELinux denial while starting haldaemon | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nalin Dahyabhai <nalin> |
Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | davidz, dwalsh, gnomeuser |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Current | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-22 14:15:14 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
Nalin Dahyabhai
2007-02-07 17:37:49 UTC
*** Bug 227713 has been marked as a duplicate of this bug. *** Here's my audit message: avc: denied { write } for comm="hald-generate-f" dev=dm-3 egid=0 euid=0 exe="/usr/libexec/hald-generate-fdi-cache" exit=-13 fsgid=0 fsuid=0 gid=0 items=0 name="hald" pid=3570 scontext=user_u:system_r:hald_t:s0 sgid=0 subj=user_u:system_r:hald_t:s0 suid=0 tclass=dir tcontext=system_u:object_r:var_t:s0 tty=(none) uid=0 Fixed in selinux-policy-2.5.2-7 (In reply to comment #3) > Fixed in selinux-policy-2.5.2-7 > I've selinux-policy-2.6.1-1.fc7. My audit message: avc: denied { write } for pid=2893 comm="hald-generate-f" name="hald" dev=dm-0 ino=32670049 scontext=user_u:system_r:hald_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir (In reply to comment #4) > (In reply to comment #3) > > Fixed in selinux-policy-2.5.2-7 > > > > I've selinux-policy-2.6.1-1.fc7. > > My audit message: > avc: denied { write } for pid=2893 comm="hald-generate-f" name="hald" > dev=dm-0 ino=32670049 scontext=user_u:system_r:hald_t:s0 > tcontext=system_u:object_r:var_t:s0 tclass=dir A "touch /.autorelabel && reboot" did it! Should be fixed in the current release |