ldapadd -W with -w password parameter causes assertion failure

[dcam]

Binary package hint: slapd

Very easy to reproduce, don't even need an ldap server up and running:

dcampbel@vostro-local:~$ /usr/bin/ldapadd -x -W -D 'cn=whatever' -w 'whatever'
ldapadd: /build/buildd/openldap-2.4.23/clients/tools/common.c:1363: tool_bind: Assertion `passwd.bv_val == ((void *)0) && passwd.bv_len == 0' failed.
Aborted

As requested, here's the system info:

dcampbel@vostro-local:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
dcampbel@vostro-local:~$ apt-cache policy slapd
slapd:
  Installed: 2.4.23-0ubuntu3.3
  Candidate: 2.4.23-0ubuntu3.3
  Version table:
 *** 2.4.23-0ubuntu3.3 0
        500 http://mirror.aarnet.edu.au/pub/ubuntu/archive/ maverick-updates/main i386 Packages
        100 /var/lib/dpkg/status
     2.4.23-0ubuntu3 0
        500 http://mirror.aarnet.edu.au/pub/ubuntu/archive/ maverick/main i386 Packages

[James Page (james-page)]

I can confirm that running the command above on a clean maverick install with slapd + ldaputils generates the error as described above. This is a change in behaviour from lucid where the command above returns:

ldap_bind: Invalid credentials (49)

You can work around this by not specifying the -W option (Prompt for simple authentication) - it appears that in the version of ldaputils in maverick [-W] and [-w passwd] conflict with each other.

[Ryan Tandy (rtandy)]

This was reported upstream as ITS#6849, and fixed in OpenLDAP 2.4.25.