Hide Forgot
libreport version: 2.0.6 executable: /usr/bin/python hashmarkername: setroubleshoot kernel: 3.1.0-0.rc10.git0.1.fc16.x86_64 reason: SELinux is preventing /usr/bin/python from 'read' accesses on the lnk_file /etc/sysconfig/selinux. time: Mon Oct 24 01:15:10 2011 description: :SELinux is preven(removed)ing /usr/bin/py(removed)hon from 'read' accesses on (removed)he lnk_file /e(removed)c/sysconfig/selinux. : :***** Plugin res(removed)orecon (99.5 confidence) sugges(removed)s ************************* : :If you wan(removed) (removed)o fix (removed)he label. :/e(removed)c/sysconfig/selinux defaul(removed) label should be e(removed)c_(removed). :Then you can run res(removed)orecon. :Do :# /sbin/res(removed)orecon -v /e(removed)c/sysconfig/selinux : :***** Plugin ca(removed)chall (1.49 confidence) sugges(removed)s *************************** : :If you believe (removed)ha(removed) py(removed)hon should be allowed read access on (removed)he selinux lnk_file by defaul(removed). :Then you should repor(removed) (removed)his as a bug. :You can genera(removed)e a local policy module (removed)o allow (removed)his access. :Do :allow (removed)his access for now by execu(removed)ing: :# grep sys(removed)em-config-f /var/log/audi(removed)/audi(removed).log | audi(removed)2allow -M mypol :# semodule -i mypol.pp : :Addi(removed)ional Informa(removed)ion: :Source Con(removed)ex(removed) sys(removed)em_u:sys(removed)em_r:firewallgui_(removed):s0-s0:c0.c1023 :Targe(removed) Con(removed)ex(removed) sys(removed)em_u:objec(removed)_r:selinux_config_(removed):s0 :Targe(removed) Objec(removed)s /e(removed)c/sysconfig/selinux [ lnk_file ] :Source sys(removed)em-config-f :Source Pa(removed)h /usr/bin/py(removed)hon :Por(removed) <Unknown> :Hos(removed) (removed) :Source RPM Packages py(removed)hon-2.7.2-4.fc16 :Targe(removed) RPM Packages selinux-policy-3.10.0-40.fc16 :Policy RPM selinux-policy-3.10.0-40.fc16 :Selinux Enabled True :Policy Type (removed)arge(removed)ed :Enforcing Mode Enforcing :Hos(removed) Name (removed) :Pla(removed)form Linux (removed) 3.1.0-0.rc10.gi(removed)0.1.fc16.x86_64 #1 SMP Wed : Oc(removed) 19 05:02:17 UTC 2011 x86_64 x86_64 :Aler(removed) Coun(removed) 1 :Firs(removed) Seen Mon 24 Oc(removed) 2011 12:32:01 AM EDT :Las(removed) Seen Mon 24 Oc(removed) 2011 12:32:01 AM EDT :Local ID 13ec2ca5-6cc8-4d1c-8e6b-021fe94c410c : :Raw Audi(removed) Messages :(removed)ype=AVC msg=audi(removed)(1319430721.143:131): avc: denied { read } for pid=2638 comm="sys(removed)em-config-f" name="selinux" dev=dm-2 ino=2363256 scon(removed)ex(removed)=sys(removed)em_u:sys(removed)em_r:firewallgui_(removed):s0-s0:c0.c1023 (removed)con(removed)ex(removed)=sys(removed)em_u:objec(removed)_r:selinux_config_(removed):s0 (removed)class=lnk_file : : :(removed)ype=SYSCALL msg=audi(removed)(1319430721.143:131): arch=x86_64 syscall=s(removed)a(removed) success=no exi(removed)=EACCES a0=eba0c0 a1=7fffaae070b0 a2=7fffaae070b0 a3=3ba833f770 i(removed)ems=0 ppid=1 pid=2638 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 (removed)(removed)y=(none) ses=4294967295 comm=sys(removed)em-config-f exe=/usr/bin/py(removed)hon subj=sys(removed)em_u:sys(removed)em_r:firewallgui_(removed):s0-s0:c0.c1023 key=(null) : :Hash: sys(removed)em-config-f,firewallgui_(removed),selinux_config_(removed),lnk_file,read : :audi(removed)2allow : :#============= firewallgui_(removed) ============== :allow firewallgui_(removed) selinux_config_(removed):lnk_file read; : :audi(removed)2allow -R : :#============= firewallgui_(removed) ============== :allow firewallgui_(removed) selinux_config_(removed):lnk_file read; :
Why does s-c-firewall need to read /etc/sysconfig/selinux?
Because lokkit is still used to configure selinux for example in anaconda. This should change for RHEL-7.
It should be reading /etc/selinux/config. We have not used /etc/sysconfig/selinux in about 8 years... But we should allow it none the less.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.