Re: [courier-users] Changing user passwords

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============1140794362==
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-6026-1186955270-0001";
micalg=pgp-sha1; protocol="application/pgp-signature"

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-6026-1186955270-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Lisa Muir writes:

> On 8/12/07, Sam Varshavchik <mrsam@courier-mta.com> 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.


--=_mimegpg-commodore.email-scan.com-6026-1186955270-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBGv4AGx9p3GYHlUOIRAsoFAJ4wPj4cr5MZHHBI7Jj08z 95YRnjkACfbM3W
x+hVVIhHVvXqAzJ4d2bRHKk=
=h5wc
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-6026-1186955270-0001--


--===============1140794362==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
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/
--===============1140794362==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

--===============1140794362==--