Red Hat Bugzilla – Bug 1144448
sudo with ldap doesn't work correctly with 'listpw=all' and 'verifypw=all' in sudoOption entry
Last modified: 2015-07-22 03:36:09 EDT
The same problem in rhel6, tested with sudo-1.8.6p3-15.el6 +++ This bug was initially created as a clone of Bug #1144446 +++ Description of problem: sudo with ldap doesn't work correctly with 'listpw=all' in sudoOption entry I have following sudoers entries in ldap: dn: cn=defaults,ou=Sudoers,dc=my-domain,dc=com objectClass: top objectClass: sudoRole sudoOption: !requiretty sudoOption: listpw=all cn: defaults # rule1, Sudoers, my-domain.com dn: cn=rule1,ou=Sudoers,dc=my-domain,dc=com objectClass: top objectClass: sudoRole cn: rule1 sudoHost: ALL sudoUser: userallowed sudoCommand: ALL dn: cn=rule2,ou=Sudoers,dc=my-domain,dc=com objectClass: top objectClass: sudoRole cn: rule2 sudoHost: ALL sudoUser: userallowed2 sudoCommand: /usr/bin/true sudoOption: !authenticate dn: cn=rule3,ou=Sudoers,dc=my-domain,dc=com objectClass: top objectClass: sudoRole cn: rule3 sudoHost: ALL sudoUser: userallowed2 sudoCommand: /usr/bin/date sudoOption: !authenticate [test]su - userallowed2 -c 'sudo -l' su: warning: cannot change directory to /home/userallowed2: No such file or directory sudo: no tty present and no askpass program specified [test]echo $? 1 Sudo -l shouldn't require password and it should list allowed commands Version-Release number of selected component (if applicable): sudo-1.8.6p7-11.el7 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I have the same problem with 'verifypw=all' ldap entries are the same, just change listpw to verifypw. Then run su - userallowed2 -c 'sudo -v' (instead of sudo -l)
I'm missing debug logs here. They were included in other BZs related to sssd/ldap. Please attach them, thanks!
Reported upstream: http://www.sudo.ws/pipermail/sudo-workers/2015-March/000865.html
Created attachment 997427 [details] proposed patch Upstream reference: http://www.sudo.ws/repos/sudo/rev/5bc60a34a477
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. https://rhn.redhat.com/errata/RHSA-2015-1409.html