Re: s_client handshake failure [auf Viren überprüft]

2005-03-01 Thread Hans Moser
Hans Moser schrieb das Folgende am 25.02.2005 13:51: [EMAIL PROTECTED] schrieb das Folgende am 24.02.2005 20:16: I think your ldap server is NOT running TLS. Here is my ldapsearch debug output, including "TLS trace: SSL_connect:SSLv3 read server certificate A": [EMAIL PROTECTED]:

Re: s_client handshake failure [auf Viren überprüft]

2005-02-25 Thread Hans Moser
[EMAIL PROTECTED] schrieb das Folgende am 24.02.2005 20:16: I think your ldap server is NOT running TLS. Here is my ldapsearch debug output, including "TLS trace: SSL_connect:SSLv3 read server certificate A": [EMAIL PROTECTED]:/ldap> bin/ldapsearch -Z -x -d -1 -h localhost:666 ldap_create ldap_url_

Re: s_client handshake failure [auf Viren überprüft]

2005-02-24 Thread Hans Moser
[EMAIL PROTECTED] schrieb das Folgende am 23.02.2005 20:34: First of all the HEX line are important because they contained information about the connection (SSL protocol layer: record, alert etc...), in fact in acts as -msg option (openssl 0.9.7e). My fault. But I had to retype it, because there's

Re: s_client handshake failure [auf Viren überprüft]

2005-02-23 Thread Hans Moser
[EMAIL PROTECTED] schrieb das Folgende am 23.02.2005 12:09: Hi, You can specify the protole to use with -ssl3 or -tls1 otherwise s_client send a ssl v2 client hello. Moreover some debug info with -state or -debug could be usefull to find what happened. ;) # openssl s_client -connect localhost:666

s_client handshake failure [auf Viren überprüft]

2005-02-23 Thread Hans Moser
Hi! I created certs for a CA and a server and the server's keys. I configured OpenLDAP to use TLS. Then I connected to the server with # ldapsearch -Z -x -h localhost:666 which works fine. Security is set to "simple bind=64" in slapd.conf, so no simple bind without TLS (# ldapsearch -x -h localhos