1386908 - Disable 3DES in TLS Handshake for early beta builds

Status: RESOLVED WONTFIX

(Core :: Security: PSM, defect, P1)

Description

[J.C. Jones [:jcj] (he/they)]

Bug 1386754 disabled 3DES in the TLS handshake in Nightly. This bug is to (eventually) do so in Beta as well.

Comment 1

[Masatoshi Kimura [:emk]]

See bug 1386754 comment 10. This bug looks a dupe of bug 1386754 for me.

Comment 2

[J.C. Jones [:jcj] (he/they)]

Basically, change from enabling 3DES in BETA_OR_RELEASE to disabling for EARLY_BETA_OR_EARLIER. (Thanks, :emk!)

Comment 3

[Alex Gaynor [:Alex_Gaynor]]

Starting to collect some sites that are known to affect users. Someone in #security today was noting that they can't access client00.chat.mibbit.com.

https://www.ssllabs.com/ssltest/analyze.html?d=client00.chat.mibbit.com indicates that it actually does support some other ciphersuites, though none which overlap with us. It also has tons of insecure settings.

Comment 4

[Asa Dotzler [:asa]]

The Wall Street Journal's subscribe page is affected by this. https://subscribe.wsj.com

Comment 5

[Martin Thomson [:mt:]]

Also https://wlcsplash.airnz.co.nz/ (used in their captive portal in lounges)

Comment 6

[J.C. Jones [:jcj] (he/they)]

We knew the TLS Canary wouldn't reveal the whole story as to what sites' we'd cause breakage for when disabling 3DES, so it's very good to know the list of webcompat issues that have been filed. :keeler, :mwobensmith and I want to thank all the people who helped us evaluate the long-tail of 3DES usage out there.

As 3DES is not known to be insecure, even though it's a legacy cipher, we're turning it back on in Bug 1405511.

Future discussions about deprecation timelines can now work with the August-October 2017 telemetry and webcompat issues as part of the decision-making process (See Bug 1227524).

Resolving WONTFIX.

Comment 7

[u580221]

3DES is also not known to be very secure. I think awarding a 3DES site (or similarly weak ciphers) a regular green padlock without any warning is problematic.

Some other ideas short of disabling 3DES:

1. Was there ever any discussion about a "[x] I don't want sham cipher security" setting that people can turn on that don't care about compatibility with badly configured sites that much?

2. Another alternative would be something Chrome sometimes does, which is letting people connect but use a non-green red striked padlock to indicate the connection to the site is not secure (similar to what firefox does with non-HTTPS password fields). This wouldn't make it impossible to use the site, but it would pressure site owners to fix their server config and make it obvious to the user that there is no proper security established.

Comment 8

[Darkspirit]

(In reply to jonas from comment #7)
> 3DES is also not known to be very secure. I think awarding a 3DES site (or
> similarly weak ciphers) a regular green padlock without any warning is
> problematic.
> 
> Some other ideas short of disabling 3DES:
> [...]
> 
> 2. Another alternative would be something Chrome sometimes does, which is
> letting people connect but use a non-green red striked padlock to indicate
> the connection to the site is not secure (similar to what firefox does with
> non-HTTPS password fields). This wouldn't make it impossible to use the
> site, but it would pressure site owners to fix their server config and make
> it obvious to the user that there is no proper security established.


identity ui: Non-PFS should be called as weak encryption (yellow triangle)
bug 1353710 comment 2