[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: ldappasswd in OPENLDAP 2.0.7
That's a bug which you should report using our Issue Tracking
System...
Kurt
At 05:49 PM 3/8/01 +0900, Manabe Atsushi wrote:
>Hi
>
>I found a small incompatibility in clients/tools/ldappasswd
>between 2.0.7 and 1.x.x .
>It is very trivial but people (including me :-) can
>be confused very much.
>
>The old version (1.x.x), you can type "user" DN including
>lower case characters in the ldappaswd operand.
>But in 2.0.7 you must type "user" in upper case characters.
>
>
>ldappasswd [-A] [-a oldPasswd] [-C] [-D binddn] [-d debu-
> glevel] [-H ldapuri] [-h ldaphost] [-n] [-p ldapport] [-S]
> [-s newPasswd] [-v] [-W] [-w passwd] [-O security-proper-
> ties] [-I] [-Q] [-U username] [-x] [-X authzid] [-Y mech]
> [-Z[Z]] [user]
> ^^^^^^
>
>For example, under tests/scripts/test010-passwd situation.
>(omitted port and host operands)
>
>ldappasswd -S -W -D "cn=Manager, o=University of Michigan, c=US" \
> "cn=sha,o=University of Michigan, c=US"
>
>does not work (was worked with OPENLDAP 1.x.x).
>
>instead,
>
>ldappasswd -S -W -D "cn=Manager, o=University of Michigan, c=US" \
> "CN=SHA,O=UNIVERSITY OF MICHIGAN, C=US"
>
>works!
>
>It may be caused by rewritten code using
>ldap_extended_operation() with RFC3062,
>but ldappasswd does not change case by itself.
>
>I hope the next version will fix it.
>
>A.Manabe KEK,Japan