Fun fact: libgit2, a library made by Github, uses TLS 1.1 on Windows versions earlier than 10. Which means that attempting to access Github via libgit2 on Windows 7 is now broken. https://github.com/rust-lang/cargo/issues/5066 …
-
Also all versions of .NET except the most recent, and all but the 2 most recent versions of Java.
Either way, my original point was not that they shouldn't have ended TLS 1.1 support. My point was that it's silly for Github to do that when a library *made by them* doesn't specify that it wants TLS 1.2 by default.
-
-
my point is that TLS support is the responsibility of the platform, not of the application developer. Most of Github’s users are able to use TLS 1.2. Why should those users’ security be downgraded to accommodate systems that won’t speak a 10-year-old protocol?
-
I am not saying that people's security should be downgraded. I'm saying the library should specify that it wants a recent TLS version by default.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.