Slashdot Mirror
Microsoft To Disable TLS 1.0 and TLS 1.1 Support in Edge and Internet Explorer (zdnet.com)
Microsoft today said it plans to disable support for Transport Layer Security (TLS) 1.0 and 1.1 in Edge and Internet Explorer browsers by the first half of 2020. From a report: "January 19th of next year marks the 20th anniversary of TLS 1.0, the inaugural version of the protocol that encrypts and authenticates secure connections across the web," said Kyle Pflug, Senior Program Manager for Microsoft Edge. "Two decades is a long time for a security technology to stand unmodified," he said. "While we aren't aware of significant vulnerabilities with our up-to-date implementations of TLS 1.0 and TLS 1.1 [...] moving to newer versions helps ensure a more secure Web for everyone."
The move comes as the Internet Engineering Task Force (IETF) -- the organization that develops and promotes Internet standards -- is hosting discussions to formally deprecated both TLS 1.0 and 1.1. Microsoft is currently working on adding support for the official version of the recently-approved TLS 1.3 standard. Edge already supports draft versions of TLS 1.3, but not yet the final TLS 1.3 version approved in March, this year. Microsoft engineers don't seem to be losing any sleep over their decision to remove both standards from Edge and IE. The company cites public stats from SSL Labs showing that 94 percent of the Internet's sites have already moved to using TLS 1.2, leaving very few sites on the older standard versions. "Less than one percent of daily connections in Microsoft Edge are using TLS 1.0 or 1.1," Pflug said, also citing internal stats. You can check public stats on the usage of TLS 1.0 and 1.1 here.
The move comes as the Internet Engineering Task Force (IETF) -- the organization that develops and promotes Internet standards -- is hosting discussions to formally deprecated both TLS 1.0 and 1.1. Microsoft is currently working on adding support for the official version of the recently-approved TLS 1.3 standard. Edge already supports draft versions of TLS 1.3, but not yet the final TLS 1.3 version approved in March, this year. Microsoft engineers don't seem to be losing any sleep over their decision to remove both standards from Edge and IE. The company cites public stats from SSL Labs showing that 94 percent of the Internet's sites have already moved to using TLS 1.2, leaving very few sites on the older standard versions. "Less than one percent of daily connections in Microsoft Edge are using TLS 1.0 or 1.1," Pflug said, also citing internal stats. You can check public stats on the usage of TLS 1.0 and 1.1 here.
In 3.2.
then get your dirty fucking hands off of it, Microsoft
some still calling this 'weather'? cease fire stand down.. just don't call it morgellons?
94% of billions is not "very few" sites remaining.
Sorry TRUMP TRAITORS
"You mouse has moved. Windows 10 needs to reboot. [OK]"
I think Windows 10 reboots more frequently than Windows 95.
Edge? Awesome. Yes, please do this.
Internet Explorere!? Oh hell no!!
Seriously, the only reason why IE is still around is due to supporting legacy systems, such as networked attached hardware (printers, routers, switches, access points, security cameras, and more). Not all of these devices are on the public internet, so security concerns in that regard may not be as high. But their web based interfaces generally can not be updated, so are stuck using older protocols. What is the point of even having IE around anymore, if its one and only task (supporting legacy enterprise systems) no longer functions? If that's the case, just remove IE entirely since it'll be made worthless.
Will there be a new Library-Version with TLS1.3 included before Windows 7 hits End-Of-Life?
Just sayin' . . .
Internet Explorer on Windows XP still only supports TLS 1.0, and now even Firefox has left Windows XP the remaining 3% of people still using Windows XP are screwed. I expect even Windows 7 will be under fire when more and more TLS versions get disabled. This is all part of Microsoft’s scheme to get people to use Spydows 10.
But I bet you anything they won't include an option to override unsafe TLS versions warning, and that sucks.
In some cases, there are good reasons to visit unsafe "sites" with expired certificates, that rely on TLS 1.0, or running older Java apps that use deprecated encryption algorithms. For instance, in my company, we have over 8,000 deployed servers with various versions of Dell DRAC (versions 5, 6 and 7) that are still perfectly serviceable, but that have become a massive pain in the butt to access with modern web browsers and newer JREs: some browsers just won't allow you to "visit the page anyway" (i.e. Firefox) and newer Java versions require a bunch of really annoying privacy configurations and a slew of impossible-to-disable warning popups to let older apps runs - despite the damn DRAC apps running quite safely behind our perfectly secure corporate VPN. It's become so annoying we now distribute a dedicated Virtualbox VM with an outdated Linux distro just to be able to access older DRACs quickly.
In short, I wish developers stopped thinking they know what's good for you 100% of the time, and at least offered a configuration option to allow older, unsafe protocols to be used painlessly - even if the configuration option is difficult to set or hard to find, so long as it exists and it can be set once and for all. But they don't, because they they think they know better...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Article updated two hours after publication to include similar announcements made by Apple and Google. While Mozilla did not issue a blog post about the upcoming deprecation, a Mozilla spokesperson confirmed the company will deprecate TLS 1.0 and TLS 1.1 in 2020. The original version of this article only mentioned Microsoft plan to deprecate TLS 1.0 and TLS 1.1.
I browse on +1 so AC's need not respond, I won't see it.
Per a recent article here, their own enterprise MITM software (TMG) maps intercepted traffic to TLS 1.0 or SSLv3:
I guess TMG will recommend Firefox or Chrome.
If there are no practical vulnerabilities and intentionally insecure negotiation bullshit has been exorcised from browsers (It has...right?!?) what is the harm in leaving it as an option so it can be selected as backup in event of unforeseen vulnerabilities in either specifications or implementations?
It's not like support for TLS 1.0 is being removed from schannel.
Arguments made about "age" in this context are inherently unfalsifiable and don't speak to technical merit.
"Two decades is a long time for a security technology to stand unmodified,"
Not only is this statement irrelevant it is provably false with numerous extensions and cipher suites making their way into production environments over the years. AES and by extension AES based cipher suites didn't even exist 20 years ago. It was added to TLS after the fact. Implementation of a relatively recent extension brought us "heartbleed".
Don't allow people to get away with unfalsifiable gibberish. Demand they make the case for change based on technical merit. There may well be a convincing reason to turn off TLS 1.0... state it, make the case for it on the merits.
If we're going to go down this mass deprication route, at least replace it with something that is SECURE, not backdoored.
Thanks.
waterfox is needed for the old java based IPMI and also need to set each IP in the java security bypass as well.
We disabled TLS 1.0 & 1.1 to kill off the people using Exploder and get them to use a decent browser... Please just kill of Internet Explorer already!
Should support it until EOL for majority of sites. Older sites that won't use newer 2.0 most likely in poor countries with many still running older OS and out dated browsers. Not like every country is as modern and up to date as US, UK, etc.
I'm not sure what you mean by this? I have an old java based IPMI and other than getting a security warning about unsigned applications I don't have any problem in IE10 with it. Is there something specific yours complains about?
They are literally defecating on us all.
No, thank you.
I had a lot of fun the time I killed TLS 1.0 in my AD, only to discover that doing so broke network authentication. So, instead of just disabling it in IE and Edge, how about patching everything so SChannel doesn't need a ton of registry changes to use TLS 1.2?