>From: [email protected] On Behalf Of Mithun Kumar >Sent: Thursday, 16 May, 2013 14:17
>Adding more info...Looks like the handshake is doesnt stop >as soon as the error is added by Openssl. Any inputs in what >scenarios such errors are thrown.? Possibly the peer made bad_cert a nonfatal alert, which appears to be permitted although I can't easily think of a good reason to do so. You could verify that by a wire trace -- or if you can reproduce this with commandline s_client or s_server as applicable (see next) just add -msg (or -debug). >On Thu, May 16, 2013 at 11:39 PM, Mithun Kumar <[email protected]> wrote: >error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate >:s3_pkt.c:1193:SSL alert number 42 This means the peer sent an alert saying he didn't like the certificate "we" (the program giving the error) offered. Are you a client talking to a server (with client auth), or a server receiving from a client? If you are talking to a server, most servers should have some kind of logging that should describe or at least indicate the problem; if you aren't the person operating the server, you may need to contact the person who does to get this info. If you are receiving from a client, it depends on the client. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
