Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


I cannot generate SHA-2 Key with old, SourceTree-affiliated version of puTTY gen


I am using Windows 11 with SourceTree v. 3.4.7 on a Microsoft Surface 7.


I have not been able to push to Github from SourceTree or from Git Bash. When I try from SourceTree, I get the following error: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see for more information.

The link explains that Github, as of today (Jan. 11, 2022) no longer allows SHA-1 keys. It has to be SHA-2 or higher. The link above contains the passage:


Clients relying on older SSH implementations will need to be updated. (The standard Git client uses your operating system’s SSH implementation on Linux and macOS.) Common examples include:

  • OpenSSH before version 7.2
  • PuTTY before 0.75

GitHub has worked with these vendors to make new versions of their packages available.


However, no matter what I do, I cannot get SourceTree to interface with anything but puTTY gen version 0.70.2. I can download puTTY gen version 0.75, but it will not interface with SourceTree. I can generate a key using the external version of puTTY gen, but it is not ideal (I run a lab with students of various backgrounds, and github is difficult enough for them without the added requirements of maintaining a SSH generator that is not affiliated with SourceTree).


Will SourceTree start supporting later versions of puTTY, or should I look for another "friendly" way to authenticate for Git pushes and pulls?

1 answer

SourceTree v3.4.9 uses puTTy 0.76. I was able generate an ecdsa key following a procedure similar to this:

Then I was able to upload this key to GitHub. I ran into other headaches and found the following resources helpful:

For some reason, Git didn't install when I first installed SourceTree. the Git Credential Manager for Windows will install that for you. After following all of these steps, it began working for me. Best of luck!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events