4 ms·
*Windows 7. Which was released in 2009, 1 year after TLS 1.2 was finalized. Windows 8.1 and 10 support TLS 1.2 without opt in.
by will4274 5y ago
*Windows 7. Which was released in 2009, 1 year after TLS 1.2 was finalized. Windows 8.1 and 10 support TLS 1.2 without opt in.
- tetha 5y agoIn case someone is hardening these settings, we had a weird issue with Windows Server 2016 (iirc) based on this. The mozilla SSL config generator is going to give you a cipher configuration and happily claims Windows 7 and Win2016 both can connect to these servers. However, that's only true if you use a certificate with an elliptic key. With a certificate with an RSA key, Win 7 and Windows Server 2016 cannot connect. That was a mess to figure out.
- JonathonW 5y ago> Windows 8.1 and 10 support TLS 1.2 without opt in. Not necessarily true depending on the application and when it was compiled. For example, older versions of Nuget will not connect to the current Nuget registry (after they removed support for TLS 1.0/1.1 a while back) without a registry change to require TLS 1.2, even on fully-patched Windows 10. Compile against current .NET Framework and IIRC you get it by default, but old code still has to opt-in.
- Already__Taken 5y agoSupported yes but windows won't do it until you turn it on and that change was a very very recent change. It's not even in the UI options were you enable it for TLS but down in the windows registry.