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

Re: How to only accept TLS connection on port 389

To: openldap-software@openldap.org
Subject: Re: How to only accept TLS connection on port 389
From: Alex Samad <alex@samad.com.au>
Date: Mon, 22 Jan 2007 22:35:20 +1100
Content-disposition: inline
In-reply-to: <cb44e8370701212114i17b7857fy6ba87398cab25adb@mail.gmail.com>
Mail-followup-to: openldap-software@openldap.org
References: <cb44e8370701211732x20d9882ax23adde2396bf13b4@mail.gmail.com> <200701220501.l0M51RGZ001926@boole.openldap.org> <cb44e8370701212114i17b7857fy6ba87398cab25adb@mail.gmail.com>
User-agent: Mutt/1.5.13 (2006-08-11)

On Mon, Jan 22, 2007 at 04:14:51PM +1100, Jean-Yves Avenard wrote:
> Hi
> 
> On 1/22/07, Kurt D. Zeilenga <Kurt@openldap.org> wrote:
> >You can require TLS (SSL)  via the slapd.conf(5) security directive.
> 
> I haven't found in the manual any directives that make TLS/SSL compulsory :(
can't you use TLSVerifyClient demand ?
> 
> JY
>

Attachment: signature.asc
Description: Digital signature

References:
- How to only accept TLS connection on port 389
  - From: "Jean-Yves Avenard" <jyavenard@gmail.com>
- Re: How to only accept TLS connection on port 389
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: How to only accept TLS connection on port 389
  - From: "Jean-Yves Avenard" <jyavenard@gmail.com>

Prev by Date: Re: slurpd access control problems
Next by Date: Two-level groups
Index(es):
- Chronological
- Thread