


We switched off the old TLS versions on our servers in 2019.

Google led the way with the deprecation of TLS 1.0 and 1.1 in Chrome 72.įirefox disabled TLS 1.0 and 1.1 by default in January 2020. Modern web browsers are enforcing the move to TLS 1.2 by showing warnings about the HTTPSĬonnection not beeing secure if the server still accepts the older cryptographic suites. LabVIEW does not seem to use the operating system defaults for SSL and TLS.Servers should not longer serve HTTPS over the deprecated protocols TLS 1.0 and TLS 1.1. Using the WATS LabVIEW add-on with TLS 1.2

TLS 1.0 and TLS 1.1 are obsolete and insecure protocols and should be disabled on the WATS server.
