From eb2b3c3f79cc750790d0f0946c629dd4b207fef4 Mon Sep 17 00:00:00 2001 From: Karel Zikmund Date: Fri, 20 Mar 2020 13:31:03 -0700 Subject: [PATCH] Update tls.md Remove misleading sentence --- docs/framework/network-programming/tls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/network-programming/tls.md b/docs/framework/network-programming/tls.md index a120967a06409..e7ffac1838e2f 100644 --- a/docs/framework/network-programming/tls.md +++ b/docs/framework/network-programming/tls.md @@ -115,7 +115,7 @@ The WCF framework automatically chooses the highest protocol available up to TLS ### For .NET Framework 3.5 - 4.5.2 and not WCF -We recommend you upgrade your app to .NET Framework 4.7 or later versions. If you cannot upgrade, take the following steps. At some point in the future, your application may fail until you upgrade to .NET Framework 4.7 or later versions. +We recommend you upgrade your app to .NET Framework 4.7 or later versions. If you cannot upgrade, take the following steps. Set the [SchUseStrongCrypto](#schusestrongcrypto) and [SystemDefaultTlsVersions](#systemdefaulttlsversions) registry keys to 1. See [Configuring security via the Windows Registry](#configuring-security-via-the-windows-registry). The .NET Framework version 3.5 supports the `SchUseStrongCrypto` flag only when an explicit TLS value is passed.