Bug 974932

Summary: selinux denies rsyslog to drop priviliges
Product: Red Hat Enterprise Linux 6 Reporter: Jens Kuehnel <bugzilla-redhat>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Michal Trunecka <mtruneck>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: dwalsh, ebenes, mmalik, mtruneck
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.7.19-208.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 10:31:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jens Kuehnel 2013-06-17 07:39:12 UTC
Description of problem:
rsyslog can drop privileges with option $PrivDropToUser and $PrivDropToGroup, but SElinux does not allow setuid/setgid.

Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-195.el6_4.10.noarch

How reproducible:
100%


Steps to Reproduce:
1. Create user rsyslog with: useradd -r rsyslog 
2. Remove line "$ModLoad imklog" to rsyslog.conf
3. Add line "$PrivDropToUser rsyslog" to rsyslog.conf
3. Fix permission in /var/log/ to allow writes
4. restart

Actual results:
could not set requested userid: Operation not permitted

Expected results:
no output, and eUID 


Additional info:
I created the following te to fix this:
module rsyslog-drop-priv 1.0;

require {
        type syslogd_t;
        class capability setuid;
        class capability setgid;
}

#============= syslogd_t ==============
allow syslogd_t self:capability setuid;
allow syslogd_t self:capability setgid;

Comment 2 Daniel Walsh 2013-06-18 15:49:29 UTC
02dd9555a1e7c22c1ce8276ca7e82dabc0a11223 fixes this in git.

Comment 3 Miroslav Grepl 2013-07-17 12:24:17 UTC
Back ported.

Comment 6 errata-xmlrpc 2013-11-21 10:31:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1598.html