Gitup: Gitup no longer works with GitHub

[fushi]

This is likely being caused by https://githubengineering.com/crypto-removal-notice/ (per #241).

[hawkrives]

It still works for me (on 10.13 High Sierra)?

Edit: because I'm using https for my repos

[combs]

Completely dead in the water for me on 10.12.6

[gabehoffman]

not working at all for me (High Sierra - 10.13.3) (Gitup 1.0.9 1024)

[luong-komorebi]

not working for me (High Sierra, gitup 1.0.9). But guys , I think the latest release will fix this problem for us. Waiting for an update to come 😄

[swisspol]

Can anyone try with 1.0.10?

[swisspol]

Looks an updated version of libssh2 is needed

[meduzen]

I tried with GitUp 1.0.9 and 1.0.10, the error remains the same no matter the GitHub project:

Failed connecting to "origin" remote: Failed to start SSH session: Unable to exchange encryption keys

Works on other repositories servers (private, or gitlab.com). And MacOS git something works on github.com.

MacOS 10.12.6 here. Will also try this week-end on a MacOS 10.13.xx computer and let you know (if no fix comes meanwhile).

[filiptepper]

No luck, GitUp 1.0.10, macOS 10.13.3.

[mluisbrown]

I built a version on my local machine using version 1.8.0 of libssh2 (as mentioned here) and that version works fine.

Just a question of using an updated libssh2 which supports the newer crypto standards now enforced by GitHub.

[Gryzor]

I also tried w/ 1.0.10 (and reverted to 9), high sierra. Same problem.

[mluisbrown]

@Gryzor the problem is independent of the version of GitUp and of the version of the OS. All current GitUp versions use the same old version of libssh2 which uses standards that GitHub no longer support. Until there is an updated version of GitUp using a more recent version of libssh2, this problem will continue.

[Gryzor]

@mluisbrown I gathered that from the thread, thanks. Just added the info because it appeared @swisspol didn’t know if this was the case; I commented from mobile, so I didn’t have the full thread reloaded. 👍

[csjones]

Started getting this error yesterday but was able to resolve the issue by changing remote.origin.url in the git config from [email protected]:csjones/gg.git to https://github.com/csjones/gg.

[fushi]

@csjones Yes, using HTTPS instead of SSH fixes the problem.

[meduzen]

Yes, it _fixes_ the problem, but then you have to provide credentials on each interaction with your GitHub repository, unless you give GitUp full access to your Keychain.

[douglashill]

I put up a build of my fork with libssh2 1.8.0 as described above: https://github.com/douglashill/GitUp/releases

[luong-komorebi]

@douglashill Can you open a pull request for upstream to fix the problem?

[douglashill]

I’m not going to submit a pull request, but if someone else wants to take my changes and do that go ahead.

[mluisbrown]

I have created a PR for Libraries to update the version of libssh2. Once that is approved, a new PR can be created to point to the new version of the Libraries submodule.

[swisspol]

Should hopefully be fixed now in master.