Bug 1167134

Summary: SELinux is preventing /usr/sbin/unbound-control from 'write' accesses on the file /run/dnssec-trigger/lock.
Product: [Fedora] Fedora Reporter: William Brown <william>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: dominick.grift, dwalsh, lvrabec, mgrepl, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:de983f9e38eb5b1f7314d2e5a5ae1dce941a71ae494fc1f1099b9ea4ef52bfd7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 10:42:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description William Brown 2014-11-23 23:21:11 UTC
Description of problem:
when dnssec-triggerd ran, as a staff_t confined user.
SELinux is preventing /usr/sbin/unbound-control from 'write' accesses on the file /run/dnssec-trigger/lock.

*****  Plugin leaks (86.2 confidence) suggests   *****************************

If you want to ignore unbound-control trying to write access the lock file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# grep /usr/sbin/unbound-control /var/log/audit/audit.log | audit2allow -D -M mypol
# semodule -i mypol.pp

*****  Plugin catchall (14.7 confidence) suggests   **************************

If you believe that unbound-control should be allowed write access on the lock 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 unbound-control /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:named_t:s0
Target Context                system_u:object_r:dnssec_trigger_var_run_t:s0
Target Objects                /run/dnssec-trigger/lock [ file ]
Source                        unbound-control
Source Path                   /usr/sbin/unbound-control
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           unbound-1.5.0-1.fc21.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-92.fc21.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.17.3-300.fc21.x86_64 #1 SMP Fri
                              Nov 14 23:36:19 UTC 2014 x86_64 x86_64
Alert Count                   824
First Seen                    2014-11-17 14:38:19 ACDT
Last Seen                     2014-11-24 09:45:55 ACDT
Local ID                      a9f02046-d160-4715-ab02-4e976fc2cf29

Raw Audit Messages
type=AVC msg=audit(1416784555.405:432): avc:  denied  { write } for  pid=2448 comm="unbound-control" path="/run/dnssec-trigger/lock" dev="tmpfs" ino=26529 scontext=system_u:system_r:named_t:s0 tcontext=system_u:object_r:dnssec_trigger_var_run_t:s0 tclass=file permissive=0


type=SYSCALL msg=audit(1416784555.405:432): arch=x86_64 syscall=execve success=yes exit=0 a0=1a0b860 a1=1a0b890 a2=7fff7fe33488 a3=30 items=0 ppid=2444 pid=2448 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=unbound-control exe=/usr/sbin/unbound-control subj=system_u:system_r:named_t:s0 key=(null)

Hash: unbound-control,named_t,dnssec_trigger_var_run_t,file,write

Version-Release number of selected component:
selinux-policy-3.13.1-92.fc21.noarch

Additional info:
reporter:       libreport-2.3.0
hashmarkername: setroubleshoot
kernel:         3.17.3-300.fc21.x86_64
type:           libreport

Potential duplicate: bug 1147608

Comment 1 Lukas Vrabec 2014-11-24 10:42:37 UTC

*** This bug has been marked as a duplicate of bug 1147705 ***