>From what I've read about it, this error seems to
indicate that the server certificate could not be
verified by the client opening the connection. Is
this correct?

If so, that would indicate a problem with the
certificates I've generated, but I've followed the
OpenSSL book to do so, and the same certificate
files are used with this code on other OSes with
no difficulty.

What could the problem be?

Thanks in advance for any ideas.


K

----- Original Message -----
From: [EMAIL PROTECTED]
To: openssl-users@openssl.org
Subject: OpenSSL on VxWorks
Date: Wed, 10 Aug 2005 15:19:04 -0500

> 
> Hello,
> 
> This is a follow up to an earlier post I made with regard to some
> problems I'm facing in running some code that uses OpenSSL on
> VxWorks. The same code, with the same certificate files runs on
> Solaris, Linux and Windows. On VxWorks, however, I get:
> 
> 30209:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad 
> certificate:s3_pkt.c:1054:SSL alert number 42
> 
> This happens when I try to initiate a TLS client connection to a
> previously opened TLS server.
> 
> What is this error usually caused by, and where should I begin
> to look for a solution?
> 
> Thanks much for any ideas.
> 
> 
> K
> 
> 
> --
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
> 
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> User Support Mailing List                    openssl-users@openssl.org
> Automated List Manager                           [EMAIL PROTECTED]


-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to