Bug#411042: Info received (Bug#411042: [Pkg-samba-maint] Bug#411042: samba -dosen't connect to OpenLDAP)

2007-03-05 Thread Mgr. Peter Tuharsky
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. This is the beginning of the /etc/ldap/slapd-cert-ldap1.pem Certificate: Data: Version: 3 (0x2)

Bug#411042: Info received (Bug#411042: [Pkg-samba-maint] Bug#411042: samba -dosen't connect to OpenLDAP)

2007-03-05 Thread Steve Langasek
On Mon, Mar 05, 2007 at 01:57:49PM +0100, Mgr. Peter Tuharsky wrote: 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. This is the beginning of the

Bug#411042: Info received (Bug#411042: [Pkg-samba-maint] Bug#411042: samba -dosen't connect to OpenLDAP)

2007-02-20 Thread Mgr. Peter Tuharsky
We have successfully workarounded the issue. We have set the passdb backend to ldapsam:ldap://localhost:389; 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

Bug#411042: Info received (Bug#411042: [Pkg-samba-maint] Bug#411042: samba -dosen't connect to OpenLDAP)

2007-02-20 Thread Steve Langasek
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