This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all, I have a Tomcat server with SSL enabled. My tomcat version in 1.4.27 and JDK is 1.4.2_03. HTTPS has been working fine with my self generated certificate [I used keytool to generate certificate and import it to keystore file]. I have replaced this self generated certificate with a signed certificate. After this, I get a 'page not found' whenever I access my server through HTTPS.
The noticable difference between the unsigned and signed certifictes is that the former cert version was V1 and signature algorithm was md5RSA. Now with the CA signed certificate the version is V3 and signature algorithm is sha1RSA.
I ran the following command to check the handshake :- openssl s_client -connect <myServer>:8443 -ssl3 -debug
I get this error : 5364:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s 3_pkt.c:1052:SSL alert number 40 5364:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c :529:
I have the same version of tomcat running on another server but when I run the openssl command on this other server, the handshake is successful.
Any help on why I am seeing the handshake failure for ssl3 is much appretiated.
Thanks a ton !
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com