PuTTY Installer Is Outdated

[MrScruffy04]

By default, GitExtensions allows you to install PuTTY 0.63. Until today (2018-02-22) that was fine for connecting to github. However, due to github discontinuing weak crypto support (https://githubengineering.com/crypto-removal-notice/), PuTTY 0.63 is insufficient.

When I attempted a push, the error message github returned started with FATAL ERROR: Couldn't agree a key exchange algorithm

As a workaround for now, I was able to:

1. Download the latest PuTTY at https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
2. Install PuTTY to the default directory
3. Copy/replace the four PuTTY .exe's in the GitExtensions install directory: pageant.exe, plink.exe, putty.exe, and puttygen.exe

I experienced this on a Windows 7, 32-bit VM where I had not previously installed PuTTY independent of GitExtensions. I was using GitExtensions 2.51 (latest release at the time). The standalone version of PuTTY I installed was 0.70.

[gerhardol]

The PuTTY version has an update in #4470 that should be merged soon, just some testing that is missing. Please chime in on the PR if you have tested this.

I guess this is a candidate for a 2.51 update release too

[grantaholliday]

Are you able to also bump the packaged version of Git for Windows from 2.13.2 to the latest 2.16.2, as it includes Git Credential Manager for Windows, which includes TLS 1.2 support?

[gerhardol]

Are you able to also bump the packaged version of Git for Windows from 2.13.2 to the latest 2.16.2

2.16.1 is in latest master, right now not targeted for next 2.51 update but for next version (may be 3.0)
Git should be updated to latest next "stable" version, at least in next release.
However, I propose that Git is updated separately from GE

[RussKie]

There are few fixes destined for the 2.51 branch, so we can probably update git in that branch as well. I haven't had a chance to look into prep'ing it...

…

On 23/02/2018 10:15 AM, "Gerhard Olsson" ***@***.***> wrote: Are you able to also bump the packaged version of Git for Windows from 2.13.2 to the latest 2.16.2 2.16.1 is in latest master, right now not targeted for next 2.51 update but for next version (may be 3.0) Git should be updated to latest next "stable" version, at least in next release. However, I propose that Git is updated separately from GE — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4509 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEMyXhRI1lb-cQeT3xzor6PVgO5oEt4vks5tXfT2gaJpZM4SQDIh> .

[RussKie]

...and yes, this can be back-patched into 2.51 as well

…

On 23/02/2018 1:17 PM, "Igor Velikorossov" ***@***.***> wrote: There are few fixes destined for the 2.51 branch, so we can probably update git in that branch as well. I haven't had a chance to look into prep'ing it... On 23/02/2018 10:15 AM, "Gerhard Olsson" ***@***.***> wrote: > Are you able to also bump the packaged version of Git for Windows from > 2.13.2 to the latest 2.16.2 > > 2.16.1 is in latest master, right now not targeted for next 2.51 update > but for next version (may be 3.0) > Git should be updated to latest next "stable" version, at least in next > release. > However, I propose that Git is updated separately from GE > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#4509 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AEMyXhRI1lb-cQeT3xzor6PVgO5oEt4vks5tXfT2gaJpZM4SQDIh> > . >

[golddragon007]

Currently I needed to update PUTTY manually, because I get this error:
FATAL ERROR: Couldn't agree a key exchange algorithm (available: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521)
fatal: Could not read from remote repository.
For every github repos. (updated to 0.7 and now it works)

[EbenZhang]

Need to upgrade both git and putty: see https://github.com/blog/2507-weak-cryptographic-standards-removed

[golddragon007]

I just updated the putty and works...

[sahgilbert]

I followed the update steps above and it resolved the issue.

[MarcoWilliamsPF]

I think this is still an issue with Putty x64 .. I am at the latest version of Git & latest version of Putty and I'm getting the same error message.

[RussKie]

Have you updated git to 2.16+?