On Tue, Feb 20, 2007 at 02:29:15PM +0100, Mgr. Peter Tuharsky wrote: > We have successfully workarounded the issue.
> We have set the passdb backend to > ldapsam:"ldap://localhost:389"; What is the cn in the SSL certificate being used by the LDAP server? It seems odd that this would work at all with start tls, unless your SSL certificate was set up oddly. > Now it works. Excepting that there are annoying errors in log: > [2007/02/20 14:30:23, 0] lib/util_sock.c:get_peer_addr(1229) > getpeername failed. Error was Transport endpoint is not connected Hrm, odd. Are there any previous errors, possibly at a higher debug level? If this is on the LDAP socket, it suggests some pretty big brokenness. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
