我修复了一个 TLS 1.2 问题，但我不知道 how/why 它有效，或者它在做什么？这个 Powershell 命令在做什么？
I fixed a TLS 1.2 issue, but I have no idea how/why it works, or what it's doing? What is this Powershell command doing?
在各种 Windows 2012 R2 服务器上，我遇到了 TLS 问题。
如果我运行:
Install-Module -Name ReportingServicesTools
我收到这个错误（下面的屏幕截图）
WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''.
WARNING: Unable to download the list of available providers. Check your internet connection.
如果我只在它上面放一个命令 运行 它，它就可以完美运行。它在做什么，我在哪里可以在 OS 中为所有内容手动配置它？ GUI/registry/etc?
的某处
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 #What is this doing?
Install-Module -Name ReportingServicesTools
简而言之，这不是 PowerShell 特有的问题。 legacy TLS is no longer supported / by web properties/endpoints 正如刚才宣布的那样。必须使用 TLS12。
Solving the TLS 1.0 Problem, 2nd Edition
End of support for TLS 1.0 and 1.1 in Microsoft Cloud App
Security
GoDaddy Browsers end support for TLS 1.0 and 1.1 in March 2020
Cisco End of Life for TLS 1.0/1.1
As of March 31, 2020, Transport Layer Security (TLS) 1.0 and 1.1 will
no longer be supported. All endpoints will be required to support TLS
1.2 after this date in order to function properly with Cisco Umbrella.
Update: Cisco Umbrella will continue to support Cisco AnyConnect and
Cisco Umbrella Roaming Client versions that require TLS 1./0/1.1 until
September 30th 2020. All other uses of TLS 1.0 and 1.1 will be
discontinued as planned on March 31st.
TLS 1.0 and TLS 1.1 Are No Longer Secure
As of Chrome version 79, released last week, Chrome will start support
and start enabling DNS Over HTTPS (DoH), and sites using TLS 1.0 and
TLS 1.1 certificates for encryption will be marked as insecure. The
marking of sites on TLS 1.0, is significant because 68% of websites
still support TLS 1.0 which is insecure due to multiple
vulnerabilities. If your web site uses a TLS 1.0 or 1.1 website, as of
January 13, 2020 it will display the following warning, and in 2021
Chrome will not load websites with TLS 1.0 or 1.1.
因此，将这一行放在您所有的 PowerShell、VSCode 配置文件和每个脚本的顶部，您将永远尝试访问任何 Web 端点。
在各种 Windows 2012 R2 服务器上，我遇到了 TLS 问题。
如果我运行:
Install-Module -Name ReportingServicesTools
我收到这个错误（下面的屏幕截图）
WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''.
WARNING: Unable to download the list of available providers. Check your internet connection.
如果我只在它上面放一个命令 运行 它，它就可以完美运行。它在做什么，我在哪里可以在 OS 中为所有内容手动配置它？ GUI/registry/etc?
的某处[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 #What is this doing?
Install-Module -Name ReportingServicesTools
简而言之，这不是 PowerShell 特有的问题。 legacy TLS is no longer supported / by web properties/endpoints 正如刚才宣布的那样。必须使用 TLS12。
Solving the TLS 1.0 Problem, 2nd Edition
End of support for TLS 1.0 and 1.1 in Microsoft Cloud App Security
GoDaddy Browsers end support for TLS 1.0 and 1.1 in March 2020
Cisco End of Life for TLS 1.0/1.1
As of March 31, 2020, Transport Layer Security (TLS) 1.0 and 1.1 will no longer be supported. All endpoints will be required to support TLS 1.2 after this date in order to function properly with Cisco Umbrella.
Update: Cisco Umbrella will continue to support Cisco AnyConnect and Cisco Umbrella Roaming Client versions that require TLS 1./0/1.1 until September 30th 2020. All other uses of TLS 1.0 and 1.1 will be discontinued as planned on March 31st.
TLS 1.0 and TLS 1.1 Are No Longer Secure
As of Chrome version 79, released last week, Chrome will start support and start enabling DNS Over HTTPS (DoH), and sites using TLS 1.0 and TLS 1.1 certificates for encryption will be marked as insecure. The marking of sites on TLS 1.0, is significant because 68% of websites still support TLS 1.0 which is insecure due to multiple vulnerabilities. If your web site uses a TLS 1.0 or 1.1 website, as of January 13, 2020 it will display the following warning, and in 2021 Chrome will not load websites with TLS 1.0 or 1.1.
因此，将这一行放在您所有的 PowerShell、VSCode 配置文件和每个脚本的顶部，您将永远尝试访问任何 Web 端点。