Bug 25889
Summary: | pam_unix.so prevents pam_ldap.so from updating passwords | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Christopher Barton <cpbarton> |
Component: | pam | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED RAWHIDE | QA Contact: | Aaron Brown <abrown> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | Florence RC-1 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-05 22:50:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christopher Barton
2001-02-03 20:01:47 UTC
Server & client are separate machines, both i386 Fisher. This most likely has to do with the fact that /usr/share/openldap/migration/migrate_passwd.pl produces userPassword LDAP attributes that start with {CRYPT} but these somehow get mangled by the time the hash goes into the LDAP server. My previous additional comment is lame, please ignore it. When I comment password /lib/security/pam_unix.so ... out of /etc/pam.d/system-auth, I can once again update passwords with LDAP. I guess the bug is related to pam & pam_unix more than a problem in pam_ldap. This is still an annoying bug, but maybe not one for nalin. When I replace /lib/security/pam_unix.so in Fisher with pam_unix.so from Guinness, the bug disappears. You can probably safely consider this a pam bug. I guess nalin gets those too? Busy guy. :) We (Red Hat) should really try hard to fix this before next release. Thinko in pam_unix's password-changing code. Should be fixed in pam-0.74-5, coming soon to a Raw Hide snapshot (ftp://ftp.redhat.com/pub/rawhide/) near you. Please reopen this bug if you find this continues to be a problem after applying the update. Thanks! Will definitely do, thanks! |