gang zhong wrote:
> 
> Hi,
> 
> I have a small program silimar to FTP running on Solaris 2.6 and Windows NT.
> IT was working fine
> until I replaced my 40-bit Verisign certificate with 128-bit global secure
> ID. I got the following error
> message:
> [Server]
> SSL_accept failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert
> bad certificate Error No: 0
> [Client]
> SSL_connect failed: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Error No: -1

I hate to say me too, but me too.  I am using SSLv3_server_method and
when my client connects with SSLv2 the certificate read happens just
fine and I get the peer information.  It always fails when using SSLv3
with bad certificate (I tested with both a self signed and a Thawte
certificate).

Eric
 [EMAIL PROTECTED]

S/MIME Cryptographic Signature

Reply via email to