GitHub introduced a change last week that drops support for weak cryptographic keys. This has resulted in connectivity issues for some users who are connecting to GitHub using SSH and the built-in client SSH Executable.
To rehash, there are two ways to work with Git and SSH when using any of the IntelliJ-based products:
- Using Built-in SSH client
- Using Native SSH client
This setting is configured under Version Control | Git | SSH executable:
It is only when you use the built-in client that this causes issues with the recent changes with GitHub.
This issue has already been fixed for 2018.1 EAP and will be available in the release version. In the meantime, as a workaround, you can switch to using Native support. Please note however that when using this option, if your SSH keys are protected with a passphrase they need to be added at system level. This is usually done by using a tool such as ssh-agent.
We are also backporting the fix to 2017.3 and the EAP for this is already available, with the release version due out in the coming weeks.
To recap, your options right now are:
- Use 2018.1 EAP
- Use 2017.3 EAP
- Switch to use Native as a workaround
We do apologize for not having resolved this issue sooner and will strive to improve.
The JetBrains Team