IntelliJ 2017.3和GitHub存在SSL(TLS v1.2)问题 [英] SSL (TLS v1.2) issues with IntelliJ 2017.3 and GitHub

查看:184
本文介绍了IntelliJ 2017.3和GitHub存在SSL(TLS v1.2)问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

因此,最近在GitHub上删除了较弱的加密标准,我不能再使用GitHub和IntelliJ。我已经做了一些研究,到目前为止,似乎IntelliJ不支持TLSv1.2?

So with the recent weak crypto standards removal at GitHub I can no longer use GitHub with IntelliJ. I've done some research and so far it seems that IntelliJ does not support TLSv1.2?

我看到的唯一SSL协议是网络中的SSLv3和TLSv1版本控制的设置。

The only SSL protocols I'm seeing are SSLv3 and TLSv1 in the Network settings of Version Control.

Subversion>网络设置

我能做些什么吗?

预先感谢。 / p>

Thanks in advance.

推荐答案

TLS仅用于HTTP连接。 IntelliJ确实支持TLS v.1.2

TLS is used in HTTPs connections only. IntelliJ does support TLS v.1.2

问题是您可能使用SSH,并且内置SSH客户端确实无法在 diffie-hellman- group1-sha1 已在GitHub上禁用。

The issue is that you probably use SSH, and builtin SSH client indeed fails to connect after diffie-hellman-group1-sha1 has been disabled on the GitHub.

问题是在2018.1修复

如果您不想更新至EAP,解决方法是您可以在 Settings |下将SSH可执行文件切换到Native版本控制| GIT中。请注意,如果您的密钥受到密码保护,您需要先将它们加载到ssh-agent中。见例如此主题 a>

If you don't want to update to the EAP yet, as a workaround you could switch SSH executable to Native at Settings | Version Control | Git. Note, that if you keys are protected with a passphrase, you need to load them into ssh-agent first. See e.g. this topic

这篇关于IntelliJ 2017.3和GitHub存在SSL(TLS v1.2)问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆