Re: Handshake Exception with Firefox and Jetty Servlet Container

Hi Nelson, thanks for the Info. We are indeed using a self-signed certificate. I need to get our clients some decisions made, whether we pursue this issue or not. Thanks anyway for your help! -Stefan Nelson Bolyard wrote: > skleinei wrote, On 2008-01-17 09:44: > > [...] Here are t

Re: Handshake Exception with Firefox and Jetty Servlet Container

On Jan 17, 3:57 am, Nelson Bolyard <[EMAIL PROTECTED]> wrote: > Robert Relyea wrote, On 2008-01-16 17:01: > > > > >> Question == > > >> Why is Firefox a ClientHelloV2, although SSL v2 is disabled in Firefox > >> 2? > > > This is a big question. Firefox2 has turned on a number of SSL3/TLS > > ex

Re: Handshake Exception with Firefox and Jetty Servlet Container

It turned out, that difference was the certificate algorithm. - DSA seems to cause the problem, with RSA there is no problem. This result can also be verified with Tomcat, so it is no Jetty-specific error. I wonder, whether this may be related to these bugs: https://bugzilla.mozilla.org/show_bug

Re: Handshake Exception with Firefox and Jetty Servlet Container

I did some more analysis: When I replace the keystore by another keystore provided by the Jetty distribution, Firefox will not complain about the handshake exception. Nevertheless there are handshake exceptions, and the SSL level switches from TLS to SSLv3. Now I guess the question is: What is

Handshake Exception with Firefox and Jetty Servlet Container

We do have a strange problem with Firefox 2 and Jetty 6.1 (a Servlet Container) using HTTPS to communicate: At some stage Firefox (FF) sends a ClientHelloV2, to which Jetty responds with a ServerHelloV3. This leads to a handshake failure for this handshake and for any subsequent attempt. To avoid