Open andreireiand opened 5 years ago
I'd like to bump on this Issue!
This March Browsers will drop TLS 1.0 and TLS1.1 support entirely. The current default behavior will break applications!
References: Mozilla Firefox Google Chrome
Is this out of date? Doesn't the current behaviour set it to SslProtocols.None
which allows the OS to handle TLS?
With current push to disable weak ciphers, the:
close 1015 An exception has occurred while connecting.
error is mostly everywhere. Hence, below procedure: private enum SslProtocolsHack { Tls = 192, Tls11 = 768, Tls12 = 3072 } var sslProtocolHack = (System.Security.Authentication.SslProtocols)(SslProtocolsHack.Tls12 | SslProtocolsHack.Tls11 | SslProtocolsHack.Tls);ws.SslConfiguration.EnabledSslProtocols = sslProtocolHack;
needs be added in default front page documentation, otherwise people might loose a full day just researching for the error code ...
or even better, make this setting the default behavior.