Rob:
> DIGEST-MD5 with LDAP won't work with out an LDAP auxprop plugin, since it
> needs the plaintext password (or DIGEST secret). (i.e. it won't work with
> saslauthd).
This is making since - Thanks. I'm assuming that the auxprop plugin method
doesn't use PAM and thus the LDAP authentication
On Sun, 24 Mar 2002, OCNS Consulting wrote:
> > DIGEST-MD5 with LDAP won't work with out an LDAP auxprop plugin, since it
> > needs the plaintext password (or DIGEST secret). (i.e. it won't work with
> > saslauthd).
>
> This is making since - Thanks. I'm assuming that the auxprop plugin method
>
On Sun, 24 Mar 2002, OCNS Consulting wrote:
> Okay. Then what plugin is expected to perform LDAP authentication?
No plugins supplied by the Cyrus SASL Distribution currently perform LDAP
authentication.
There is one third-party auxprop plugin that we're looking at including in
the distribution
Okay. Then what plugin is expected to perform LDAP authentication?
RB
> Every plugin that supports a client-side SASL negotiation should export
> this (which is basically all of the included ones, except for libsasldb).
> -Rob
Also, have any idea what is causing the following error?
unable to get entry point sasl_client_plug_init in
/usr/lib/sasl/libsasldb.so:
/usr/local/lib/libsasl.so.7: undefined symbol: sasl_client_plug_init
RB
> Every plugin that supports a client-side SASL negotiation should ex
On Sun, 24 Mar 2002, OCNS Consulting wrote:
> Interesting. Have any ideas of what SASL V2 library the module
> "sasl_client_plug_init"
> resides? I look via "nm" and "ar" and found nothing.
Every plugin that supports a client-side SASL negotiation should export
this (which is basically all o
Ken:
>>Just to insure that Cyrus IMAP
>> was not
>> experiencing the same bdb issue as SASL V2, I recompiled IMAP 2.1.3 -
here
>> are the
>> "configure script" options selected ->
>>
>> ./configure \
>> --enable-fulldirhash \
>> --with-sasl=/usr/lib/sasl2 \
>> --wi
OCNS Consulting wrote:
>
> Ken:
>
> I finally determined the issue with BerkeleyDB. The SASL configure script
> looks for "/usr/include/db3" which is found and contains (as expected) bdb3
> headers. Of course I compile SASL against bdb4 which is specified by
> including
> the options ->
>
>
Ken:
I finally determined the issue with BerkeleyDB. The SASL configure script
looks for "/usr/include/db3" which is found and contains (as expected) bdb3
headers. Of course I compile SASL against bdb4 which is specified by
including
the options ->
--with-bdb-libdir=/usr/local/BerkeleyDB
