> From: [email protected] On Behalf Of jason.ting > Sent: Thursday, 25 November, 2010 04:16
> ... I am a client and the SSL server is being managed > by a 3rd party. When i try ... > openssl s_client -connect i5.paywide.nps.comm.com:9001 -CAfile > verisignVB.pem -cert L2009080526.crt -key L2009080526.key -debug -msg > > What i am getting is <snip: send CCS+Finished, recv alert48> > It is the final TLS ChangeCipherSpec message that the my > client sends to the > server and the server rejects the connection. The certificate No it's not, it's the client Cert(+CertVerify), which are sent (with ClientKeyExch) BEFORE the CCS+Finished and turnaround. > verification > both on the Server and Client seems to work. I used OpenSSL > as well as MS > Windows to verify both the client and server certs with the > CA and it seems > to be fine. > The server doesn't think so. Look at the server CertReq to see if it is asking for particular CA(s) and if so whether the cert your client is using is issued by that CA (or one of them). Also check whether it is directly under or chained; if the latter I don't think commandline s_client can do it, although a (custom) app using the library can. Remember that the client's issuer may be different from the server's issuer (whatever is in verisignVB.pem). > I have checked that the Time and Date on my Client device is > correct. I have > no control over the server side but I was told that they are > using it with a > different client cert and it is working. > Maybe their different client cert is under a different CA, which the server does like. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
