[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: SSHA for rootdn issue
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
- --
Todd Lyons | Always carry a short length of fibre-optic cable.
Professional Geek | If you get lost, then you can drop it on the
| ground, wait 10 minutes, and ask the backhoe
http://www.mrball.net | operator how to get back to civilization.
Linux kernel 2.4.21-0.25mdk 7 users, load average: 0.01, 0.01, 0.02
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: http://www.mrball.net/todd.asc
iD8DBQE/NoDLIBT1264ScBURAh3yAJ9fxy3zBJCa6yEjwPmgh6HU1PomsACfVCFz
ZYPgQi2DItA1+9a8P3cm7o8=
=97r2
-----END PGP SIGNATURE-----