Migration path to removing TLS 1.0 and 1.1 #4319
Milestone
Comments
|
Why milestone 3.12 based on above comments? |
|
Using “next release” as a mechanism for “short list of things to consider for next release”, with the expectation that it’ll slip one or two. Gotta cut a release soon too. |
|
... I created a new milestone “Backlog” for issues that we’ve triaged. |
swankjesse
pushed a commit
that referenced
this issue
Dec 30, 2018
We no longer connect to TLSv1.0 or TLSv1.1 servers out-of-the-box; instead it is necessary to enable COMPATIBLE_TLS in the OkHttpClient configuration. This is in the path to later removing these TLS versions completely; that is scheduled for March 2020 by some browsers. #4319
swankjesse
pushed a commit
that referenced
this issue
Dec 30, 2018
We no longer connect to TLSv1.0 or TLSv1.1 servers out-of-the-box; instead it is necessary to enable COMPATIBLE_TLS in the OkHttpClient configuration. This is in the path to later removing these TLS versions completely; that is scheduled for March 2020 by some browsers. #4319
|
This step is done. Next step comes in 2020 with #4499! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Browser vendors announced they’re phasing out obsolete versions of TLS in March 2020.
https://blog.mozilla.org/security/2018/10/15/removing-old-versions-of-tls/
In an early-2019 release we should flip
MODERN_TLSto support this 2020 spec, and changeCOMPATIBLE_TLSto cover everything that was dropped.The text was updated successfully, but these errors were encountered: