Forum Discussion
TLS 1.3
TLS 1.3 is a very needed feature for those in corporate environments for our public facing websites. The speed advantages are immense in larger sites with no caching
TheAutisticTechie As with Chrome, TLS/1.3 is supported in all versions of Chromium-based Edge (and will be supported on all platforms).
28 Replies
It is nice that Edge and Windows 10 and 2019 support TLS 1.3.
However some Windows Update Servers (like https://www.ssllabs.com/ssltest/analyze.html?d=fe2.update.microsoft.com&hideResults=on&latest on their IPv6 addresses) only support those Ciphers that are known to be weak. Disabling those ciphers in Windows 10 or 2016/2019 breaks Windows Update functionality. So more security actually turns into less security.
https://www.ssllabs.com/ssltest/analyze.html?d=fe2.update.microsoft.com&s=2a01%3a111%3af330%3a1793%3a0%3a0%3a0%3aa21&hideResults=on
TheAutisticTechie No, TLS 1.3 is not a 'badly needed feature' and the speed benefits are not 'immense,' unless you are TLS servers on old consumer level hardware that lack AES accelerators.
Microsoft is not like garbage developers - I mean open source developers that race to implement something for the personal gratification rather than for the quality of the product. MS, RSA and Cisco have the only TLS 1.0 implementations without active exploits because of it where nearly all other implementations do.
In addition, TLS 1.3 was only ratified a few months ago. All efforts so far are based on code written before the standard was ratified and have extreme likelihood of containing legacy code that will provide a vector for exploit. In addition, these open source projects have also carelessly introduced exploits into TLS 1.3 that do not exist in 1.2, and simply having 1.3 enabled enables downgrade attacks against weaker protocols that can be completely broken.
Wait for a correct implementation. Most (other than the ones where the protocol was fundamentally broken) of the famous SSL and TLS exploits have been created by bad open source solutions that incorrectly implemented SSL/TLS. You will see no difference in performance, other than perhaps at low power client devices.
- Microsoft released TLS 1.2 within about 6 months of its ratification.
It's been longer than that for TLS 1.3 and no word yet on future support.
Tls 1.3 is designed to bring significant speed & security improvements. Reducing the number of round trips required is a massive improvement, especially for global customers who have longer latencies.
IIS is falling behind.1. No MS did not release support for TLS 1.2 within 6 months. TLS 1.2 was ratified in August of 2008. NT 6.1 RTMed at the end of July 2009. That is nearly a year.
2. It doesn't matter. TLS 1.3 is not the same thing as TLS 1.2. TLS 1.3 is a radical update to the protocol, so much so that it was nearly named TLS 2.0. Correctly implementing it will take time. If you are fine with settling for exploit-ridden, incorrect implementations of 1.3 currently available, then you cannot claim to care about anything you claim to care about in the implementation. TLS 1.2 is also not yet exploitable and is better than every incorrect implementation of 1.3 out there.
3. Mathematical differences in speed are not measurable differences in speed. It doesn't matter how much you insist there will be a measurable difference between 1.3 and 1.2, it wont be there. Your part about latency is correct, but in order for latency to come into play in speed - which would manifest only through avoiding some packet loss - you will have to be into latencies of 600-700 milliseconds with high jitter, or 800-900 milliseconds or higher with consistent latency. In other words, EXTREME low end satellite service or extraordinarily busy site to site microwave links.
4. IIS is an HTTP server, not a TLS server. The two have absolutely NOTHING to do with each other. Windows keeping an incorrect implementation of TLS out of the operating system which opens up exploits that never existed before, in place of a TLS 1.2 that currently cannot be exploited is foolhardy at best.
- Sorry I wasn't able to get to this yesterday, TheAutisticTechie. As joel0m and Eric_Lawrence have discovered, all preview channels of Edge already support TLS1.3. Are you seeing sites that are should be using TLS1.3 and are not with the Edge browser? If so, please let me know so that we can investigate.
ElliotElliot Kirk, @joel0m and @ericlaw
Thanks for your replies. I checked some sites last night which didn't work. Reinstalled tonight and it is now working the same as my Chrome. SSL Labs site reports TLS 1.2 in use with experimental 1.3 as expected
Not entirely sure why it didnt work yesterday, though maybe because I also have Windows insider too perhaps?
- Thanks. If you see any weirdness like this again, please send a smiley (top right of the browser) as that will collect some light telemetry and will help us better diagnose any potential problems.
Elliot
- Eric_Lawrence
Microsoft
TheAutisticTechie As with Chrome, TLS/1.3 is supported in all versions of Chromium-based Edge (and will be supported on all platforms).
https://www.ssllabs.com/ssltest/viewMyClient.html
It looks like TLS 1.3 is supported on my configuration using Edge Canary and Dev with Windows 10 1809. Are you seeing otherwise?
- Isn't the issue here that Windows Server IIS doesn't support TLS1.3...
Does Microsoft have an ETA?- Eric_Lawrence
Avaza It's unlikely that the original poster's issue was with IIS (as Chrome would exhibit matching behavior and apparently it started working as expected later).
In terms of Windows Server's roadmap for TLS/1.3 support in IIS, you'll probably get a better informed answer over in https://techcommunity.microsoft.com/t5/Microsoft-IIS/ct-p/Microsoft-IIS
