search

Disassembler0 / Win10-Initial-Setup-Script

PowerShell script for automation of routine tasks done after fresh installations of Windows 10 / Server 2016 / Server 2019
MIT License
4.69k stars 1.08k forks source link

EnableDotNetStrongCrypto is only relevant for legacy applications #291

Closed Zero3 closed 4 years ago

Zero3 commented 4 years ago

The comment for the EnableDotNetStrongCrypto tweak says:

Enable strong cryptography for .NET Framework (version 4 and above) https://stackoverflow.com/questions/36265534/invoke-webrequest-ssl-fails

This is not entirely accurate though, as its effect has been enabled by default since .NET Framework 4.6, which is shipped with Windows 10:

If your app targets .NET Framework 4.6 or later versions, this key defaults to a value of 1. That's a secure default that we recommend. If your app runs on .NET Framework 4.6, but targets an earlier version, then the key defaults to 0. In that case, you should explicitly set its value to 1.

(Source: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#schusestrongcrypto)

So this feature is only relevant for legacy applications that are compiled for ~5+ year old versions of .NET Framework. It would be nice if the comment reflected this.