Hi,
On Friday 19 April 2002 3:47 pm, you wrote:
> Tomcat will not work with my imported Verisign certificate. Following is
> the debug output I get when I try to connect. Can anyone interpret this?
>
> Thanks in advance
>
> [read] MD5 and SHA1 hashes: len = 3
> 0000: <line snipped>...
> [read] MD5 and SHA1 hashes: len = 43
> 0000: <line snipped>
> 0010: <line snipped>
> 0020: <line snipped>
> HttpProcessor[8443][4], READ: SSL v2, contentType = 22, translated length
> = 53
> *** ClientHello, v3.0
> RandomCookie: GMT: 0 bytes = { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 225,
> 89, 6, 40, 32, 38, 91, 62, 222, 23, 130, 66, 234, 101, 158, 2 }
> Session ID: {}
> Cipher Suites: { 0, 100, 0, 98, 0, 3, 0, 6, 0, 99 }
> Compression Methods: { 0 }
> ***
> %% Created: [Session-2, SSL_NULL_WITH_NULL_NULL]
> HttpProcessor[8443][4], SEND SSL v3.0 ALERT: fatal, description =
> handshake_failure
> HttpProcessor[8443][4], WRITE: SSL v3.0 Alert, length = 2
This is just a quick off the wall suggestion. Is it because the two hosts
can't agree on a common cipher suite? The session seems to be created with a
load of null algorithms. This is usually because some browsers can only
deal with RSA keys in your certificates, e.g. IE 5.5 and Netscape 4.x. and
JSSE only has DSA keys/certs to play with. Sorry I couldn't be more help.
Regards,
Richard
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
