Skip to content

Commit cbe39d7

Browse files
committed
document TLS 1.2 on Win7
fixes #412
1 parent e815a7a commit cbe39d7

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,3 +97,7 @@ If you know which provider you're talking to and want to avoid the probe, that's
9797
| Bitbucket | `git config --global credential.https://example.com.provider bitbucket`
9898
| Azure DevOps | `git config --global credential.https://example.com.provider azure-repos`
9999
| Generic | `git config --global credential.https://example.com.provider generic`
100+
101+
### How do I fix "Could not create SSL/TLS secure channel" errors on Windows 7?
102+
103+
This likely indicates that you don't have newer TLS versions available. Please [follow Microsoft's guide](https://support.microsoft.com/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392) for enabling TLS 1.1 and 1.2 on your machine, specifically the **SChannel** instructions. You'll need to be on at least Windows 7 SP1, and in the end you should have a `TLS 1.2` key with `DisabledByDefault` set to `0`. You can also read [more from Microsoft](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn786418(v=ws.11)#tls-12) on this change.

0 commit comments

Comments
 (0)