Hi all,
The problem was an expired self-generated CA certificate. Now everything
works fine.
Br,
Harri
On 12.04.2019 20:20, Harri T. wrote:
Hi!
I'm trying to get LDAP STARTTLS working. What does "SSL_connect:error in SSLv3/TLS
write client hello → write:errno=0" mean?
Ha
Hi!
I'm trying to get LDAP STARTTLS working. What does "SSL_connect:error in
SSLv3/TLS write client hello → write:errno=0" mean?
Harri
root@ldap2:~# echo | openssl s_client -connect ldap2.mydomain.com:389
-showcerts -state -CAfile /etc/ssl/certs/ldap2_cacert.pem
CON
el
+1 214.770.1896 / Mobile
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dave Thompson
Sent: Friday, July 19, 2013 4:32 PM
To: openssl-users@openssl.org
Subject: RE: SSL_connect:error in SSLv3 flush data - Certif
> From: owner-openssl-us...@openssl.org On Behalf Of Michel, Audrey
> Sent: Friday, 19 July, 2013 11:41
> Thanks for the reply and good information as it helped clear
> up some misunderstanding I had. Here is some additional
> information based on your responses.
>
> -The two servers have diffe
s anything specific in my
searches on that subject.
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dave Thompson
Sent: Thursday, July 18, 2013 6:52 PM
To: openssl-users@openssl.org
Subject: RE: SSL_connect:error in SSLv3
> From: owner-openssl-us...@openssl.org On Behalf Of Michel, Audrey
> Sent: Thursday, 18 July, 2013 15:24
> Subject: SSL_connect:error in SSLv3 flush data - Certificate
> Verification: Error (20) when setting up replacement server
Aside: the error isn't really in flush-data;
write to 0x1f03cc0 [0x1f18570] (267 bytes => 267 (0x10B))
..
SSL_connect:SSLv3 write certificate verify A
write to 0x1f03cc0 [0x1f18570] (6 bytes => 6 (0x6))
SSL_connect:SSLv3 write change cipher spec A
write to 0x1f03cc0 [0x1f18570] (53 bytes => -1 (0xFFFF))
SSL_connect:error in SSLv3 flush data
SSL_conne
On Sun, Aug 19, 2001 at 02:26:24PM -0500, Amos Gouaux wrote:
> As it happens, I too am trying to get SSL/TLS going with latest
> cyrus-imapd. Though, in my case I'm trying to use a Verisign cert.
> At this point I'm just trying to figure out what I need to do next.
>
> I have the server key file
On Sun, Aug 19, 2001 at 10:27:52AM -0700, chirs charter wrote:
> Thanks for your replay Lutz. I do have a /dev/unrandom
> though which is a link to /dev/random and I see a
> prescence of a /.rnd file doesnt this mean that
> openssl is starting up correctly ? Also can you tell
The link does help f
As it happens, I too am trying to get SSL/TLS going with latest
cyrus-imapd. Though, in my case I'm trying to use a Verisign cert.
At this point I'm just trying to figure out what I need to do next.
I have the server key file in pem format defined, the cert I got
back from Verisign, and the vsig
(0x5))
> > 2a 20 42 41 44
> > write to 000D6A20 [000E3DD0] (7 bytes => 7 (0x7))
> > 15 20 42 00 02 02 46
> > SSL3 alert write:fatal:unknown
>
> I don't know what is going on here. Yesterday
> afternoon I wrote the
> manual page for SSL_alert_
2 00 02 02 46
> SSL3 alert write:fatal:unknown
I don't know what is going on here. Yesterday afternoon I wrote the
manual page for SSL_alert_type_string() et al and just discovered,
that the alert descriptions for TLSv1 are not included in the library,
only for SSLv3... Therefore we only s
12 00 09 00 14
0050 00 11 00 08 00 06 00 03|01
005a -
SSL_connect:SSLv3 write client hello A
read from 000D6A20 [000EC060] (5 bytes => 5 (0x5))
2a 20 42 41 44
write to 000D6A20 [000E3DD0] (7 bytes => 7 (0x7))
15 20 42 00 02 02 46
SSL3 alert write:fatal:unknown
SSL_connect:error
13 matches
Mail list logo
