>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.

I checked the server CertReq and from my little in depth knowledge of
OpenSSL and the TLS protocol it looks like it is not request for a specific
certificate.

read from 0xa3efa8 [0xa459fd] (15 bytes => 15 (0xF))
0000 - 0d 00 00 07 04 03 04 01-02 00 00 0e               ............
000f - <SPACES/NULS>
<<< TLS 1.0 Handshake [length 000b], CertificateRequest
    0d 00 00 07 04 03 04 01 02 00 00
<<< TLS 1.0 Handshake [length 0004], ServerHelloDone
    0e 00 00 00

The server certificate is chained but through my testing it looks like it is
verified ok from the logs below

depth=2 /C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification
Authority
verify return:1
depth=1 /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign
International Server CA - Class 3/OU
=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign
verify return:1
depth=0 /C=AU/ST=NSW/L=Sydney/O=Commonwealth Bank of Australia/OU=Enterprise
Services/CN=i2.paywide.
nps.commbank.com.au
verify return:1

>Remember that the client's issuer may be different from 
>the server's issuer (whatever is in verisignVB.pem).

In this case yes the client and server issuers are both different. The
Server certificate was issued under verisign and the client is a self signed
certificate generated using OpenSSL

>Maybe their different client cert is under a different CA,
>which the server does like. 

So in this case is the problem caused by the server not able to verify the
client certificate and hence rejecting the connection? Do I just have to
ensure that the server has the correct client CA?

I have also attached the entire debug message and i changed the command a
little to include the -verify depth.

C:\Documents and Settings\jason.ting.GHL\Desktop\CBA SSL Testing>openssl
s_client -verify 1 -connect i2.paywide.nps.commbank.com.au:9001 -CAfile
verisignV.crt -cert L2009080526.crt -key L2009080526.key -debug -msg
http://old.nabble.com/file/p30328149/SSL%2BFail%2BLog.txt SSL+Fail+Log.txt 


Thanks.


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]



-- 
View this message in context: 
http://old.nabble.com/TLS-unknown_ca-alert-number-48-tp30303596p30328149.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]

Reply via email to