3 ms·

And for the client-side: 90.29% support according to [0] [0] https://caniuse.com/tls1-3 https://caniuse.com/tls1-3

by moviuro 6y ago

oaiey 6y ago
When you are in a browser. API calls are not evergreen as Browsers are.
- croutonwagon 6y ago
  Same with compiled applications. Windows is the clear laggard here but still https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- https://docs.microsoft.com/en-us/windows/win32/secauthn/prot... .Net says to use the OS schannel protocols. Even the latest Windows doesnt do TLS 1.3 yet. MSSQL has no support for it either. Even on the end user side. One i like to point out is disable TLS 1.0 and try and launch discord. Their update cdn only supports TLS 1.0. So the application doesnt function unless the OS client also will use TLS 1.0 I opened a ticket with them about it and was marked solved and responded with. >Sadly, this is currently working as intended. However, if you would like to see changes to these systems in the future, then you can definitely vote up the suggestions at feedback.discordapp.com. We are a long way from removing TLS 1.0.
  - pitterpatter 6y ago
    Some details missing on that page: Windows supports TLS 1.3 as of version 1903 [1], just disabled by default. I believe it's enabled by default in insider builds as of this summer. [1] https://devblogs.microsoft.com/premier-developer/microsoft-tls-1-3-support-reference/ https://devblogs.microsoft.com/premier-developer/microsoft-t...
    - croutonwagon 6y ago
      Thats where "supported as in can the OS attempt to use it" and "supported as in stable and ready for prod" are diverged. Also the link in that document is unsurprisingly 404'd. If only IIS had a method of doing redirects and rewrites :? https://web.archive.org/web/20200327011332/https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903 https://web.archive.org/web/20200327011332/https://docs.micr...

And for the client-side: 90.29% support according to [0] [0] https://caniuse.com/tls1-3 https://caniuse.com/tls1-3

oaiey 6y ago

When you are in a browser. API calls are not evergreen as Browsers are.

croutonwagon 6y ago
Same with compiled applications. Windows is the clear laggard here but still https://docs.microsoft.com/en-us/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp- https://docs.microsoft.com/en-us/windows/win32/secauthn/prot... .Net says to use the OS schannel protocols. Even the latest Windows doesnt do TLS 1.3 yet. MSSQL has no support for it either. Even on the end user side. One i like to point out is disable TLS 1.0 and try and launch discord. Their update cdn only supports TLS 1.0. So the application doesnt function unless the OS client also will use TLS 1.0 I opened a ticket with them about it and was marked solved and responded with. >Sadly, this is currently working as intended. However, if you would like to see changes to these systems in the future, then you can definitely vote up the suggestions at feedback.discordapp.com. We are a long way from removing TLS 1.0.
- pitterpatter 6y ago
  Some details missing on that page: Windows supports TLS 1.3 as of version 1903 [1], just disabled by default. I believe it's enabled by default in insider builds as of this summer. [1] https://devblogs.microsoft.com/premier-developer/microsoft-tls-1-3-support-reference/ https://devblogs.microsoft.com/premier-developer/microsoft-t...
  - croutonwagon 6y ago
    Thats where "supported as in can the OS attempt to use it" and "supported as in stable and ready for prod" are diverged. Also the link in that document is unsurprisingly 404'd. If only IIS had a method of doing redirects and rewrites :? https://web.archive.org/web/20200327011332/https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903 https://web.archive.org/web/20200327011332/https://docs.micr...