Re: Issue 26 in nsscache: ldapsource "x" hack results in "pam_acct_mgmt: 7" (Authentication failure)

[nssc...@googlecode.com]

Updates:
Status: Accepted

Comment #1 on issue 26 by j...@spacepants.org: ldapsource "x" hack results
in "pam_acct_mgmt: 7" (Authentication failure)
http://code.google.com/p/nsscache/issues/detail?id=26

Thanks to that comment that I probably wrote many years ago, there's no way
to know why we used 'x' instead of '*'. I'm submitting the change; please
try it out.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[nssc...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 26 by j...@spacepants.org: ldapsource "x" hack results

in "pam_acct_mgmt: 7" (Authentication failure)
http://code.google.com/p/nsscache/issues/detail?id=26

This issue was closed by revision 0fbbf2b6aa71.

[nssc...@googlecode.com]

Comment #3 on issue 26 by j...@spacepants.org: ldapsource "x" hack results

in "pam_acct_mgmt: 7" (Authentication failure)

https://code.google.com/p/nsscache/issues/detail?id=26

This change was done in error. The documentation (passwd(5)) states that *
marks locked accounts, and 'x' or other indicates that /etc/shadow should
be used.

See #35