Re: FF 37 - ssl_error_no_cypher_overlap with java SSL and java generated self-signed certificates

2015-04-08 Thread Gervase Markham
On 07/04/15 17:32, Hanno Böck wrote: Are you using DSA? Firefox removed DSA recently (which is good - almost nobody uses it and it's a quite fragile algorithm when it comes to random numbers). Hanno's probably hit the nail on the head here. https://bugzilla.mozilla.org/show_bug.cgi?id=1073867

Re: FF 37 - ssl_error_no_cypher_overlap with java SSL and java generated self-signed certificates

2015-04-08 Thread Brian Smith
Gervase Markham g...@mozilla.org wrote: On 07/04/15 17:32, Hanno Böck wrote: Are you using DSA? Firefox removed DSA recently (which is good - almost nobody uses it and it's a quite fragile algorithm when it comes to random numbers). Hanno's probably hit the nail on the head here.

Re: FF 37 - ssl_error_no_cypher_overlap with java SSL and java generated self-signed certificates

2015-04-07 Thread Gervase Markham
Hi Stefano, On 02/04/15 22:06, stefano.forn...@gmail.com wrote: Hi All, it seems the latest update to FF37 has broken some SSL functionality. Are you sure the problem has begun in 37, and not 36, or 35, or an earlier version? Are you able to see how many connection attempts Firefox makes?

Re: FF 37 - ssl_error_no_cypher_overlap with java SSL and java generated self-signed certificates

2015-04-07 Thread Hanno Böck
On Thu, 2 Apr 2015 14:06:32 -0700 (PDT) stefano.forn...@gmail.com wrote: it seems the latest update to FF37 has broken some SSL functionality. I am not able to access any more a java server running HTTPS. The implementation is based on standard Java SSL and I generated the certificates myself

FF 37 - ssl_error_no_cypher_overlap with java SSL and java generated self-signed certificates

2015-04-02 Thread stefano . fornari
Hi All, it seems the latest update to FF37 has broken some SSL functionality. I am not able to access any more a java server running HTTPS. The implementation is based on standard Java SSL and I generated the certificates myself (being an internal server). It seems the problem is not in the