Re: SSHA for rootdn issue

[Peter Marschall <peter@adpm.de>]

Hi,

On Sunday 10 August 2003 19:28, Todd Lyons wrote:
> Peter Marschall wanted us to know:
> >> > dn: uid=codywang,ou=People,dc=clunet,dc=edu
> >> > userPassword:: e0NSWVBUfUxTLi4ydnRhTXllbGc=
> >>
> >> base64 decoded password results in: '{CRYPT}LS..2vtaMyelg', but
> >> crypt.crypt('secret', 'LS') (generate crypt with seed 'LS') results
> >> 'LSgOjE04PUmqs'. Is there a reason for using bas64 coded strings?
> >
> >When doing a ldapsearch, user passwords are returned base 64 encoded.
> >I don't know the exact reason for this behaviour but I assume it's the
> > curly braces that make ldapsearch behave this way.
>
> The two colons (::) indicate that it's base64 encoded.  As for the
> reason, I don't know.

Right, the double colons indicate base64 encoding but they are
not its cause.
I was speculating about the cause for the base64 encoding of
userPassword strings in ldapsearch.

Peter

-- 
Peter Marschall
eMail: peter@adpm.de