Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
commit 6efdf0ec8b73c7bb52870a36f2a003f33f9b05c9
Author: Miroslav Grepl <mgrepl>
Date: Tue Jul 30 11:02:27 2013 +0200
Allow firewalld to interact also with lnk files labeled as firewalld_etc_rw_t
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: There could be many XML files which contain various lockdown whitelists. If /etc/firewalld/lockdown-whitelist.xml is a symlink pointing to one of them then SELinux prevents firewalld from accessing it. Version-Release number of selected component (if applicable): firewalld-0.3.3-2.el7.noarch selinux-policy-3.12.1-65.el7.noarch selinux-policy-devel-3.12.1-65.el7.noarch selinux-policy-doc-3.12.1-65.el7.noarch selinux-policy-minimum-3.12.1-65.el7.noarch selinux-policy-mls-3.12.1-65.el7.noarch selinux-policy-targeted-3.12.1-65.el7.noarch How reproducible: always Steps to Reproduce: # mv /etc/firewalld/lockdown-whitelist.xml /etc/firewalld/lockdown-whitelist.xml.orig # ln -s /etc/firewalld/lockdown-whitelist.xml.orig /etc/firewalld/lockdown-whitelist.xml # sed -i "s/Lockdown=no/Lockdown=yes/" /etc/firewalld/firewalld.conf # service firewalld restart # ausearch -m avc -m user_avc -m selinux_err -ts recent -i Actual results: ---- type=PATH msg=audit(07/30/2013 09:12:37.742:34724) : item=0 name=/etc/firewalld/lockdown-whitelist.xml type=CWD msg=audit(07/30/2013 09:12:37.742:34724) : cwd=/ type=SYSCALL msg=audit(07/30/2013 09:12:37.742:34724) : arch=x86_64 syscall=stat success=no exit=-13(Permission denied) a0=0x23f4220 a1=0x7fffa3187bb0 a2=0x7fffa3187bb0 a3=0x6c2f646c6c617765 items=1 ppid=1 pid=4655 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root ses=unset tty=(none) comm=firewalld exe=/usr/bin/python2.7 subj=system_u:system_r:firewalld_t:s0 key=(null) type=AVC msg=audit(07/30/2013 09:12:37.742:34724) : avc: denied { read } for pid=4655 comm=firewalld name=lockdown-whitelist.xml dev="sda4" ino=3935804 scontext=system_u:system_r:firewalld_t:s0 tcontext=unconfined_u:object_r:firewalld_etc_rw_t:s0 tclass=lnk_file ---- Expected results: * no AVCs