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

Re: SASL Mech EXTERNAL disabled?

To: openldap-software@openldap.org
Subject: Re: SASL Mech EXTERNAL disabled?
From: "Dieter Kluenter" <dieter@dkluenter.de>
Date: Tue, 29 Sep 2009 21:52:15 +0200
In-reply-to: <87eipqfe0l.fsf@rubin.avci.de> (Dieter Kluenter's message of "Tue, 29 Sep 2009 08:42:18 +0200")
References: <87fxa6ddkl.fsf@magenta.l4b.de> <alpine.BSO.2.00.0909281831270.31272@vanye.sendmail.com> <87iqf2fjjz.fsf@rubin.avci.de> <4AC19397.8020001@symas.com> <87eipqfe0l.fsf@rubin.avci.de>
User-agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b29 (linux)

"Dieter Kluenter" <dieter@dkluenter.de> writes:

> Howard Chu <hyc@symas.com> writes:
>
>> Dieter Kluenter wrote:
>>> The update was from 2.4.17 to 2.4.18 build with openssl.
> [...]
>>
>> Still works for me. Have your certificates expired?
[...]

> This is rather strange, the error happens on my laptop, I just ran
> ldapwhoami on my x64 server, same configuration, same openldap
> version, with no problems. I think I have to dig into this matter.

Found the culprit. For some unknown reason the openldap package update
modified the init script to run slapd with flag -f
/path/to/slapd.conf instead of -F, and slapd.conf indeed contained the
line 'TLSVerfiyClient never'. Sorry for the noise.

-Dieter
 
-- 
Dieter Klünter | Systemberatung
sip: +49.180.1555.7770535
http://www.dpunkt.de/buecher/2104.html
GPG Key ID:8EF7B6C6

References:
- SASL Mech EXTERNAL disabled?
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: SASL Mech EXTERNAL disabled?
  - From: Philip Guenther <guenther+ldapsoft@sendmail.com>
- Re: SASL Mech EXTERNAL disabled?
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: SASL Mech EXTERNAL disabled?
  - From: Howard Chu <hyc@symas.com>
- Re: SASL Mech EXTERNAL disabled?
  - From: "Dieter Kluenter" <dieter@dkluenter.de>

Prev by Date: Re: Write, then read & mirror-mode
Index(es):
- Chronological
- Thread