Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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;
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
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;