Additional info: libreport version: 2.0.13 kernel: 3.6.0-0.rc6.git0.1.fc18.x86_64 description: :SELinux is preventing /usr/bin/python2.7 from 'read' accesses on the file /etc/nsswitch.conf. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that python2.7 should be allowed read access on the nsswitch.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 tuned /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context system_u:system_r:tuned_t:s0 :Target Context system_u:object_r:system_dbusd_var_lib_t:s0 :Target Objects /etc/nsswitch.conf [ file ] :Source tuned :Source Path /usr/bin/python2.7 :Port <Unknown> :Host (removed) :Source RPM Packages bash-4.2.37-6.fc18.x86_64 :Target RPM Packages glibc-2.16-15.fc18.x86_64 :Policy RPM selinux-policy-3.11.1-21.fc18.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Enforcing :Host Name (removed) :Platform Linux (removed) 3.6.0-0.rc6.git0.1.fc18.x86_64 #1 : SMP Mon Sep 17 13:16:51 UTC 2012 x86_64 x86_64 :Alert Count 67 :First Seen 2012-09-20 21:11:21 PDT :Last Seen 2012-09-22 11:14:54 PDT :Local ID 10aec680-e17f-4d9d-8343-cc12d2bbbbce : :Raw Audit Messages :type=AVC msg=audit(1348337694.969:692): avc: denied { read } for pid=2925 comm="sh" name="nsswitch.conf" dev="dm-1" ino=2490725 scontext=system_u:system_r:tuned_t:s0 tcontext=system_u:object_r:system_dbusd_var_lib_t:s0 tclass=file : : :type=SYSCALL msg=audit(1348337694.969:692): arch=x86_64 syscall=open success=no exit=EACCES a0=30e3178512 a1=80000 a2=1b6 a3=238 items=0 ppid=574 pid=2925 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=sh exe=/usr/bin/bash subj=system_u:system_r:tuned_t:s0 key=(null) : :Hash: tuned,tuned_t,system_dbusd_var_lib_t,file,read : :audit2allow : :#============= tuned_t ============== :allow tuned_t system_dbusd_var_lib_t:file read; : :audit2allow -R : :#============= tuned_t ============== :allow tuned_t system_dbusd_var_lib_t:file read; :
Created attachment 615889 [details] File: type
Created attachment 615890 [details] File: hashmarkername
The problem is the nsswitch.conf is mislabeled. Did you do an upgrade or is this a fresh install? # restorecon -R -v /etc/nsswitch will fix it.
That was an upgrade since August 2012.
(In reply to comment #3) > The problem is the nsswitch.conf is mislabeled. > > Did you do an upgrade or is this a fresh install? > > # restorecon -R -v /etc/nsswitch > # restorecon -R -v /etc/nsswitch restorecon: lstat(/etc/nsswitch) failed: No such file or directory # restorecon -R -v /etc/nsswitch.conf command worked but the sealert keeps popping 11 alerts related to nsswitch.conf. Here is ls command ]# ls -al /etc/ | grep nsswitchw -rw-r--r--. 1 root root 1717 Aug 18 01:54 nsswitch.conf -rw-r--r--. 1 root root 1717 Aug 15 19:57 nsswitch.conf.bak I am reopening the bug because the problem still occurs.
# ls -Z /etc/nsswitch.conf*
# ls -alZ /etc/ | grep nsswitch -rw-r--r--. root root system_u:object_r:system_dbusd_var_lib_t:s0 nsswitch.conf -rw-r--r--. root root system_u:object_r:etc_t:s0 nsswitch.conf.bak I removed the bak file
The question I have is how did this happen? What created nsswitch as system_dbusd_var_lib_t and then mv'd it to /etc?
I would say an upgrade issue. $ restorecon -v /etc/nsswitch.conf* and then you will see if this happens again.
Yes it happens again after applying $ restorecon -v /etc/nsswitch.conf* Source process according to sealert: mcelog, rpc.statd, dbus-daemon, unix-chkpwd, systemd-tmpfiles, tuned Is tuned the cause of mislabeling?
No something is creating this file with the wrong label. Is something other then dbus running with the dbus label? ps -eZ | grep system_dbusd_t
(In reply to comment #11) > Is something other then dbus running with the dbus label? > > ps -eZ | grep system_dbusd_t $ ps -eZ | grep system_dbusd_t system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 512 ? 00:00:01 dbus-daemon
Does it happen on reboot?
(In reply to comment #13) > Does it happen on reboot? Yes, it happened on reboot.=(
Is this still happening?
(In reply to comment #15) > Is this still happening? Yes, it was still happening until I did a fresh installation of F18. Be in mind the problem occurred after an upgrade from F17 to F18.
Ok then it was an upgrade issue. Let's close it and re-open if we see it again. Thank you.