Lisa Muir writes:
On 8/12/07, Sam Varshavchik <[EMAIL PROTECTED]> wrote:Lisa Muir writes:> Hi, > > I have a courier-mta config working with authldap > > I set the users up with SHA1 hashed passwords. If the users change the > passwords through sqwebmail as I instruct them to, the new passwords > get {crypt} hashed. > > To the best of my knowledge / recollection, that limits the passwords > to the first 8 characters entered, whereas sha1 doesn't. Is there > anyway to configure auth_password (i think this is the culprit) to use > sha1 instead of crypt? The new password should use the same hash function as the old password. It's going to be {crypt} only if authlib does not recognize the old password format. Give a specific example of an existing password.Here's what I had in the original password (as retrieved by authtest): Encrypted Password: {SSHA}0mzmds/alGA8jaRnrM49GDCdi+vJHiGS
Courier does not implement this hash function, so it does not recognize it, and falls back to crypt. You must be using authenticated binds, and have the LDAP server verify the password.
pgp8CRjHQzXfV.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
