SCIENTIFIC-LINUX-USERS Archives

January 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Olf Epler <[log in to unmask]>
Reply To:
Olf Epler <[log in to unmask]>
Date:
Thu, 22 Jan 2009 19:24:53 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (29 lines)
 Dear colleagues,

since a couple of days I try to switch on the ssl connection
for a ldap client on SL-5.2 x86_64.
I cleaned this installation so that only x86_64 packets are
installed and runs also yum upgrade.
My server works without any problems with SL-4.2 i386/x86_64,
SL-5.1 i386 and also on port 389 with SL-5.2 x86_64.
openssl097a and openssl-0.9.8b are installed.
As soon I change to "ldaps://<server>" in ldap.conf nothing
happens.
"ssl on" in ldap.conf allows "getent passwd" or ldapsearch
but disables console logins. A further login is only possible
as root with ssh.
"ssl tls_start" also doesn't work.
I've recompiled nss_ldap and also pam_ldap - no result.
Because pam works well if I use port 389 I believe something
other must be wrong. Can anybody help?

 Cheers, Olf Epler

----------------------------------------------------------
Olf Epler                          phone: +49 30 2093-7804
Humboldt University Berlin           fax: +49 30 2093-7642
Department of Physics
Newtonstr. 15
12489 Berlin              email: [log in to unmask]
----------------------------------------------------------

ATOM RSS1 RSS2