Cyrus IMAP Presentation

[Luca Olivetti]

Rob Siemborski wrote:

>>saslauthd won't care what OpenLDAP is linked against.  saslauthd talks to some
>>mechanism like PAM.
> 
> 
> Saslauthd can also use LDAP directly, in which case it needs to link
> libldap and liblber.

Yes, but what happens if openldap is compiled againts sasl v1?

$ ldd /usr/sbin/saslauthd
         libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x4002e000)
         libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40041000)
         libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x4009d000)
         libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x400b0000)
         libresolv.so.2 => /lib/libresolv.so.2 (0x400b3000)
         libcrypt.so.1 => /lib/libcrypt.so.1 (0x400c5000)
         libpam.so.0 => /lib/libpam.so.0 (0x400f2000)
         libldap.so.2 => /usr/lib/libldap.so.2 (0x400fa000)
         liblber.so.2 => /usr/lib/liblber.so.2 (0x4012a000)
         libc.so.6 => /lib/libc.so.6 (0x40136000)
         libdl.so.2 => /lib/libdl.so.2 (0x40272000)
         libnsl.so.1 => /lib/libnsl.so.1 (0x40275000)
 >>>>>   libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4028b000)
         libssl.so.0 => /usr/lib/libssl.so.0 (0x40299000)
         libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0x402c7000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
         libdb-3.3.so => /lib/libdb-3.3.so (0x4038a000)

What are my options if I want to provide an useful package right out of 
the box?

1) wait until the rest of the distribution catches up to sasl v2
2) tell the users to recompile openldap without sasl support
3) compile saslauthd without ldap support


1) is not really an option, 2) don't know the side effects and 3) maybe 
is the only good solution, provided that it works through pam_ldap 
without bombing.


Bye
-- 
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004      Fax +34 93 5883007