[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Assertion in dnNormalize after SASL authentication (ITS#1696)
Thanks. I'm in the process of rewriting the parse routine so all of this
will
be changed soon.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support
> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of simon@sxw.org.uk
> Sent: Thursday, March 28, 2002 10:21 AM
> To: openldap-its@OpenLDAP.org
> Subject: Assertion in dnNormalize after SASL authentication (ITS#1696)
>
>
> Full_Name: Simon Wilkinson
> Version: 2.1.0alpha
> OS: Linux
> URL:
> Submission from: (NULL) (62.6.93.21)
>
>
> slap_parseURI calls dnNormalize2 with the length of the berval
> set to 1, rather
> than
> the correct length of the string. This causes dnNormalize to
> assert. The code
> that does this is marked with a FIXME - I guess the time has come
> to fix it.
>
> I believe that a minimal fix is to change
>
> is_dn: bv.bv_len = 1;
>
> to
>
> is_dn: bv.bv_len = strlen(bv.bv_val);
>
> It would also be possible to tidy the code to remove the 'goto',
> and neaten
> the codepath, but at the expense of an additional call to
> strncasecmp in some
> situations. Let me know if you're interested in a patch for that.