On Thursday 24 August 2006 08:49, Dieter Kluenter wrote:
> Karsten Römke <[EMAIL PROTECTED]> writes:
> > Dieter Kluenter schrieb:
> >> Quanah Gibson-Mount <[EMAIL PROTECTED]> writes:
> >>> --On Wednesday, August 23, 2006 8:18 PM +0200 Karsten Römke
> >>> <[EMAIL PROTECTED]> wrote:
>
[...]
> > Hello,
> > in the moment I do not really know what to do :-)
> > I appended the output from openssl ...
> > Should I start with a nearly empty ldap.conf on client side?
> > I use that one which is generated by yast, the suse
> > administration tool and without encryption this
> > file works.
>
> Please note that there are 2 ldap.conf files as Quanah lined out. The
> file /etc/openldap/ldap.conf is read by any client compiled with
> libldap and might be read by other clients.
> The file /etc/ldap.conf contains configuration for pam_ldap.
> To configure properly /etc/openldap/ldap.conf read man ldap.conf(5)
IIRC Karsten is using a pretty old SuSE Version (8.2?). With SuSE Linux 8.2 we
had both ldap.confs merged into one. That is nss_ldap, pam_ldap and the
openldap libraries were all configured to use /etc/openldap/ldap.conf. So it
might be that there really is only one ldap.conf file.
Luckily we have changed that with newer SuSE releases.
--
regards,
Ralf
SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg
T: +49-911-74053-0
F: +49-911-74053575 - [EMAIL PROTECTED]
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
