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

Re: ldapadd requires confidentiality





--On Wednesday, January 21, 2004 3:47 PM +0100 Tony Earnshaw <tonye@billy.demon.nl> wrote:

This is a Solaris-specific thing. I'm afraid I have no Openldap
experience on Solaris and have no machine to check on.

However:

1: above would seem to indicate that there is already a daemon running;
check that;
2: I don't know what you use to seed your encryption software, Linux has
a /dev/random which is usually used for this.

It looks as though you might have *2* LDAP instances on your Solaris
machine. The strange thing is, that in your slapd.conf you have nothing
about certificates, nor have you explicitly compiled for SSL support,
but your daemon is definitely trying to run with TLS support.

Hope that a Solaris Openldap person sees this and can help you further.
I know that there have been conflicts reported on this list for Solaris
stuff that is already installed as standard, and Openldap installs.

Well, we run Solaris here (that is what our OpenLDAP servers are running on).


Of course, we have highly customized builds that only install a bare minimum of the OS. Generally, I believe Sun installs SunOne Directory server/client software on their systems. I am curious if the ldap* commands being run are the OpenLDAP ones or the Solaris ones. Other things to look at are a netstat -a output to see what's listening to port 389.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/TSS/Computing Systems
ITSS/TSS/Infrastructure Operations
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html