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:

When an rsyslog server is configured to use GSSAPI authentication, the generated ticket (/tmp/host_0 by default) has no default label. When the host is rebooted, this ticket gets relabeled to 'user_tmp_t' (from 'krb5_host_rcache_t'). The rsyslog server attempts to remove the ticket to reacquire credentials, but does not have 'unlink' privileges for that domain. Removing the '/tmp/host_0' file and restarting rsyslog resolves the issue.


Version-Release number of selected component (if applicable):

rsyslog-5.8.10-8.el6.x86_64

How reproducible:

Very

Steps to Reproduce:
1. Set up GSSAPI-authed rsyslog server and 'service rsyslog start'
2. Reboot the machine. The old KRB ticket should still be in /tmp
3. rsyslog fails to perform GSSAPI auth. In the rsyslog log, this message repeats: "GSS-API Context initialization failed"

Moving to selinux-policy.

Please provide the AVCs:

# ausearch -m avc -m user_avc -m selinux_err -i -ts today