Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Raise TLS min to v1.1 (or v1.2) #167

Closed
Thorin-Oakenpants opened this issue Jul 9, 2017 · 5 comments
Closed

Raise TLS min to v1.1 (or v1.2) #167

Thorin-Oakenpants opened this issue Jul 9, 2017 · 5 comments

Comments

@Thorin-Oakenpants
Copy link
Contributor

Thorin-Oakenpants commented Jul 9, 2017

snip

@earthlng
Copy link
Contributor

earthlng commented Jul 9, 2017

Yes, I have disabled TLS1.0 ever since I created my user.js and nowadays I very rarely encounter pages that break. I'd say lets disable both 1.0 and 1.1 while we're at it.
One of the sites that didn't used to work was the securityartwork.es link in 1200's description but they seem to have recently updated to TLS1.2 as well.

Btw your linked article hides all the content by default. Fuck that! - let's replace the link with an archived version: https://archive.is/hY2Mm (created today)

@Atavic
Copy link

Atavic commented Jul 9, 2017

EDIT: When a site uses a SSL or TLS version that's inactive in the browser:
Error code: SSL_ERROR_NO_CYPHER_OVERLAP

@2glops
Copy link

2glops commented Jul 9, 2017

TLS 1.2 min seems good.
Only very few sites should break.

@earthlng
Copy link
Contributor

earthlng commented Jul 9, 2017

we also have one in 2668, which I will edit as well to use the same number

👍

1202 nits:

  • I'd make the WARNING a NOTE and add a [WARNING] If you get an "SSL_ERROR_NO_CYPHER_OVERLAP" error temporarily set a lower value for 'security.tls.version.min' in about:config or something like that.
  • simply replace link [2] because fuck them and their shenanigans. The original link can still be seen at the top of the archived page
  • I also don't like version.max=4 because 0-RTT still sucks in TLS1.3 but that's just me

@earthlng
Copy link
Contributor

earthlng commented Jul 9, 2017

while you pushed and pushed for it (and got salty!)

I always said "IF/WHEN the change lands in stable"! I still feel that way btw. So far it's beta-only.
I also don't remember getting salty about it

# for free to join this conversation on GitHub. Already have an account? # to comment
Development

No branches or pull requests

4 participants