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

Re: SSL/TLS connection on port 389

Subject: Re: SSL/TLS connection on port 389
From: Tony Earnshaw <tonni@hetnet.nl>
Date: Tue, 29 Jan 2008 06:51:30 +0100
Cc: openldap-technical@openldap.org
In-reply-to: <1201532248.3348.116.camel@x068238.lbcamden.net>
References: <1201532248.3348.116.camel@x068238.lbcamden.net>
User-agent: Thunderbird 2.0.0.9 (X11/20071031)

Chris Carr skrev, on 28-01-2008 15:57:

I've been running slapd with "-h ldaps:///" so that it takes SSL/TLS connections on port 636. This has worked with most clients (Outlook, Seamonkey, Thunderbird) but does not work for Evolution. I don't know why not, but Evolution seems to insist on using port 389 for secure connections.

Evo will connect to port 636 ok, *if* you specify 'the_host:636' in your connection box. It works out that this is ssl for itself.

[...]

--Tonni

--
Tony Earnshaw
Email: tonni at hetnet dot nl

Follow-Ups:
- RE: SSL/TLS connection on port 389
  - From: "Carr, Chris" <Chris.Carr@Camden.gov.uk>

References:
- SSL/TLS connection on port 389
  - From: Chris Carr <chris.carr@Camden.gov.uk>

Prev by Date: Re: SSL/TLS connection on port 389
Next by Date: Re: Uniqueness of entryUUID across multiple LDAP servers
Index(es):
- Chronological
- Thread