On Thu, 31 Jan 2002, Martin Feeney wrote:
> OK. I just did something similar. I left it as {crypt}, didn't bother
> base64 encoding. Iadded the user to my ldap database (and removed it from
> /etc/passwd) then I logged in with the old password just fine.
>
hmmm, another bit of rooting around indicated that passwords on one
machine do not necessarily work on another machine. I think thats the
problem I'm running into where different crypts are been used
> If the userPassword starts with $1$ then it's an md5, but setting the
> scheme to {crypt} means ldap will use the crypt(3) function to compare
> passwords - this recognises the $1$ as signifying md5 and the next 8
> chars as the salt.
>
I'll mess around with the different values of password-hash and see does
it produce anything
> To give some examples (I don't have SASL set up yet):
>
ok, I'll look into it. For the most part I have what you've had except
ldapsearch tells me to go away so at least I know it's something with the
password hash. Thanks for the help
--
Mel
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
