Bug 1036861

Summary: SELinux is preventing /usr/sbin/runuser from 'write' accesses on the sock_file system_bus_socket.
Product: [Fedora] Fedora Reporter: Jared Smith <jsmith.fedora>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dominick.grift, dwalsh, jsmith.fedora, lvrabec, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0366fe8f67a3cbd6dae70d224789f023f8c6ce9c4f351725d39f9eba0e5fde35
Fixed In Version: selinux-policy-3.12.1-116.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-16 07:09:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jared Smith 2013-12-02 19:09:24 UTC
Description of problem:
Using my system (swiching between Firefox for web browsing and Evolution for email), when I saw this alert.
SELinux is preventing /usr/sbin/runuser from 'write' accesses on the sock_file system_bus_socket.

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

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

Additional Information:
Source Context                system_u:system_r:logrotate_t:s0-s0:c0.c1023
Target Context                system_u:object_r:system_dbusd_var_run_t:s0
Target Objects                system_bus_socket [ sock_file ]
Source                        runuser
Source Path                   /usr/sbin/runuser
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           util-linux-2.24-2.fc20.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-90.fc20.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.11.8-300.fc20.x86_64 #1 SMP Wed
                              Nov 13 16:34:27 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-12-02 14:08:01 EST
Last Seen                     2013-12-02 14:08:01 EST
Local ID                      f66d022f-b976-463b-9a04-787dba11e6fc

Raw Audit Messages
type=AVC msg=audit(1386011281.977:1838): avc:  denied  { write } for  pid=27575 comm="runuser" name="system_bus_socket" dev="tmpfs" ino=11050 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:system_dbusd_var_run_t:s0 tclass=sock_file


type=SYSCALL msg=audit(1386011281.977:1838): arch=x86_64 syscall=connect success=no exit=EACCES a0=3 a1=7fff2740c9b0 a2=21 a3=0 items=0 ppid=27574 pid=27575 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=27 tty=(none) comm=runuser exe=/usr/sbin/runuser subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null)

Hash: runuser,logrotate_t,system_dbusd_var_run_t,sock_file,write

Additional info:
reporter:       libreport-2.1.9
hashmarkername: setroubleshoot
kernel:         3.11.8-300.fc20.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2013-12-03 10:23:11 UTC
Do you have a custom logrotate script?

Comment 2 Miroslav Grepl 2013-12-03 10:26:27 UTC
commit cc15ae8dbb8e9987d724c3f760913963373cf6ee
Author: Miroslav Grepl <mgrepl>
Date:   Tue Dec 3 11:26:10 2013 +0100

    Allow runuser running as logrotate connections to system DBUS

Comment 3 Jared Smith 2013-12-03 16:14:58 UTC
No this is a very standard F20 installation.

Comment 4 Fedora Update System 2014-01-13 22:55:11 UTC
selinux-policy-3.12.1-116.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-116.fc20

Comment 5 Fedora Update System 2014-01-15 05:56:50 UTC
Package selinux-policy-3.12.1-116.fc20:
* should fix your issue,
* was pushed to the Fedora 20 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.12.1-116.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-0806/selinux-policy-3.12.1-116.fc20
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-01-16 07:09:20 UTC
selinux-policy-3.12.1-116.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.