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

Re: TLSVerifyClient => no login possible

To: Sebastian Reinhardt <snr@lmv-hartmannsdorf.de>
Subject: Re: TLSVerifyClient => no login possible
From: Michael StrÃder <michael@stroeder.com>
Date: Fri, 06 Mar 2009 02:15:56 +0100
Cc: openldap-technical@openldap.org
In-reply-to: <49B07504.3080506@lmv-hartmannsdorf.de>
References: <49A4693D.2040205@lmv-hartmannsdorf.de> <87hc2i5028.fsf@rubin.l4b.de> <49A56823.3080803@lmv-hartmannsdorf.de> <871vtmh15q.fsf@rubin.l4b.de> <49A70157.6050101@lmv-hartmannsdorf.de> <87eixkugwd.fsf@rubin.l4b.de> <49AC5803.4070501@lmv-hartmannsdorf.de> <87ab83ezkz.fsf@rubin.l4b.de> <8763iqg6wl.fsf@rubin.l4b.de> <49B06DAE.8020405@lmv-hartmannsdorf.de> <49B07504.3080506@lmv-hartmannsdorf.de>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15

Sebastian Reinhardt wrote:
> So only the one point is left: the LDAP- Workshop (Stefan Kania's
> one) uses the "TLSCipherSuite HIGH:MEDIUM:+SSLv2" option.

BTW: SSLv2 should not be used anymore. It has security flaws.

Ciao, Michael.

References:
- Re: TLSVerifyClient => no login possible
  - From: Sebastian Reinhardt <snr@lmv-hartmannsdorf.de>
- Re: TLSVerifyClient => no login possible
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: TLSVerifyClient => no login possible
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: TLSVerifyClient => no login possible
  - From: Sebastian Reinhardt <snr@lmv-hartmannsdorf.de>
- Re: TLSVerifyClient => no login possible
  - From: Sebastian Reinhardt <snr@lmv-hartmannsdorf.de>

Prev by Date: Re: TLSVerifyClient => no login possible
Next by Date: Re: Syncrepl cn=config from another context ...
Index(es):
- Chronological
- Thread