Re: 2.0.4: inserting password

[kunkee@neosoft.com (Randy Kunkee)]

There used to be an option in ldapsearch (-B I recall) that would decode
(or perhaps suppress the encoding) of binary values so that you could
easily view them.  Was there a particular reason this was removed?

Randy

> On Tue, 3 Oct 2000, Kurt D. Zeilenga wrote:
> 
> > Date: Tue, 03 Oct 2000 15:47:05 -0700
> > From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
> > To: Jie Gao <J.Gao@isu.usyd.edu.au>
> > Cc: openldap-software@OpenLDAP.org
> > Subject: Re: 2.0.4: inserting password 
> > 
> > At 09:01 AM 10/4/00 +1100, Jie Gao wrote:
> > >Hi All,
> > >
> > >I have been trying to run a batch job to populate the database using
> > >perl-ldap. This includes inserting passwords, straight from a password
> > >file, along with other data.
> > >
> > >This is an example of what I used:
> > >
> > >            userPassword        =>      '{crypt}testtest',
> > >
> > >But the search result shows something like:
> > >
> > >    userPassword:: e2NyeXB0fXRlc3R0ZXN0
> > >
> > >'{crypt}'is not there anymore. This used to work with v1.2.
> > 
> > Note the double colon.  This means the value is base64 encoded.
> > 
> >   perl <<EOF
> >   use MIME::Base64;
> >   print "userPasswd=\"" . decode_base64('e2NyeXB0fXRlc3R0ZXN0') . "\"\n";
> >   EOF
> >   userPasswd="{crypt}testtest"
> 
> I like this little piece of code. :-) 
> 
> Thanks, and thanks to all who replied.
> 
> 
> Jie
> 
>