RE: ldap_sasl_interactive_bind_s leaks? (ITS#2423)

[hyc@highlandsun.com]

> -----Original Message-----
> From: Igor Brezac [mailto:igor@ipass.net]

> Thanks.  This makes more sense. However, there is still a leak and this
> time it is in DIGEST-MD5.  I tried PLAIN and CRAM-MD5 and it works fine
> with those.  I am going to try to profile DIGEST-MD5 plugin and see what
> happens.

Yes, I see the same result.

> I want to be able to call ldap_sasl_interactive_bind_s() multiple times
> without having to ldap_unbind() and then ldap_init(ialize)().  Is it
> designed not to work this way or am I missing something?

The current design won't work this way. The SASL client session is created in
ldap_initialize and closed in ldap_unbind. You would need to close the SASL
session and create a new one before trying to do a new SASL bind. The server
behaves the same way, and would need reorganizing as well. I suppose one
could argue that the current design is wrong. Please file a new ITS if you
want to pursue it, as that is a separate topic.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support