<div>Yes, it worked. It came back saying that the certificate has expired, verify return code: 10. Probably the certificate has expired and I need to generate the new certificates..</div>
<div> </div>
<div>Thanks a lot....</div>
<div>NCheeku<br><br> </div>
<div><span class="gmail_quote">On 12/29/06, <b class="gmail_sendername">Steffen Witt</b> <<a href="mailto:witt.steffen@googlemail.com">witt.steffen@googlemail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">OK, the certificate authority (CA) is missing in your client command:<br><br>openssl s_client ... -CAfile name_of_cafile.pem
<br><br>In my opinion a client should use a different certificate/private key<br>pair but signed by the same CA.<br><br><br>Best regards,<br>Steffen<br><br><br>2006/12/29, Ncheeku Baranov <<a href="mailto:opensersubscribe@gmail.com">
opensersubscribe@gmail.com</a>>:<br>> You are correct, so just for the trial purposes if I want the TLS handshake<br>> to be successful what credentials for the client should I use? i.e. can I do<br>> something like:
<br>><br>> openssl s_client -cert user-cert.pem -key user-privkey.pem -state -connect<br>> <a href="http://10.30.00.41:5061">10.30.00.41:5061</a><br>><br>> on doing this it comes back with an error saying Verify Return Code: 21
<br>> (Unable to verify the first certificate), Should I be using new certificates<br>> or with the same set of certificates I can achive a successful handshake?<br>><br>> Thanks a lot..<br>> Ncheeku<br></blockquote>
</div><br>