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

Re: ldapsearch and TLS

To: openldap-software@OpenLDAP.org
Subject: Re: ldapsearch and TLS
From: Luca Filipozzi <lucaf+openldap@ece.ubc.ca>
Date: Wed, 17 Mar 2004 14:16:14 -0800
Content-disposition: inline
In-reply-to: <ymh4qsncqak.fsf@okocim.cs.ubc.ca>
Organization: UBC Electrical & Computer Engineering
References: <Pine.LNX.4.21.0403161044340.12780-100000@mi.krzys.ca> <40581146.8070101@central.susx.ac.uk> <ymh4qsncqak.fsf@okocim.cs.ubc.ca>
User-agent: Mutt/1.5.5.1+cvs20040105i

On Wed, Mar 17, 2004 at 09:54:43AM -0800, Chris Majewski wrote:
> D.M.Lewney@sussex.ac.uk (Dave Lewney) writes:
> 
> > My guess is that the CN in your certificate is not "okocim" . Try this ...
> >
> > openssl s_client -connect okocim:636 -CAfile <path-to-CA-cert>
> 
> It's "okocim.cs.ubc.ca"

I walked over to my fellow UBC sysadmin's building and together we got
his LDAPS stuff squared away.  Moral of the story: when in doubt, buy
your friends donuts and invite them over :)

Yours,

Luca

-- 
Luca Filipozzi, ECE Dept. IT Manager, University of British Columbia
gpgkey 5A827A2D - A149 97BD 188C 7F29 779E  09C1 3573 32C4 5A82 7A2D

References:
- Re: ldapsearch and TLS
  - From: Chris Majewski <majewski@cs.ubc.ca>
- Re: ldapsearch and TLS
  - From: D.M.Lewney@sussex.ac.uk (Dave Lewney)
- Re: ldapsearch and TLS
  - From: Chris Majewski <majewski@cs.ubc.ca>

Prev by Date: Re: ldap_init problem
Next by Date: Problem with ldapsearch and TLS
Index(es):
- Chronological
- Thread