thelevelup/pos-tls-patcher

A simple installer which enables Transport Layer Security (TLS) 1.2 on Microsoft Windows Vista Service Pack 2 or later.

pos-tls-patcher's Issues

Question for a specific scenario

First of all, this project is very nice and neat as it describes the such problem by defining the big TLS "chaos" between old .NET programs, OSes and newest secure servers.

However I searched many resources including stackoverflow and this one and found no definite answer to my question.

Issue; It is known that Windows 7 SP1 supports both TLS 1.2 and 1.1 out of the box but they are not enabled. And Microsoft support articles and docs dictate that for example TLS 1.2 can easily be enabled for Schannel-level by tweaking the registy mentioned in your projects "Schannel Registry Keys", just like setting the required values of this key:

HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client

Thus the question is, if we have .NET 4.0 on Windows 7 SP1, can't we simply enable TLS 1.2 in our apps by default (with/without code changes of ServicePointManager) by making such system-wide registry change above WITHOUT requring to install .NET 4.6 (or .NET 4.5) as it is a global Schannel registry tweak?

Is it still and "really" required to install .NET 4.6 (some articles say 4.5) along with existing .NET 4.0 environment even we do all the necessary registry changes?

Best regards.

Net 4.x key

I see that the key for 3.5 and lower below is included with the patcher

HKLM\SOFTWARE\Microsoft.NETFramework\v2.0.50727 | SystemDefaultTlsVersions | 0x00000001

Is this not required for 4.x aswell or is the behaviour different for this key?

Lifesaver

This isn't really an issue, I just wanted to say how truly helpful this was. After banging my head against a table for hours I stumbled on this and it just sorted everything like magic. Thank you!