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.
DescriptionMilan Kerslager
2015-02-01 22:46:07 UTC
The non-working line in /etc/sysconfig/saslauthd is:
#DAEMONOPTS=--user saslauth
The working line should be with quotes around argument:
#DAEMONOPTS="--user saslauth"
The line is example for running saslauthd with another authentication method than "pam". I use "rimap" and because this, the daemon should not be run as root which is why the line is here.
The second bug is that the socketdir (SOCKETDIR=/var/run/saslauthd) owned by this package should be owned by saslauth (currently is owned by root). If saslauthd is running as root, ownership does not matter. If saslauthd is running under saslauth user, the daemon is unable to create the socket. The user may change ownership, but after update, the working setup breaks (bacuse ownership will be reverted to the root).
I have working example here (rimap authentication through stunnel to the machine with IMAP daemon running).
The package cyrus-sasl-2.1.23-15.el6_6.2.x86_64 still has the bug with ownership. Current status (just FYI):
drwxr-xr-x. 2 root root 4096 Mar 27 12:15 /var/run/saslauthd
It should be:
$ ls -ld /var/run/saslauthd
drwxr-xr-x. 2 saslauth root 4096 Mar 27 12:15 /var/run/saslauthd
The ownership should be root:saslauth, not as I wrote above, because the solution above allows saslauth user to change ownership or mode of this directory which is what should be avoided.
Thank you for this report.
I tested the whole use case and it seems to be feasible to fix this issu at least to the same extent as in RHEL7. Both changes are required to fix the problem. Proposing for next release.
When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Production Phase 2.
https://access.redhat.com/support/policy/updates/errata#Production_2_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released". Additionally, this issue has been resolved in Red Hat Enterprise Linux 7 which is still in Production Phase 1. Please consider upgrading to RHEL 7 where less than critical bugs, hardware enablement and feature requests can be addressed. Please re-open this Bugzilla if it is production impacting and critical for the customer and provide a thorough business justification.
Jakub --
This ticket was submitted 2015-02-01.... so, while it may be true that 6.x is *now* in production phase 2, it doesn't really explain why the ticket wasn't addressed in the intervening year+.
FWIW, I've moved on to a different organization, but this issue has caused problems in production for an active RH customer.
It was not fixed during last year, because we didn't update cyrus-sasl package since 2014 in RHEL6. There was no significant customer demand.
If this bug has production impact on you or any other customer, please reach for our Red Hat support and possibly reopen with justification as mentioned in the previous comment.