LDAP issue in Plugin

[Jon Snyder]

I think you're on to something there.  In doing some research, ldap_init()
calls sasl_client_init().  Perhaps that is causing some issues with the
callbacks that SASL uses or something.

Whomever wrote the comment "If any other plugin wants SASL this won't be
good..." probably knows at least WHY this is a problem, if not how to work
around it.

Thanks again.

Jon

On Wed, Sep 23, 2009 at 4:11 PM, Paul Aurich <paul at darkrain42.org> wrote:

> On Sep 23, 2009, at 15:45, Jon Snyder wrote:
>
>> That's exactly what I thought.  I went over it again at your suggestion
>> and simplified my LDAP method down to:
>>
>>
> <snip/>
>
>  Is it possible that some framework Adium uses is built against a different
>> version of OpenLDAP?  I'm just not sure what could be causing this, and like
>> you, I'm not sure why LDAP is even involved in the Jabber SSL process.
>>
>
> The issue is with the XMPP prpl's use of S*A*SL, not SSL, probably because
> LDAP uses it for authentication.
>
> I have no idea why it's crashing on you (being conversant in neither cyrus
> sasl's nor openldap's API), but the following snippet from libpurple's
> ./libpurple/protocols/jabber/libxmpp.c might (or might not) be pertinent:
>
>    /* XXX - If any other plugin wants SASL this won't be good ... */
> #ifdef HAVE_CYRUS_SASL
>    if ((ret = sasl_client_init(NULL)) != SASL_OK) {
>        purple_debug_error("xmpp", "Error (%d) initializing SASL.\n", ret);
>    }
> #endif
>
> ~Paul
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20090923/ba607224/attachment-0002.html>