Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Re^2: Need help on Net::LDAP

by MidLifeXis (Prior)
on Apr 30, 2008 at 17:48 UTC ( #683744=note: print w/ replies, xml ) Need Help??


in reply to Re: Need help on Net::LDAP
in thread Need help on Net::LDAP

No, s/he posted a base-64 encoded unix crypted (yeah, I know it is redundant, but that is the LDAP spec) password. So it would not take as much time.

Update: I may be wrong on this - it appears the data I was using may not be entirely reliable. However, the encouragement below still stands.

srinivas_rocks, I would also encourage you to change the password on the displayed account.

--MidLifeXis


Comment on Re^2: Need help on Net::LDAP
Re^3: Need help on Net::LDAP
by ghenry (Vicar) on May 03, 2008 at 20:08 UTC

    What do you mean by redundant?

    Walking the road to enlightenment... I found a penguin and a camel on the way.....
    Fancy a yourname@perl.me.uk? Just ask!!!

      A crypted password, in the traditional unix sense, should be 13 characters long, and already in a base-64ish representation. It appeared to me, after reading a couple of incomplete sites documenting how this works in LDAP, is that since the password field is binary, it is always base64 encoded. This can be read as base64 encoding a string that is already base64 encoded.

      I have since questioned the data I based my conclusion on, and all I can say at this point is... "I don't know" :)

      --MidLifeXis

        It actually comes from rfc2849:

        The LDAP Data Interchange Format (LDIF) - Technical Specification:

              4)  Any dn or rdn that contains characters other than those
                  defined as "SAFE-UTF8-CHAR", or begins with a character other
                  than those defined as "SAFE-INIT-UTF8-CHAR", above, MUST be
                  base-64 encoded.  Other values MAY be base-64 encoded.  Any
                  value that contains characters other than those defined as
                  "SAFE-CHAR", or begins with a character other than those
                  defined as "SAFE-INIT-CHAR", above, MUST be base-64 encoded.
                  Other values MAY be base-64 encoded.

        So since we have

        {crypt}
        the
        {
        triggers the base64 encoding if you slapcat the Directory data out into LDIF. it has nothing to do with whom or what added the {crypt} data to the directory in the first place.

        Walking the road to enlightenment... I found a penguin and a camel on the way.....
        Fancy a yourname@perl.me.uk? Just ask!!!

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://683744]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (10)
As of 2014-10-25 16:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (145 votes), past polls