[Pkg-openldap-devel] Bug#365409: slapd: segfaults on entry modify

[Steinar H. Gunderson]

On Sun, Apr 30, 2006 at 02:34:17AM -0700, Steve Langasek wrote:
> So, it's pretty non-obvious how this value has changed from being
> LDAP_MOD_REPLACE in bdb_modify_internal, to something else in
> modify_add_values.  It seems to be either a very strangely-consistent
> threading bug, a subtle stack smash that I'm not seeing by looking at the
> code, or a bug in the hardware/kernel.  Determining which of these it is
> will take somebody stepping through the code with a debugger to see what's
> going on.

I'm completely unable to reproduce this. I've dug out the NSLU2 with latest
sid and installed slapd on it, and although my experience with LDAP is
limited, ldapmodify seems to go through just fine:

  kose:~# ldapmodify -W -x -D cn=admin,dc=nodomain
  Enter LDAP Password:
  dn: cn=admin,dc=nodomain
  userPassword:: e2NyeXB0fUJhYzdXMjhxb2RTOW8=

  modifying entry "cn=admin,dc=nodomain"

  kose:~#

(The hash is of "admin", so you can spare yourself the cracking :-) )

The bug is reported against a quite old version (2.2.26-5) of slapd; the
latest version is 2.3.23-1. Unfortunately, snapshot.debian.net doesn't have
this version for arm, but it has 2.2.26-4.0.1. I downgraded slapd, ldap-utils
and libldap-2.2 (purging slapd first), but everything worked just as with
2.3.

I haven't tried your exact configuration file, but it's nearly identical to
what I have (the main differences being samba.schema and the domain names),
so I doubt this is the problem. I'm quite willing to write this off as either
BrokenDB corruption or hardware error... Steve?

/* Steinar */
-- 
Homepage: http://www.sesse.net/