Bug 699231

Summary: SELinux is preventing /usr/sbin/NetworkManager from 'unlink' accesses on the file resolv.conf.
Product: [Fedora] Fedora Reporter: Ranjan Maitra <itsme_410>
Component: pm-utilsAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, dwalsh, hughsient, jskarvad, mgrepl, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:3b87f538d7a863ec083f6fe76d52e0ff885906d3a43ea07f9de8af0d9c62fd6e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:40:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ranjan Maitra 2011-04-24 12:23:22 UTC
SELinux is preventing /usr/sbin/NetworkManager from 'unlink' accesses on the file resolv.conf.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that NetworkManager should be allowed unlink access on the resolv.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep NetworkManager /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:NetworkManager_t:s0
Target Context                system_u:object_r:etc_runtime_t:s0
Target Objects                resolv.conf [ file ]
Source                        NetworkManager
Source Path                   /usr/sbin/NetworkManager
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           NetworkManager-0.8.3.998-2.fc14
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.7-37.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.35.12-88.fc14.x86_64 #1 SMP Thu Mar 31
                              21:21:57 UTC 2011 x86_64 x86_64
Alert Count                   2
First Seen                    Sat 23 Apr 2011 11:37:22 PM CDT
Last Seen                     Sat 23 Apr 2011 11:37:23 PM CDT
Local ID                      d7d29bdf-a594-4194-bab0-e5d116408622

Raw Audit Messages
type=AVC msg=audit(1303619843.123:38): avc:  denied  { unlink } for  pid=1242 comm="NetworkManager" name="resolv.conf" dev=sda2 ino=10959 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:etc_runtime_t:s0 tclass=file


type=SYSCALL msg=audit(1303619843.123:38): arch=x86_64 syscall=rename success=no exit=EACCES a0=136d800 a1=1363800 a2=1394bf0 a3=ffffffff items=0 ppid=1 pid=1242 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=NetworkManager exe=/usr/sbin/NetworkManager subj=system_u:system_r:NetworkManager_t:s0 key=(null)

Hash: NetworkManager,NetworkManager_t,etc_runtime_t,file,unlink

audit2allow

#============= NetworkManager_t ==============
#!!!! This avc is allowed in the current policy

allow NetworkManager_t etc_runtime_t:file unlink;

audit2allow -R

#============= NetworkManager_t ==============
#!!!! This avc is allowed in the current policy

allow NetworkManager_t etc_runtime_t:file unlink;

Comment 1 Daniel Walsh 2011-04-25 13:23:33 UTC
restorecon -R -v /etc/resolv.conf

Should fix.  Any idea how this happened?

Comment 2 Ranjan Maitra 2011-09-14 13:13:54 UTC
(In reply to comment #1)
> restorecon -R -v /etc/resolv.conf
> 
> Should fix.  Any idea how this happened?

Back on fedora 15, 2.6.40.4-5.fc15.x86_64:
pm-hibernate and wake up after that.

Comment 3 Miroslav Grepl 2011-09-14 13:43:22 UTC
Does pm-utils pckg handle with resolv.conf?

Comment 4 Ranjan Maitra 2011-09-15 01:38:49 UTC
I am not sure what this means. I do have the pm-utils package installed and the latest version at pm-utils-1.4.1-8.fc15.x86_64

Comment 5 Jaroslav Škarvada 2011-09-15 07:31:24 UTC
(In reply to comment #3)
> Does pm-utils pckg handle with resolv.conf?

AFAIK not directly, it only calls org.freedesktop.NetworkManager.sleep / wake through dbus.

Comment 6 Jaroslav Škarvada 2011-09-15 10:16:25 UTC
Nevertheless I am unable to reproduce this on freshly installed f15 system. My version of packages:
kernel-2.6.40.4-5.fc15.x86_64
NetworkManager-0.9.0-1.fc15.x86_64
pm-utils-1.4.1-8.fc15.x86_64
selinux-policy-3.9.16-38.fc15.noarch

I tried in both enforcing and permissive mode. I also tried w/wo LAN/WLAN.

Could you provide output of pm-utils-bugreport-info.sh? Also please check the /var/log/messages if there are any related logs (especially NetworkManager logs). Which interfaces / VPNs are active during hibernate?

AFAIK the unlink is not done by pm-utils.

Comment 7 Jaroslav Škarvada 2011-09-15 10:21:45 UTC
AFAIK there are some unlinks in the NetworkManager code, CCing NetworkManager maintainer in case he gets idea what's going there.

Comment 8 Fedora End Of Life 2012-08-07 16:40:19 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping