.Net Framework 3.5 and Tls 1.2

.NET Framework 3.5 and TLS 1.2

As you can see from the docs, TLS 1.2 is not in the enumeration for SslProtocols, it was added to the enum in .NET 4.5 (thanks @orhun).

There is no workaround for TLS 1.2 compatibility on .NET 3.5.

Unfortunately you will have to upgrade to .NET 4.5 or later to get TLS 1.2 compatibility.

EDIT 10/11/17

My above answer is no longer accurate. In May of 2017, Microsoft released a package to allow TLS 1.2 in .NET 3.5.1.

Use TLS on .NET Compact Framework 3.5

Thanks for all the comments. We ended doing an "bridge" between our code and the Bouncy Castle libraries, so now we can send TLS request via SOAP protocol to the server.
Maybe the community may remember that some kind of companies do not use to update the tools they use, so, as I have been told that this is outdated, I must say that this system is in use by one of the largest companies in the world. And we keep it up to date.

Thanks anyway.

Related Topics