“致命的:遇到HttpRequestException."由于放弃TLS-1.0支持，导致GitHub/Bitbucket存储库出错 [英] "fatal: HttpRequestException encountered." Error with GitHub/Bitbucket Repositories due to dropping TLS-1.0 support

问题描述

我最近推送到GitHub存储库时遇到以下消息:

I recently encountered the following message when I pushed to a GitHub repo:

"fatal: HttpRequestException encountered. " 然后再次提示我输入用户名和密码.

"fatal: HttpRequestException encountered. " followed by being prompted for my username and password again.

从以前的搜索中， Visual Studio 和各种其他有相同的根本问题.对于那些比我懒惰的人，这里有针对不同应用程序/操作系统的各种解决方案的摘要，并进行了相关讨论.希望人们对此有所帮助.

From previous searches, Visual Studio and various others have the same root problem. For those lazier than I am, a summary of the various solutions for different applications/OS are here with relevant discussions. Hopefully people find this helpful.

不能真正将更新安全性称为问题，所以这就是原因.问题是GitHub已删除TLS-1.0支持，这导致客户端出现问题，包括Microsoft Visual Studio的内置git客户端，1.14以下的Git版本以及GUI客户端(包括tortoiseGit等).可以在此处找到完整的发行说明: https://githubengineering.com/crypto-removal-notice/

Can't really call updating sercurity a problem, so here's the reason. The issue is GitHub has removed TLS-1.0 support which is causing the problem with clients including Microsoft Visual Studio's built in git client, versions of Git below 1.14 as well as GUI clients includint tortoiseGit, etc. The full release notes can be found here: https://githubengineering.com/crypto-removal-notice/

Bitbucket 将删除TLSv1.0和TLSv1 .1从2018年12月1日开始.我期望与以前类似的问题.

Bitbucket will drop TLSv1.0 and TLSv1.1 starting 1 Dec 2018. I expect similar problems as before.

将我的自我答案移至答案框.见下文.

moved my self-answer to an answer box. See below.

推荐答案

Git集线器已从其身份验证服务中删除了TLS-1.0. https://githubengineering.com/crypto-removal-notice/

Git hub has removed TLS-1.0 from it's authentication services. https://githubengineering.com/crypto-removal-notice/

使用适用于Windows的2.14.3版(或更高版本)的Git及更高版本，包括适用于Windows的最新Git凭据管理器: https://gitforwindows.org/

Use Version 2.14.3 (or newer) of Git for Windows and newer include an up-to-date Git Credential Manager for Windows: https://gitforwindows.org/

您还可以将Git Windows Credencial Manager显式更新到最新版本1.14.0，以获得TLS-1.2支持:

You can also explicitly update your Git Windows Credencial Manager to the latest version, 1.14.0, to get TLS-1.2 support: https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.14.0

建议将客户端更新到VS 2017，或者，如果无法升级，则可以设置两个计算机范围的注册表项，这些注册表项会影响可以更改的客户端计算机上所有基于.NET的应用程序... https://developercommunity.visualstudio.com/content/problem/201457/unable-to-connect-to-github-due-to-tls-12-only-cha.html

It is suggested to update your client to VS 2017 or, if you cannot upgrade, there are two machine-wide registry keys you can set that affect all .NET-based applications on the client machine that you can change... https://developercommunity.visualstudio.com/content/problem/201457/unable-to-connect-to-github-due-to-tls-12-only-cha.html

TLS-1.2在JDK8中是默认设置，在JDK7中可用. https://blogs.oracle.com/java -platform-group/diagnosing-tls，-ssl和-https

TLS-1.2 is default in JDK8 and available in JDK7. https://blogs.oracle.com/java-platform-group/diagnosing-tls,-ssl,-and-https

RH 5不支持TLS-1.2，并且GitHubEngineering建议更新到较新版本的OS. RH 6.8和7.2将支持TLS-1.2. https://www.linuxquestions.org/questions/blog/mensawater-183304/rhel5-wont-support-tlsv1-1-or-higher-36951/

RH 5 does not support TLS-1.2 and GitHubEngineering suggest updating to newer versions of the OS. RH 6.8 and 7.2 will support TLS-1.2. https://www.linuxquestions.org/questions/blog/mensawater-183304/rhel5-wont-support-tlsv1-1-or-higher-36951/

这篇关于“致命的:遇到HttpRequestException."由于放弃TLS-1.0支持，导致GitHub/Bitbucket存储库出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！