Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1227397 - SELinux is preventing NetworkManager from 'execute' accesses on the file dnssec-trigger-script.
Summary: SELinux is preventing NetworkManager from 'execute' accesses on the file dnss...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:926789e4a2eed3b2750eaf2fcaa...
Depends On:
Blocks: Default_Local_DNS_Resolver 1223110
TreeView+ depends on / blocked
 
Reported: 2015-06-02 14:57 UTC by Tomáš Hozza
Modified: 2015-07-21 11:36 UTC (History)
7 users (show)

Fixed In Version: selinux-policy-3.13.1-128.1.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-11 18:38:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Tomáš Hozza 2015-06-02 14:57:54 UTC 
Description of problem:
NetworkManager dispatcher is executing dnssec-trigger-script on each network configuration change. This happened with dnssec-triggerd enabled when booting up the system.
SELinux is preventing NetworkManager from 'execute' accesses on the file dnssec-trigger-script.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that NetworkManager should be allowed execute access on the dnssec-trigger-script 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 NetworkManager /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:NetworkManager_t:s0
Target Context                system_u:object_r:dnssec_trigger_exec_t:s0
Target Objects                dnssec-trigger-script [ file ]
Source                        NetworkManager
Source Path                   NetworkManager
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-126.fc22.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.0.4-303.fc22.x86_64 #1 SMP Thu
                              May 28 12:37:06 UTC 2015 x86_64 x86_64
Alert Count                   1
First Seen                    2015-06-02 16:24:37 CEST
Last Seen                     2015-06-02 16:24:37 CEST
Local ID                      e30e878c-cb69-4e9b-9941-93e6e23e52e4

Raw Audit Messages
type=AVC msg=audit(1433255077.753:463): avc:  denied  { execute } for  pid=1355 comm="NetworkManager" name="dnssec-trigger-script" dev="dm-1" ino=292581 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:dnssec_trigger_exec_t:s0 tclass=file permissive=0


Hash: NetworkManager,NetworkManager_t,dnssec_trigger_exec_t,file,execute

Version-Release number of selected component:
selinux-policy-3.13.1-126.fc22.noarch

Additional info:
reporter:       libreport-2.5.1
hashmarkername: setroubleshoot
kernel:         4.0.4-303.fc22.x86_64
type:           libreport
Comment 1 Miroslav Grepl 2015-06-02 15:37:59 UTC 
commit 754b7715a77345afccf0abb7e2a6e1e4a959aa2d
Author: Miroslav Grepl <mgrepl>
Date:   Tue Jun 2 17:36:27 2015 +0200

    Allow NM to execute dnssec-trigger-script in dnssec_trigger_t domain. BZ(1227397)
Comment 2 Langdon White 2015-06-08 17:29:38 UTC 
Description of problem:
enabling unbound per steps here: https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
restarted NetworkManager

Version-Release number of selected component:
selinux-policy-3.13.1-126.fc22.noarch

Additional info:
reporter:       libreport-2.5.1
hashmarkername: setroubleshoot
kernel:         4.0.4-303.fc22.x86_64
type:           libreport
Comment 3 Tomáš Hozza 2015-06-09 07:33:26 UTC 
When can we expect the updated selinux-policy in F22?

This issue badly influences the user experience of the planned F23 change. We need it to work, otherwise users will not be willing to accept it.

Thank you.
Comment 4 Fedora Update System 2015-06-09 14:39:37 UTC 
selinux-policy-3.13.1-128.1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-128.1.fc22
Comment 5 Matthew Miller 2015-06-09 23:06:18 UTC 
Description of problem:
Testing DNSSEC feature https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver -- presumably this will need to work

Version-Release number of selected component:
selinux-policy-3.13.1-126.fc22.noarch

Additional info:
reporter:       libreport-2.5.1
hashmarkername: setroubleshoot
kernel:         4.0.4-303.fc22.x86_64
type:           libreport
Comment 6 Fedora Update System 2015-06-10 19:11:23 UTC 
Package selinux-policy-3.13.1-128.1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 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-128.1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-9714/selinux-policy-3.13.1-128.1.fc22
then log in and leave karma (feedback).
Comment 7 Fedora Update System 2015-06-11 18:38:08 UTC 
selinux-policy-3.13.1-128.1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.