Description of problem: Occurs after logging in to Gnome UI. SELinux is preventing dnssec-trigger- from 'write' accesses on the sock_file private. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that dnssec-trigger- should be allowed write access on the private sock_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 dnssec-trigger- /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:dnssec_trigger_t:s0 Target Context system_u:object_r:NetworkManager_var_run_t:s0 Target Objects private [ sock_file ] Source dnssec-trigger- Source Path dnssec-trigger- Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.9.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.19.3-200.fc21.x86_64 #1 SMP Thu Mar 26 21:39:42 UTC 2015 x86_64 x86_64 Alert Count 63 First Seen 2015-03-26 22:50:13 PDT Last Seen 2015-04-02 21:53:35 PDT Local ID 5a7ead13-136b-43b6-b3d4-9a11f7991d8b Raw Audit Messages type=AVC msg=audit(1428036815.234:515): avc: denied { write } for pid=3472 comm="dnssec-trigger-" name="private" dev="tmpfs" ino=21632 scontext=system_u:system_r:dnssec_trigger_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=sock_file permissive=0 Hash: dnssec-trigger-,dnssec_trigger_t,NetworkManager_var_run_t,sock_file,write Version-Release number of selected component: selinux-policy-3.13.1-105.9.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 3.19.3-200.fc21.x86_64 type: libreport
commit 06005bc0ac9370f93ba99e44d478e9930f3896c1 Author: Lukas Vrabec <lvrabec> Date: Thu Apr 9 21:06:09 2015 +0200 Allow dnssec_trigger_t to stream connect to networkmanager.
selinux-policy-3.13.1-105.13.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-105.13.fc21
Package selinux-policy-3.13.1-105.13.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.13.1-105.13.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6316/selinux-policy-3.13.1-105.13.fc21 then log in and leave karma (feedback).
selinux-policy-3.13.1-105.13.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Description of problem: boot up and log in Version-Release number of selected component: selinux-policy-3.13.1-105.19.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 4.0.7-200.fc21.x86_64 type: libreport
[root@localhost ~]# audit2allow -i avc -R require { type dnssec_trigger_t; type NetworkManager_var_run_t; class sock_file write; } #============= dnssec_trigger_t ============== #!!!! This avc is allowed in the current policy allow dnssec_trigger_t NetworkManager_var_run_t:sock_file write; [root@localhost ~]# rpm -q selinux-policy selinux-policy-3.13.1-105.13.fc21.noarch Could you attach your AVC?
Description of problem: Wakeup from suspend. Version-Release number of selected component: selinux-policy-3.13.1-105.19.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 4.0.7-200.fc21.x86_64 type: libreport
Created attachment 1050721 [details] AVCs since new selinuc-policy and reboot Here are all AVCs on this system that have occurred since selinux-policy-targeted-3.13.1-105.19.fc21.noarch was installed and the system was rebooted on July 4. The system was also rebooted again on July 10, and you can see AVCs after that time as well. See also bug #1241989.
Created attachment 1050723 [details] AVCs since autorelabel, reboot. I also just did a touch /.autorelabel, reboot. Here are the new AVCs. It seems that these AVCs appear on each reboot.
commit 64a70229de72f596c6c5fd874d13aaae6794dbe6 Author: Lukas Vrabec <lvrabec> Date: Thu Apr 9 17:57:43 2015 +0200 Label new dnssec-trigger files.
Hi, I added some fixes to F21. I'll create F21 build&&update ASAP for testing.
selinux-policy-3.13.1-105.20.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-105.20.fc21
Package selinux-policy-3.13.1-105.20.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.13.1-105.20.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12049/selinux-policy-3.13.1-105.20.fc21 then log in and leave karma (feedback).
I have selinux-policy-targeted.noarch 3.13.1-105.20.fc21 I don't think this got fixed as I am still getting this AVC: SELinux is preventing dnssec-trigger- from write access on the sock_file private. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that dnssec-trigger- should be allowed write access on the private sock_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 dnssec-trigger- /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:dnssec_trigger_t:s0 Target Context system_u:object_r:NetworkManager_var_run_t:s0 Target Objects private [ sock_file ] Source dnssec-trigger- Source Path dnssec-trigger- Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.20.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux j 4.1.4-100.fc21.x86_64 #1 SMP Tue Aug 4 03:25:05 UTC 2015 x86_64 x86_64 Alert Count 8 First Seen 2015-08-09 11:21:39 PDT Last Seen 2015-08-09 11:25:06 PDT Local ID f596bdad-650d-4352-bae3-e9962fc767db Raw Audit Messages type=AVC msg=audit(1439144706.874:426): avc: denied { write } for pid=2617 comm="dnssec-trigger-" name="private" dev="tmpfs" ino=17079 scontext=system_u:system_r:dnssec_trigger_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=sock_file permissive=0 Hash: dnssec-trigger-,dnssec_trigger_t,NetworkManager_var_run_t,sock_file,write
selinux-policy-3.13.1-105.20.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
see comment 14
commit 2c6d2b70ac152f33d386eca07037452db234e98a Author: Lukas Vrabec <lvrabec> Date: Sun Aug 23 18:53:18 2015 +0200 Fix networkmanager_sigchld interface.
selinux-policy-3.13.1-105.21.fc21 has been submitted as an update to Fedora 21. https://bugzilla.redhat.com/show_bug.cgi?id=1208742
selinux-policy-3.13.1-105.21.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14070
selinux-policy-3.13.1-105.21.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.