[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP, SASL and TLS

To: Kristof Takacs <kristof.takacs@gmail.com>
Subject: Re: OpenLDAP, SASL and TLS
From: Dan White <dwhite@olp.net>
Date: Mon, 6 Oct 2014 13:27:13 -0500
Cc: openldap-technical@openldap.org
Content-disposition: inline
In-reply-to: <20141006182447.GC3716@dan.olp.net>
References: <CAJVcxRZcXYCjOa3r1YOUgGLdUwT4gS2-P8_emSCVgFJq3D2xvA@mail.gmail.com> <CAJVcxRZuyY=J4CLHuJkWKZaFtTApE9bX75BDLG2sstpL5OtBeQ@mail.gmail.com> <20141006182447.GC3716@dan.olp.net>
User-agent: Mutt/1.5.23 (2014-03-12)

On 10/06/14 13:24 -0500, Dan White wrote:

There is a known bug in Cyrus SASL which triggers this problem:

https://bugzilla.cyrusimap.org/show_bug.cgi?id=3480

If adding "-O maxssf=0" to your ldapsearch command, when using both
Kerberos and TLS, works then that's likely the culprit.


Apparently I can't read my own bug reports. This may or may not be your
issue.

--
Dan White

Follow-Ups:
- Re: OpenLDAP, SASL and TLS
  - From: Kristof Takacs <kristof.takacs@gmail.com>

References:
- Re: OpenLDAP, SASL and TLS
  - From: Kristof Takacs <kristof.takacs@gmail.com>
- OpenLDAP, SASL and TLS
  - From: Kristof Takacs <kristof.takacs@gmail.com>
- Re: OpenLDAP, SASL and TLS
  - From: Dan White <dwhite@olp.net>

Prev by Date: Re: OpenLDAP, SASL and TLS
Next by Date: LMDB Crash-consistency
Index(es):
- Chronological
- Thread