Description of problem: SELinux is preventing firewalld from 'write' accesses on the directory root. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that firewalld should be allowed write access on the root directory 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: # ausearch -c 'firewalld' --raw | audit2allow -M my-firewalld # semodule -X 300 -i my-firewalld.pp Additional Information: Source Context system_u:system_r:firewalld_t:s0 Target Context system_u:object_r:admin_home_t:s0 Target Objects root [ dir ] Source firewalld Source Path firewalld Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages filesystem-3.2-37.fc24.x86_64 Policy RPM selinux-policy-3.13.1-192.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.7.0-0.rc0.git10.1.fc25.x86_64 #1 SMP Fri May 27 14:56:48 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-05-28 19:11:10 CEST Last Seen 2016-05-28 19:11:10 CEST Local ID 8a3485b9-769f-48b6-8993-519e57e0d860 Raw Audit Messages type=AVC msg=audit(1464455470.276:212): avc: denied { write } for pid=832 comm="firewalld" name="root" dev="dm-0" ino=655362 scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u:object_r:admin_home_t:s0 tclass=dir permissive=0 Hash: firewalld,firewalld_t,admin_home_t,dir,write Version-Release number of selected component: selinux-policy-3.13.1-192.fc25.noarch Additional info: reporter: libreport-2.7.1 hashmarkername: setroubleshoot kernel: 4.7.0-0.rc0.git10.1.fc25.x86_64 reproducible: Not sure how to reproduce the problem type: libreport Potential duplicate: bug 1329854
*** Bug 1329854 has been marked as a duplicate of this bug. ***
Thomas, Whats going on here?
(In reply to Lukas Vrabec from comment #2) > Thomas, > Whats going on here? Lukas, this is very unexpected as there is no code in firewalld that touches /root.
Which firewalld version is installed on the system? Do you have steps to reproduce this?
When I reported the bug it was firewalld-0.4.1.2-2.fc25.
Probably some library that writes content in /root
We can dontaudit it. Thomas, Agree?
Hi Lukas, yes this might be possible. Regards, Thomas
Issue still present for firewalld-0.4.3.2-1.fc25.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
(In reply to Daniel Walsh from comment #6) > Probably some library that writes content in /root On my Fedora 24 system, it was attempting to create the /root/.cache directory. I only found out because in permissive mode, the empty /root/.cache directory was created.
firewalld is not using /root/.cache at all. This needs to be hunted down.
After removing /root/.cache I am able to reproduce this. But I have absolutely no clue, why this happens.
Me either: type=AVC msg=audit(1470084516.47:178): avc: denied { create } for pid=953 comm="firewalld" name=".cache" scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u:object_r:admin_home_t:s0 tclass=dir permissive=1
It must be in one of the gnome libraries or gtk?
Description of problem: This popped up on me on first boot after a default Workstation Live install (Fedora-Workstation-Live-x86_64-25-20160815.n.2.iso). I just started terminal and ran dnf, nothing else. Not sure whether this occurred before or after. Version-Release number of selected component: selinux-policy-3.13.1-207.fc25.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc1.git0.1.fc25.x86_64 type: libreport
Proposing as a Final blocker: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. " https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#SELinux_and_crash_notifications
commit 48be02c9e486299e26df76a6698ed2ab4700c2e4 Author: Lukas Vrabec <lvrabec> Date: Tue Aug 16 13:08:25 2016 +0200 Dontaudit firewalld to create dirs in /root/ BZ(1340611)
This is subjective information, I know, but I believe this is related to having firewall-config installed--the issue only happens on my GUI workstations, where firewall-config is installed, but not my headless servers, where firewall-config is not.
Discussed during the 2016-08-22 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made as it is a clear violation of "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-08-22/f25-blocker-review.2016-08-22-16.00.txt
selinux-policy-3.13.1-210.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d8defc177
selinux-policy-3.13.1-211.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cbdde50ec4
selinux-policy-3.13.1-211.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.