Re: (ITS#4180) slapd (back-sql) hangs/segfaults on SASL bind

[Nels@maei.ca]

On 18 Nov 2005 at 1:22, Pierangelo Masarati wrote:

> On Thu, 2005-11-17 at 17:05 -0700, Nels Lindquist wrote:
> 
> > Here they are (new backtrace, of course):
> > 
> > (gdb) p *((struct berval *)0xb71d7658)
> > $1 = {bv_len = 29, bv_val = 0xb67fa7b0 "cn=nels 
> > lindquist,o=maei,c=ca"}
> > (gdb) p *((struct berval *)0xb71d7650)
> > $2 = {bv_len = 1685217607, 
> >   bv_val = 0x47006e65 <Address 0x47006e65 out of bounds>}
> > 
> > Woah!  That second value is authzDN, and I'm betting it shouldn't be 
> > 1685217607 bytes long...
> 
> Did you actually give an authz id?  I didn't check that case (I'm going
> to).  Can you provide the "exact" (well, anonymized) command(s) you
> used?

I just tried again supplying -U [uid] and -X [uid] to the ldapsearch 
command, and it behaved in exactly the same way.  I assume the 
problem lies in converting the supplied authzid to a DN?  My 
slapd.conf has this line:

sasl-regexp  uid=(.*),cn=.*,cn=auth  ldap:///o=maei,c=ca??sub?uid=$1

----
Nels Lindquist <*>
Information Systems Manager
Morningstar Air Express Inc.