78

Since I just discovered that RFC 5425 requires TLS 1.2 to be used, and that .NET doesn't yet support it, I wonder if there are any implementation, possibly open source, of TLS 1.2 protocol, as defined in RFC 5246.

Improve this question
2

10 Answers 10

Reset to default
79

Yes, though you have to turn on TLS 1.2 manually at System.Net.ServicePointManager.SecurityProtocol

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls; // comparable to modern browsers var response = WebRequest.Create("https://www.howsmyssl.com/").GetResponse(); var body = new StreamReader(response.GetResponseStream()).ReadToEnd();

Your client is using TLS 1.2, the most modern version of the encryption protocol

Out the box, WebRequest will use TLS 1.0 or SSL 3.

Your client is using TLS 1.0, which is very old, possibly susceptible to the BEAST attack, and doesn't have the best cipher suites available on it. Additions like AES-GCM, and SHA256 to replace MD5-SHA-1 are unavailable to a TLS 1.0 client as well as many more modern cipher suites.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Is it possible to specify the SecurityProtocol via a setting in the app.exe.config?
Doesn't this also depend on the OS/Server that the application is running on, since that's where the actual HTTP traffic will be created/received?
Thanks. Works like a charm. FYI this works on Windows 2012 server. I was told that Windows 2008 does not support TLS1.2.
You should be able to use TLS1.2 on 2008Svr. May need to install dotNet 4.5 framework. See: msdn.microsoft.com/en-us/library/8z6watww(v=vs.110).aspx
44

Just found that .Net Framework 4.5 now supports TLSv1.2
http://msdn.microsoft.com/en-us/library/system.security.authentication.sslprotocols(v=vs.110).aspx

Improve this answer

1 Comment

Actually when you use the values of the SSLProtocol constants and cast it to the enum things work in .NET 4.0 as well
28

You can make use of the SchUseStrongCrypto registry setting to require all .NET applications to use TLS 1.2 instead of 1.0 by default.

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
Improve this answer

5 Comments

Microsoft should really update this value in one of their security updates. I can not believe the default is to enable SSL v3 and disable TLS 1.2, and the fix is a simple registry setting.
.Net framework 4.0 doesn't supports TLS 1.1+, but framework 4.5 does: fwk 4.0: msdn.microsoft.com/en-us/library/… fwk 4.5: msdn.microsoft.com/en-us/library/…
There's now (Sept 2016) a bunch of different framework versions in the registry (4.0.30319, 4.5, 4.5.1, 4.5.23026, 4.5.50709). Which one needs updating - or all of them?
The answer to this is below - you just need to set the 4.0.30319 one.
It will work on Windows 2008 SP2 with Microsoft Update KB4019276. More info here: github.com/TheLevelUp/pos-tls-patcher
12

I fixed my problem by switching to the latest .Net Framework. So your target Framework sets your Security Protocol.

when you have this in Web.config 

<system.web> <httpRuntime targetFramework="4.5"/> </system.web>

you will get this by default: 

ServicePointManager.SecurityProtocol = Ssl3 | Tls

when you have this in Web.config

<system.web> <httpRuntime targetFramework="4.6.1"/> </system.web>

you will get this by default: 

ServicePointManager.SecurityProtocol = Tls12 | Tls11 | Tls
Improve this answer

1 Comment

and NET 4.7.1 ?
9

Just download this registry key and run it. It will add the necessary key to the .NET framework registry. You can have more info at this link. Search for 'Option 2' in '.NET 4.5 to 4.5.2'.

The reg file appends the following to the Registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

This is the part of the page that is useful in case it goes broken :

" .. enable TLS 1.2 by default without modifying the source code by setting the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don't exist: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319" and "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319". Although the version number in those registry keys is 4.0.30319, the .NET 4.5, 4.5.1, and 4.5.2 frameworks also use these values. Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. It is thus advisable to test this change before deploying it to your production servers. This is also available as a registry import file. These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value. "

Improve this answer

1 Comment

Hi, I have edited your answer to include the contents of the registry file. Reg files are normally considered "security sensitive", and experienced sysadmins people won't bindly open the first reg file linked by someone else (with all the respect!). I think it will also be a great idea to quote part of the linked article, as per SO policy (no link-only answers - better say "no answers that 100% depend on links")
8

If you are dealing with older versions of .NET Framework, then support for TLS 1.2 is available in our SecureBlackbox product in both client and server components. SecureBlackbox contains its own implementation of all algorithms, so it doesn't matter which version of .NET-based framework you use (including .NET CF) - you'll have TLS 1.2 with the latest additions in all cases.

Please note that SecureBlackbox wont magically add TLS 1.2 to framework classes - instead you need to use SecureBlackbox classes and components explicitly.

Improve this answer

7 Comments

Open source project doesn't necessarily mean that you need to open all code.
I am correct in thinking that this will satisfy the SSL requirements of PCI DSS 3.1? This would be very useful as there are a lot XP-Derived operating systems out there which are still under Microsoft Support but cannot run .Net Framework 4.5.
@user1069816 I am not ready to officially confirm the conformance until we carefully analyze the requirements of PCI DSS 3.1. But in general SecureBlackbox fully implements TLS 1.2 and takes care about recent security-related findings and incapsulates the corresponding workarounds.
@user1069816 We have reviewed the PCI DSS 3.1. PCI-DSS 3.1 requires all compliant environments to get rid of support for SSL (2.0 and 3.0) and TLS 1.0 versions of the protocol until 30 June 2016 at the latest. This is easily achievable with SBB, which provides full support for TLS 1.1 and 1.2 and all modern cipher suites.
@user1069816 As SecureBlackbox uses its own cryptographic and SSL/TLS engines, it is not dependent on specifics of the relevant functionality offered by the operating system or .NET framework. I.e. you can ensure your old XP machines stay PCI-DSS-compliant by migrating your WinAPI- or .NET 2.0-based software product to SecureBlackbox.
|
4

The latest version of SSPI (bundled with Windows 7) has an implementation of TLS 1.2, which can be found in schannel.dll

Improve this answer

2 Comments

Any guidance on how to use this in .NET?
@foson It won't be pretty because SChannel is COM. There is a C++ example here and some very useful notes here
3

.NET Framework 4.6 uses TLS 1.2 by default.

Moreover, only host application should be in .NET 4.6, referenced libraries may remain in older versions.

Improve this answer

Comments

3

You can enable TLS 1.2 in IIS by following these instructions. I presume this would be sufficient if you have an ASP.NET-based application that runs on top of IIS, although it looks like it does not really meet your needs.

Improve this answer

2 Comments

Sorry, this doesn't apply to me. I'm writing an application for running the Syslog protocol, which is very far from ASP.NET and uses regular sockets programming. Unfortunately I need a class equivalent to SslStream to provide me TLS 1.2 services :(
This link 403s now, but the new URL appears to be derekseaman.com/2010/06/…
-1

as mentioned here you can just add this line

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
Improve this answer

3 Comments

This only applies to .NET 4.0.
Not true. The enum goes according to OS. Unless you have 4.5 or higher then you the enum by name.
Not true. First, it depends on the .NET Framework target version. If the OS supports TLS 1.2 is the second question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.