On Wed, 5 Mar 2003, Nalin Dahyabhai wrote:
> Also correct. It bears mentioning that 8.0 was released in September,
> and quite a bit has changed since then (particularly, 2.1.12 being
> designated the STABLE release). I'm personally looking forward to
> moving to 2.1.
>
2.1 has been the "stable
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Simon Brady
> On Wed, 5 Mar 2003, Howard Chu wrote:
> > I suggest you ditch OpenLDAP 2.0.27 and update to the
> latest 2.1 release.
> > Then you ditch saslauthd & PAM and have SASL authenticate
> directly
On Wed, 5 Mar 2003, Howard Chu wrote:
> I suggest you ditch OpenLDAP 2.0.27 and update to the latest 2.1 release.
> Then you ditch saslauthd & PAM and have SASL authenticate directly against
> LDAP. Note that OpenLDAP 2.0.X does not work with Cyrus SASL 2.1.x anyway, so
> you need OpenLDAP 2.1 if
> -Original Message-
> From: Jonathan Marsden [mailto:[EMAIL PROTECTED]
> On 5 Mar 2003, Howard Chu writes:
> > Note that OpenLDAP 2.0.X does not work with Cyrus SASL 2.1.x anyway,
> > so you need OpenLDAP 2.1 if you're already using SASL 2.1.
> I believe this general statement to be inco
[Jonathan Marsden]:
>
> That combination certainly seems to work fine here, in a
> multi-server multi-domain international directory and email
> deployment. OpenLDAP 2.0.27 and cyrus-sasl-2.1.7 or -2.1.10 or
> -2.1.12 have all worked (currently on Red Hat 7.3, on x86 SMP
> hardware).
ye
[Jonathan Marsden]:
>
> That combination certainly seems to work fine here, in a
> multi-server multi-domain international directory and email
> deployment. OpenLDAP 2.0.27 and cyrus-sasl-2.1.7 or -2.1.10 or
> -2.1.12 have all worked (currently on Red Hat 7.3, on x86 SMP
> hardware).
ye
On 5 Mar 2003, Howard Chu writes:
> Note that OpenLDAP 2.0.X does not work with Cyrus SASL 2.1.x anyway,
> so you need OpenLDAP 2.1 if you're already using SASL 2.1.
I believe this general statement to be incorrect.
That combination certainly seems to work fine here, in a multi-server
multi-do
I suggest you ditch OpenLDAP 2.0.27 and update to the latest 2.1 release.
Then you ditch saslauthd & PAM and have SASL authenticate directly against
LDAP. Note that OpenLDAP 2.0.X does not work with Cyrus SASL 2.1.x anyway, so
you need OpenLDAP 2.1 if you're already using SASL 2.1.
With those issu
