1107103 - https://wcis.ceiwc.com does not work in Firefox 34 and later

Status: RESOLVED INVALID

(NSS :: Libraries, defect)

Description

[therube]

SSL 3.0 Broken in Firefox 34

(At least some) sites that required SSL 3.0 to be enabled no longer work as of FF34.

URL: https://wcis.ceiwc.com/sso/Login.do

That page will not load.
Setting security.tls.version.min;0 no longer works.

It does work in Firefox 33.

So unless there are some other Prefs that need to be tweaked, looks like a regression to me.

> SSL peer rejected a handshake message for unacceptable content.
> (Error code: ssl_error_illegal_parameter_alert)

Another site: https://servizididattica.unical.it/ssweb/gissweb.home
(from https://bugzilla.mozilla.org/show_bug.cgi?id=951156#c33)

SeaMonkey 2.31 is likewise affected.

Comment 1

[therube]

(I moved this to NSS | Libraries, but have no idea what the Version should be.)

Comment 2

[Robert Longson [:longsonr]]

SSL 3 is dead.

https://community.qualys.com/blogs/securitylabs/2014/10/15/ssl-3-is-dead-killed-by-the-poodle-attack

Comment 3

[Boris Zbarsky [:bzbarsky]]

Indeed.  From the Firefox 34 release notes:

 Changed: Disabled SSLv3

Comment 4

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

According to https://www.ssllabs.com/ssltest/analyze.html?d=https%3A%2F%2Fwcis.ceiwc.com%2F, this server does support TLS 1.0. However, it also says that the server is "extension intolerant."

More work should be done to identify exactly what the extension intolerance issue is, to see if it can be worked around--e.g. by changing the order of extensions in the ClientHello, by dropping the padding extension, etc.

Comment 5

[therube]

With the Summary: change, perhaps there is some reference information in the link below that could help?

http://forums.mozillazine.org/viewtopic.php?p=13862063#p13862063

Comment 6

[therube]

> So unless there are some other Prefs that need to be tweaked, looks like a
> regression to me.

Setting:

security.tls.version.min;0
AND
security.tls.version.fallback-limit;0

allows the ceiwc.com & unical.it pages to load.

Comment 7

[rsx11m]

So, what exactly is the difference between security.tls.version.min and .fallback-limit if either of those prevents you to go below the minimum and need to be set to 0 to be able to use SSL 3.0?

This looks a bit redundant to me (and we are exposing .min in SeaMonkey's UI but not .fallback-limit).

Comment 8

[therube]

From, http://www.dslreports.com/forum/r29703508-FF34-and-SSL3

> In the Bug, Brian spoke of "extension intolerance issue ... changing the order of
> extensions in the ClientHello".

> Now I have no idea what that means, but maybe it is for those reasons that I can
> see different results at different times with the same tls Pref settings."

Now maybe this is totally expected behavior, for you, but seeing different behavior, for me, is nothing more then confusing ;-).

IOW...

1. Starting with a new Profile, neither ceiwc page will load, by default in FF34.
2. Once you change the two tls Prefs to '0', both pages will load.
3. But then if you revert those changes back to defaults, then the one page loads but the other will not.

It is 3. that was unexpected for me, as I would have expected 1.

Comment 9

[therube]

Oh, that link didn't work, lets try again, twice (with one purposely broken).

http://www.dslreports.com/forum/r29703508-FF34-and-SSL3
h ttp:/ /www.dslreports.com/forum/r29703508-FF34-and-SSL3

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 11

[John Schanck [:jschanck]]

AFAICT there's no actionable information remaining in this bug.