Hi,

I'm trying to change my user password in the ldap backend using courier authtest user oldpassword newpassword.

Courier does change the userPassword hash in the backend, but after that I can no longer bind with the ldap as the specified user. It creates the following password hash field for the password "test":

userPassword:: e1NIQTUxMn03aWF3M1VyMzUwbXFHbzdqd1FycGtqOWhpWUIzTGtjL2lCbWwxSlF
 PRGJKNndZWDRvT0hWK0UrSXZJaC8xbnNVTnpMREJNeGZxYTJPYjFmMUFDaW8vdz09

Which, base64 decoded amounts to:

userPassword:: {SHA512}7iaw3Ur350mqGo7jwQrpkj9hiYB3Lkc/iBml1JQODbJ6wYX4oOHV+E+IvIh/1nsUNzLDBMxfqa2Ob1f1ACio/w==

My backend doesn't understand {SHA512}, it understands {SHA}, but I would actually like to use {SSHA}. Is it possible to somehow tell courier what algorithm to use?

Regards,
Sebastiaan

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to