Disabling TLS 1.0 and 1.1

Guest

Please review KB#1161 for instructions on how to update this

This is OS & .NET Framework dependent.

Many users have reported that setting the follow registry will resolved this issue:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 
Value: SchUseStrongCrypto 
Data: 1

Note that this will involve a reboot. See this guide on TLS in .NET for more information.

Edited answer to reflect comments/discussion below

mark.barnard_0845

I'm afraid this doesn't really help. The server is already configured correctly for TLS, but ProGet doesn't work under this configuration (or at least the external connector to Nuget.org doesn't). I assume ProGet does not require TLS 1.0/1.1 so I need to understand why ProGet is giving this error when run under this configuration

thoven

What that article says is that programs should not set specific TLS versions (which ProGet does not) because the defaults will change as the OS is patched/updated. This means that it should be using the most secure by default, which based on the TCP error, it is not doing. Unfortunately this is symptom of applications targeting versions of the .NET Framework before v4.7 like ProGet does (it targets v4.5.2).

We may be able to hack in a fix like we did for our Git extension in a future version, but if you want to get it working right away, follow this part of the guide: Configuring security via the Windows Registry

mark.barnard_0845

Setting the following registry setting has resolved this issue:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 
Value: SchUseStrongCrypto 
Data: 1

Guest

Hello,

I created the key in regedit, but it did not help to solve the problem.

In fact, when I test the connection to github.com in the Proxy Configuration, I get a "Test failed: The request was aborted: Could not create SSL/TLS secure channel." error, whereas https://google.com or https://gitlab.com do work.

Thanks for the help. :)

Guest

Hey!

It did solve my problem, thank you so much!

Have a great week-end. :)

thoven

For completeness, after the registry value is configured the server will likely need a reboot to take effect.

Guest

typo in VERY important registry path given above:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319

should instead be:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

(i.e., original was missing backlash between Microsoft and .NETFramework)

fwiw, it looks like the wiki software is responsible for removing the backslash, as I had to double the blackslash for it to appear in the preview.

Update/Edit by Inedo: thanks, we've edited the post above to be correct

Guest

Hello,

I again have a problem with github.com, saying:
"Receiving...
Error making request.
Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 8080 8080:80"

This time, the test in proxy configuration window on ProGet is successful.

Guest

Please review KB#1161 for instructions on how to update this.