Bug 644808

Summary: NetworkManager writing out resolv.conf with wrong context
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0CC: mgrepl, mmalik, pm-eus, snagar, tremble
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.7.19-54.el6_0.2 Doc Type: Bug Fix
Doc Text:
With SELinux running in the enforcing mode, resuming the system from the Suspend mode resulted in the /etc/resolv.conf file being recreated with the wrong security context. This meant that under subsequent normal operation Network manager was unable to update the /etc/resolv.conf file. This was caused by NetworkManager, which was running under wrong SELinux domain, "devicekit_power_t". With this update, the proper SELinux domain transition from DeviceKit-power to NetworkManager has been added, and resuming from the Suspend mode now works as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 19:01:39 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:
Bug Depends On: 639074    
Bug Blocks:    

Description RHEL Program Management 2010-10-20 11:22:04 UTC
This bug has been copied from bug #639074 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 3 Miroslav Grepl 2010-10-20 13:41:19 UTC
Fixed in selinux-policy-3.7.19-54.el6_0.2.

Comment 5 Jaromir Hradilek 2010-10-21 08:53:53 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
With SELinux running in the enforcing mode, resuming the system from the Suspend mode failed, because the /etc/resolv.conf file did not have the correct security context. This was caused by NetworkManager, which was running under wrong SELinux domain, "devicekit_power_t". With this update, the proper SELinux domain transition from DeviceKit-power to NetworkManager has been added, and resuming from the Suspend mode now works as expected.

Comment 6 Mark Chappell 2010-10-21 10:44:31 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-With SELinux running in the enforcing mode, resuming the system from the Suspend mode failed, because the /etc/resolv.conf file did not have the correct security context. This was caused by NetworkManager, which was running under wrong SELinux domain, "devicekit_power_t". With this update, the proper SELinux domain transition from DeviceKit-power to NetworkManager has been added, and resuming from the Suspend mode now works as expected.+With SELinux running in the enforcing mode, resuming the system from the Suspend mode resulted in the /etc/resolv.conf file being recreated with the wrong security context. This meant that under subsequent normal operation Network manager was unable to update the /etc/resolv.conf file.  This was caused by NetworkManager, which was running under wrong SELinux domain, "devicekit_power_t".  With this update, the proper SELinux domain transition from DeviceKit-power to NetworkManager has been added, and resuming from the Suspend mode now works as expected.

Comment 9 errata-xmlrpc 2010-11-10 19:01:39 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0845.html