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 …
-
-
Replying to @sgrif
Windows 7 was released 10 years ago and Microsoft’s support for it ended 3 years ago, so it seems weird to expect Github to support its use...
1 reply 0 retweets 1 like -
Replying to @hdevalence
Windows 7 is not EOL until 2020. Depending on where you get your stats, it accounts for somewhere between 45% and 25% of desktop marketshare today. It's the most widely used desktop OS. This also affects Windows 8 and 8.1 AFAIK
1 reply 0 retweets 5 likes -
Replying to @sgrif
The fact that 40% of desktops are running an unsupported OS doesn’t mean it’s Github’s problem that those desktops are unable to make TLS connections, though...
2 replies 0 retweets 2 likes -
Replying to @hdevalence @sgrif
I kind fo chalk it up to the human factor. Not everyone thinks they need an upgrade ("My computer works why upgrade?!" or enterprise reasons), but it ends up causing problems anyways cause at some point, even with forewarning (1 year in GitHub's case), people still don't upgrade.
1 reply 0 retweets 0 likes -
Replying to @mgattozzi @hdevalence
This also broke all sorts of things that have nothing to do with Windows version. Mono (e.g. Unity) is the most prominent that comes to mind
2 replies 0 retweets 1 like -
Also all versions of .NET except the most recent, and all but the 2 most recent versions of Java.
1 reply 0 retweets 1 like -
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.
1 reply 0 retweets 1 like -
Replying to @sgrif @mgattozzi
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?
1 reply 0 retweets 0 likes
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.
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.