Description of problem: login to xfed SELinux is preventing /usr/sbin/xtables-multi from 'read' accesses on the file /etc/firewalld/zones/public.xml. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that xtables-multi should be allowed read access on the public.xml 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 iptables /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:iptables_t:s0 Target Context system_u:object_r:firewalld_etc_rw_t:s0 Target Objects /etc/firewalld/zones/public.xml [ file ] Source iptables Source Path /usr/sbin/xtables-multi Port <Unknown> Host (removed) Source RPM Packages iptables-1.4.18-1.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-28.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.9.0-0.rc6.git2.1.fc19.x86_64 #1 SMP Thu Apr 11 17:11:04 UTC 2013 x86_64 x86_64 Alert Count 82 First Seen 2013-04-14 08:32:35 GMT Last Seen 2013-04-14 08:32:37 GMT Local ID 85620499-362c-44c6-987e-6eea5b2a6dc5 Raw Audit Messages type=AVC msg=audit(1365928357.837:2101): avc: denied { read } for pid=2138 comm="ip6tables" path="/etc/firewalld/zones/public.xml" dev="dm-1" ino=2097444 scontext=system_u:system_r:iptables_t:s0 tcontext=system_u:object_r:firewalld_etc_rw_t:s0 tclass=file type=SYSCALL msg=audit(1365928357.837:2101): arch=x86_64 syscall=execve success=yes exit=0 a0=1281dc0 a1=12745d0 a2=1256960 a3=1 items=0 ppid=1274 pid=2138 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=ip6tables exe=/usr/sbin/xtables-multi subj=system_u:system_r:iptables_t:s0 key=(null) Hash: iptables,iptables_t,firewalld_etc_rw_t,file,read audit2allow #============= iptables_t ============== allow iptables_t firewalld_etc_rw_t:file read; audit2allow -R require { type firewalld_etc_rw_t; type iptables_t; class file read; } #============= iptables_t ============== allow iptables_t firewalld_etc_rw_t:file read; Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc6.git2.1.fc19.x86_64 type: libreport
Does firewalld close all fds? "/etc/firewalld/zones/public.xml" in this case.
fcntl(fd,F_SETFD, FD_CLOEXEC)
*** Bug 956881 has been marked as a duplicate of this bug. ***
Could be fixed with https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=d08ddbe77047d157983f0cc31a01cbc4dc44e746
firewalld-0.3.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/firewalld-0.3.6-1.fc20
firewalld-0.3.6-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/firewalld-0.3.6-1.fc19
Package firewalld-0.3.6-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firewalld-0.3.6-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18182/firewalld-0.3.6-1.fc19 then log in and leave karma (feedback).
firewalld-0.3.6.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
firewalld-0.3.7-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/firewalld-0.3.7-1.fc19
Package firewalld-0.3.7-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firewalld-0.3.7-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19324/firewalld-0.3.7-1.fc19 then log in and leave karma (feedback).
firewalld-0.3.7-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.