Red Hat Bugzilla – Bug 1034560
RFE: Investigate pmcd saslauthd integration and whether this can be default enabled
Last modified: 2016-07-19 16:03:55 EDT
Description of problem: When working on SASL authentication in pmcd, it was noticed that use of the saslauthd mechanism did not complete the authentication correctly. It appears to reject everything pmcd passes to it, including what pmcd believes to be valid username and password combinations. We know these are making their way successfully into saslauthd, as it logs a message to its logfile saying authentication attempt rejected, every time. Other forms of SASL authentication attempted appear to work as expected. Once working, we should consider further whether this can be enabled by default. The only other confounding factor here (AFAIK) is that to do so, we will need a packaging dependency on the saslauthd package - which may not be a default install. It runs as root too (saslauthd, that is, as it needs to read the shadow passwd file), so it may be some people have a problem with having such a dependency in pcp. Version-Release number of selected component (if applicable): pcp-3.8.x and later. How reproducible: Every time. Steps to Reproduce: 1. Configure /etc/sasl2/pmcd.conf to use saslauthd for password checking 2. Check detailed notes in lab.secure.html in pcp-doc package. 3. Attempt an authenticated connection Actual results: User is not authenticated, connection attempt is rejected. Expected results: User should be allowed to proceed on with an authenticated connection if valid credentials are passed, accessing performance data and so on. Additional info:
Possibly related; SELinux may be involved (RHEL6 host tested). https://lists.fedoraproject.org/pipermail/selinux/2013-January/015038.html $ getsebool -a | grep sasl allow_saslauthd_read_shadow --> off
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Note also that pmdaroot(1) now provides us an option to solve the underlying problem here, and in a way that doesn't depend on any additional packages or external daemons running.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.