Skip to content

Commit

Permalink
Update 10013,HttpProtocol,.NetFramework.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Ryu3tthz committed May 7, 2020
1 parent 2ecad2e commit 5446b5e
Showing 1 changed file with 47 additions and 19 deletions.
66 changes: 47 additions & 19 deletions 10013,HttpProtocol,.NetFramework.md
Original file line number Diff line number Diff line change
@@ -1,31 +1,59 @@
<!--
* @Author : Primimy
* @Date : 2020-05-07 23:11:41
\* @Author : Primimy
\* @Date : 2020-05-07 23:11:41
-->

# Windows Event Log TLS shows that _A fatal error occurred while creating a TLS client credential. The internal error state is 10013._

## Description
1. Windows Event Log TLS shows that _A fatal error occurred while creating a TLS client credential. The internal error state is 10013_.
2. Failed to login in Github in Visual Studio with its extension, explorer shows that _waiting for localhost_.
3. Failed to clone Github repository: _Git failed with a fetal error_.
4. Failed to update/download extensions in marketplace with a error _Could not create SSL/TLS secure channel_ or _The underlying connection was closed: An unexpected error occurred on a send_.

1. Windows Event Log TLS shows that ***A fatal error occurred while creating a TLS client credential. The internal error state is 10013.***

2. Failed to login in Github in Visual Studio with its extension, explorer shows that ***waiting for localhost***.

3. Failed to clone Github repository: ***Git failed with a fetal error***.

4. Failed to update/download extensions in marketplace with a error ***Could not create SSL/TLS secure channel*** or ***The underlying connection was closed: An unexpected error occurred on a send***.

## Reproduce
Use IIS Crypto to change default protool(server, client)with ___Best Prctice___ template and manually change it on TLS/SSL protocols.

Use IIS Crypto to change default protocol (server, client) with ***Best Practice*** template and manually change it on TLS/SSL protocols.

## Fix

Use IIS Crypto to apply its best practice template.
Modify registry.(constrst newly installed Windows registry will be more accurate)

Modify registry.(contrast newly installed Windows registry will be more accurate)

1. _[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]_
Delete every item in its sub keys.
​ delete every item in its sub keys.

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

3. _[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.5.25000]"SchUseStrongCrypto"=dword:00000001_
4._[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]_"SchUseStrongCrypto"=dword:00000001_
5. Reboot.
4. _[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001_

Reboot.

## Reason
Modification on registry of IIS Crypto will break default tendency protocol on Windows, when visit websites only supporting TLS 1.2 or above, will be failed to (*?*)handshake with the site.

Modification on registry of IIS Crypto will break default tendency protocol on Windows, when visit websites only supporting TLS 1.2 or above, will be failed to (***?***)handshake with the site.

## Reference
1. _https://www.smarterasp.net/support/kb/a1968/how-to-fix-error-underlying-connection-was-closed-an-unexpected-error-occurred-on.aspx_
2. _https://stackoverflow.com/questions/2859790/the-request-was-aborted-could-not-create-ssl-tls-secure-channel_
3. _https://developercommunity.visualstudio.com/content/problem/298616/failing-to-clone-github-repository-ssl-error.html_
4. _https://www.smarterasp.net/support/kb/a1968/how-to-fix-error-underlying-connection-was-closed-an-unexpected-error-occurred-on.aspx_
5. _https://support.microsoft.com/en-us/help/4458166/applications-that-rely-on-tls-1-2-strong-encryption-experience-connect_
6. _https://www.microsoft.com/en-us/download/details.aspx?id=55266_
7. _https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc776467(v=ws.10)?redirectedfrom=MSDN_

1. *https://www.smarterasp.net/support/kb/a1968/how-to-fix-error-underlying-connection-was-closed-an-unexpected-error-occurred-on.aspx*

2. *https://stackoverflow.com/questions/2859790/the-request-was-aborted-could-not-create-ssl-tls-secure-channel*

3. *https://developercommunity.visualstudio.com/content/problem/298616/failing-to-clone-github-repository-ssl-error.html*

4. *https://www.smarterasp.net/support/kb/a1968/how-to-fix-error-underlying-connection-was-closed-an-unexpected-error-occurred-on.aspx*

5. *https://support.microsoft.com/en-us/help/4458166/applications-that-rely-on-tls-1-2-strong-encryption-experience-connect*

6. *https://www.microsoft.com/en-us/download/details.aspx?id=55266*

7. *https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc776467(v=ws.10)?redirectedfrom=MSDN*

0 comments on commit 5446b5e

Please sign in to comment.