Bug#462588: [Pkg-openldap-devel] Bug#462588: Bug#462588: Same problem

2008-02-03 Thread Steve Langasek
A patch has been committed to the package svn tree to fix handling of cipher lists, which leaves this issue: On Tue, Jan 29, 2008 at 11:09:32AM -0800, Steve Langasek wrote: > I'm not sure if we should also try to migrate the OpenSSL-specific cipher > specs to GNUTLS equivalents as part of the pack

Bug#462588: [Pkg-openldap-devel] Bug#462588: Bug#462588: Same problem

2008-01-29 Thread T.A. van Roermund
Steve Langasek wrote: Well, I can reproduce the problem when using this value for TLSCipherSuite. But why would you set this value, rather than leaving TLSCipherSuite blank to use the default? I don't see the point of listing *all* the cipher types if you don't intend to exclude some of them.

Bug#462588: [Pkg-openldap-devel] Bug#462588: Bug#462588: Same problem

2008-01-29 Thread Steve Langasek
On Sat, Jan 26, 2008 at 12:33:28PM +0100, T.A. van Roermund wrote: > # all cipher suites as currently supported by gnutls, > # constructed using command: > # gnutls-cli -l | grep -E "^TLS" | cut -d\ -f1 | xargs echo > TLSCipherSuite TLS_ANON_DH_ARCFOUR_MD5 TLS_ANON_DH_3DE

Bug#462588: [Pkg-openldap-devel] Bug#462588: Bug#462588: Same problem

2008-01-27 Thread T.A. van Roermund
Quanah Gibson-Mount wrote: Have you verified that port 636 is open? I.e., telnet localhost 636 The port is open: $ telnet localhost 636 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. And: $ netstat --listening --numeric --program | gre

Bug#462588: [Pkg-openldap-devel] Bug#462588: Bug#462588: Same problem

2008-01-26 Thread Quanah Gibson-Mount
--On Saturday, January 26, 2008 12:33 PM +0100 "T.A. van Roermund" <[EMAIL PROTECTED]> wrote: Quanah Gibson-Mount wrote: Have you verified whether or not you can connect using LDAPS via the command line tools? (ldapsearch, ldapwhoami, etc). Yes I did: $ ldapsearch -H ldaps://localho