My Git setup runs fine on Linux, but when I try to set things up under Windows (using Git for Windows and TortoiseGit), I don't know where to put my private SSH key (or, better still, how to tell ssh where it's located). I'm using the standard ssh.exe option during installation of Git for Windows. The setup runs fine if I allow password authentication (in lieu of RSA) on the server.

  • I have the same problem, I can ssh into my dev box using a public key as "root" using the "Git Bash" program that is installed with "Git For Windows" but I can't log in as "git" with my key even though I have copied my "authorized_keys" file from my "root" to my "git" user and set the owners and permissions correctly. Why can't I login as "git" when "root" works with the exact same "authorized_keys" file. Instead for "git" it passes up all the private keys, which are the exact same that work with "root" and asks for a password. This is a Centos 5.5 server by the way.
    – user35861
    Commented Nov 5, 2010 at 1:36
  • @fuzzy lollipop: Do you have the right permissions on your git user's authorized_keys file? It should be chmod 600, and should be owned by the git user. If it's owned by the root user, it wont work Commented Nov 5, 2010 at 17:20
  • yes all the files and directories are the correct owners and permissions
    – user35861
    Commented Nov 6, 2010 at 7:21

33 Answers 33


For Git Bash

If you are running msysgit (I am assuming you are) and are looking to run Git Bash (I recommend it over TortoiseGit, but I lean to the CLI more than GUI now), you need to figure out what your home directory is for Git Bash by starting it then type pwd (On Windows 7, it will be something like C:\Users\phsr I think). While you're in Git Bash, you should mkdir .ssh.

After you have the home directory, and a .ssh folder under that, you want to open PuTTYgen and open the key (.ppk file) you have previously created. Once your key is open, you want to select Conversions -> Export OpenSSH key and save it to HOME\.ssh\id_rsa. After you have the key at that location, Git Bash will recognize the key and use it.

Note: Comments indicate that this doesn't work in all cases. You may need to copy the OpenSSH key to Program Files\Git\.ssh\id_rsa (or Program Files (x86)\Git\.ssh\id_rsa).

For TortoiseGit

When using TortoiseGit, you need to set the SSH key via pacey's directions. You need to do that for every repository you are using TortoiseGit with.

  • 4
    pacey's instructions for tortoisegit won't work until you have the repository (because the 'remote' configuration setting doesn't appear unless you act on a repo), and you probably can't get the repository in the first place if you can't authenticate yourself in order to clone from the origin. Tricky!
    – Kylotan
    Commented Oct 6, 2011 at 19:59
  • 46
    With GitBash I found I had to copy my ~/.ssh/id_rsa file to Program Files\Git\.ssh\id_rsa - which was a little confusing, but now IntelliJ and Windows cmd can push to git repositories that use key authentication.
    – JP.
    Commented May 23, 2012 at 12:17
  • 10
    Likewise. I just installed git-for-windows, I am running it from cmd.exe. I needed to put the files id_rsa and id_rsa.pub into c:\program files (x86)\Git\.ssh . The .ssh dir was already present. Thanks, JP.
    – Cheeso
    Commented Jul 26, 2012 at 1:07
  • 5
    Second paragraph was golden. :)
    – Bjørn
    Commented Aug 31, 2012 at 10:51
  • 4
    @Damon: It should be id_rsa without the extension. That is the file name, it is not a directory Commented Nov 27, 2012 at 13:26

Using the built-in SSH client shipped with Git for Windows, you need to set up the HOME environment variable so that the Git SSH client can find the key.

For example, on a Windows Vista installation, this would be done by issuing setx HOME c:\Users\admin\ on the command line.

It made my day and fixed the issue with Git provided that your private key is not password protected. If you want to use ssh-agent, then you can probably run ssh-agent cmd.exe (although I've never done that) and the ssh-add as usual.

Note that all Git/SSH tools are supposed to be run from a cmd.exe in order not to blink a window.

If this does not work correctly, using plink can probably be achieved by tweaking GIT_SSH. Refer to all the SVN + ssh tutorials; this is basically the same plumbing you need to setup.

  • 18
    This is what I was looking for since I'm trying to use the Windows command prompt, not git bash.
    – John Ruiz
    Commented Mar 5, 2012 at 18:33
  • Nice, easy fix but it would have been hard to figure out without this!
    – thaddeusmt
    Commented Apr 13, 2012 at 20:39
  • Important is as well to have no blanks between HOME = and c:\... Oct's solution did the trick for me. :-)
    – Lutz
    Commented Apr 21, 2012 at 23:09
  • Worth noting - if you have spaces in your home (if you are using win XP/server 2003 you will), then you should prefix the path with a single quote. Bizarrely - if you end it with a quote that will be in the variable... Commented Apr 16, 2013 at 10:57
  • 2
    The setx HOME c:\Users\admin` command doesn't seems to be working in Git Bash. You have to use cmd` instead.
    – trejder
    Commented Dec 12, 2013 at 8:01

You can specify the key location for TortoiseGit the following way:

  • Open an Explorer Window.
  • Open the Contextmenu and navigate TortoiseGitSettings
  • In the now opened window, navigate to GitRemote
  • Set the path to your PuTTY key in the corresponding input box.

A screenshot is below:

Enter image description here

  • 9
    Additionally if you need to convert your private key into '.ppk' format from other format you can follow THIS Commented Dec 18, 2013 at 11:04
  • It worked for me. Commented Sep 10, 2014 at 16:53
  • 6
    Git > Remote only appears once you've successfully cloned the repository. Commented Jul 23, 2015 at 9:18
  • 5
    A much easier solution is to set everything up working properly in git (using openSSH), and then tell TortoiseGit to use the ssh.exe used by git. See stackoverflow.com/a/33328628/318317 That way, you only need to fix this once. Commented Feb 4, 2016 at 16:04

None of the previous answers worked for me. Here was what worked for me in the end. It is actually fairly simple, if you know what to type. It doesn't need PuTTY.

  • Open a Git Bash prompt
  • Type 'ssh-keygen'
    • Accept the default location
    • Choose a blank passphrase (so just press 'enter' to all questions')
  • Now copy the public key to your server, for example: scp ~/.ssh/id_rsa.pub [email protected]:~

That's the bit on your own computer done. Now ssh into the destination server, then do

mkdir -p ~/.ssh
cd ~/.ssh
cat ../id_rsa.pub >> authorized_keys
rm ../id_rsa.pub

That's it! You're done! From Git Bash, do the following to test:

ssh [email protected] ls

If it lists the files in your home directory on the Git server, and then you're done!

For GitHub, you don't have shell access to their server, but you can upload the key using their website, so for the bit 'now copy to your server', do:

  • In Git Bash, type 'cat ~/.ssh/id_rsa.pub', select the result, and copy it to the clipboard.
  • On the GitHub website, go to 'Account settings', 'SSH and GPG keys', click 'New SSH key', and paste the key.
  • 11
    Don't create keys without passphrases. It's like putting your password in a text file, except that everyone knows the default location for private keys.
    – GregB
    Commented Apr 11, 2013 at 6:10
  • 21
    You're answering the wrong question. The Q is how to point to an existing private key.
    – Orangutech
    Commented Apr 17, 2013 at 18:18
  • 8
    @GregB, I look at it like this: any server for which I create a password-less key is as secure as my laptop, it's an extension of the security perimeter of my laptop. Actually, not even, since my home directory is encrypted ;-) So, it's as secure as the encrypted home partition on my laptop, which is 'good enough' for securing access to github, in my opinion. (which may vary from your opinion of course!) Commented Jun 21, 2013 at 5:38
  • 4
    @GregB Don't fall down into paranoia! :] Sure, that using password-protected keys is much more secure, than using password-less, but claiming that password-less key is as easy to break as storing passwords in a text file is an obvious false. I've seen many guides, that encourage users to use password-protected keys, but I have never seen any claiming, that using them without passwords is not secure at all. Plus: some systems doesn't support solutions for remembering key's password, entered by users, and asks for it, each time key is used. Which makes using SSH keys pointless in this situation.
    – trejder
    Commented Dec 12, 2013 at 8:33
  • 5
    For the sake of the conversation, which has deviated from the original question, SSH keys are certainly more cryptographically secure than passwords, but that security is put at risk by not encrypting your SSH keys. My personal approach is to unlock my keys at the beginning of the day using an SSH agent, which then keeps the decrypted keys in memory so that I don't need to re-enter the password throughout the day. As @Hugh Perkins comments, and I'm paraphrasing, you all know your security requirements better than I/we do :).
    – GregB
    Commented Dec 13, 2013 at 18:09

If you're using msysgit with the OpenSSH tools, you need to either create ~/.ssh/id_rsa, or create a Git configuration in ~/.ssh/config which points to your key.

Here's an example of a Git configuration for Bitbucket that will use the correct username, and a key other than the default key (in case you maintain one key for SSH connections, and another for Git accounts).


Host bitbucket.org
    Hostname bitbucket.org
    User git
    IdentityFile /C/keys/yourkey.key

Once in Git Bash, you can run two commands to add your key to your current session's ssh-agent to avoid having to repeatedly type the key's password.

eval `ssh-agent`
ssh-add /C/keys/yourkey.key
  • 3
    I did this but for github.com: Host github.com IdentityFile ~/.ssh/github_rsa Commented Jun 22, 2013 at 18:28
  • 1
    If you have a space in your path you have to use quotes: IdentityFile "/C/My Keys/key"
    – roeland
    Commented Aug 1, 2014 at 10:31
  • I prefer this way, because this allowed me fast connect existed keys from other PC Commented Jun 30, 2017 at 7:10
  • My .gitconfig has sections. Under which sections should I put these hosts? Commented Oct 8, 2017 at 10:47

I just set %HOME%=%HOMEPATH%

This has the advantage of working for all users logged into the system (they each get separate .ssh folders).

In Vista:

  1. Right-click on Computer
  2. Choose Properties
  3. Click on Advanced System Settings
  4. Click on Environment Variables
  5. In the bottom section (System Variables) Click on New
  6. For Variable name type: HOME
  7. For Variable path type: %HOMEPATH%
  8. Click OK
  • 7
    In my case I've added HOME = %USERPROFILE%
    – igor
    Commented Oct 14, 2013 at 11:41
  • 1
    Note that %HOMEPATH% does not contain the drive letter, so if your source is not on C: you need to prepend C: to %HOME%. Commented Mar 2, 2016 at 12:36
  • set %HOME%=%HOMEPATH% worked for me! Thank you!!
    – pangyuteng
    Commented Dec 19, 2018 at 18:09
  • to cope with the fact that %HOMEPATH% is not a full path, use: 1. via command-line, setx HOME %HOMEDRIVE%%HOMEPATH%; 2. via Control Panel, in step 7 above use %HOMEDRIVE%%HOMEPATH%. Commented May 27, 2022 at 16:48

In my case I was using Git for Windows in the Docker container windowsservercore.

My Git was installed by Chocolatey to C:\Program Files\Git.

I had to update the file C:\Program Files\Git\etc\ssh\ssh_config with this:

Host example.com
   Identityfile ~/.ssh/id_rsa

Then I was could use key from C:\Users\<user>\.ssh\id_rsa

If you are using Git for windows together with OpenSSH for Windows. Git is still using its own ssh.

Plus if you plan using ssh-keyscan host.com > known_hosts from OpenSSH, be careful because piping output from stdout of keyscan (on Windows) changes encoding to UCS-2, but OpenSSH can read only UTF-8! So make sure to change the known_hosts file encoding.

  • This helped, but for anyone who's using an id_dsa key, you'll also need to add "PubkeyAcceptedKeyTypes ssh-dss" under your host. Commented Nov 30, 2017 at 16:47

Your private key needs to be added to the SSH agent on your workstation. How you achieve this may depend on what git client you are using, however puTTY and its associated agent (pageant) might do the trick for you, here's the link to the official binaries and source:


  • I stated above that I'm using Git for Windows and am using ssh.exe (packaged w/ git) in lieu of putty. There must be some standard practice for adding a private key, I just can't seem to find out how. While switching software may indeed allow me to log in, there has to be a way to do it with the standard Git setup, no? Commented Oct 25, 2010 at 21:32
  • Sorry i dont work on windows, only linux. But the key does have to be in your SSH agent. is there an agent.exe or something along those lines? Commented Oct 25, 2010 at 22:01
  • 1
    Yeah, setup was cake on the linux side. But I've got to have it working on Windows too unfortunately. There are several ssh-related executable files in the git/bin folder on the Windows box (ssh, ssh-add, ssh-agent, ssh-keygen & ssh-keyscan), but I don't know how to make any of them do anything. They just blink a cmd window open and close right away. I'm stumped. Commented Oct 26, 2010 at 1:13
  • 8
    Pageant does indeed solve the problem for me -- I have a shortcut in my Start Menu's Startup folder (C:\Users\owen.blacker\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) pointing to "C:\Program Files (x86)\PuTTY\pageant.exe" "C:\Users\owen.blacker\Documents\SSH\OwenBlackerPersonal.ppk" "C:\Users\owen.blacker\Documents\SSH\OwenBlackerWork.ppk", so that it loads my SSH keys on startup and this makes GIT "just work" :o) Commented Jun 27, 2012 at 12:51
  • @OwenBlacker OMFG! You definitely should write this comment as a full-size answer! This is the only solution here, that actually helped me and solved my problem! Pity, that I can give you only +1! :]
    – trejder
    Commented Dec 12, 2013 at 9:01

The most efficient way is using Pageant because it will let you write the passphrase only once at the beginning of the session instead of every push. All answers here were too short, so I'll post a detailed guide here:

  1. Download pageant.exe, puttygen.exe, putty.exe and plink.exe from PuTTY's website. Place them in C:\puttyTools directory.
  2. Run puttygen.exe.
  3. Click button Generate.
  4. Wiggle the mouse around in the top part of the window until the progress bar is full, as the program asks you to do.
  5. Provide a passphrase, and repeat it in the subsequent textbox.
  6. Click "Save private key". The usual directory to save these in is %USERPROFILE%\.ssh (in my computer this maps to C:\Users\andres\.ssh\). It doesn't matter what you call the key, but for demonstration purposes, I'm going to call it github.ppk. This file should have an extension of .ppk.
  7. Copy the text in the top text box in PuTTYgen, the one labeled Public key for pasting into OpenSSH authorized_keys file and paste it into a new SSH key in GitHub's settings. Give it a title that describes what machine the key is on (e.g. "Work laptop").
  8. Run pageant.exe, a new systray icon will appear.
  9. Right click on the icon -> Add key.
  10. Locate your ppk file, enter your passphrase.
  11. Create these new user environment variables (via looking for application Environ through WindowsMenu which will find Edit environment variables for your account): GIT_SSH = "C:\puttyTools\plink.exe" and SVN_SSH = "C:\puttyTools\PuTTY\plink.exe"
  12. Open putty.exe and try to connect to the host where you host your Git repositories. For example, try to connect to github.com via SSH, and a dialog will ask you if you accept the fingerprint of the server: click on YES.
  13. Run a new instance of your MINGW64 Git console, and verify that the environment variables are there by writing the command env | grep -i ssh.
  14. You should be all set. Try to clone with the Git + SSH protocol from your host.

(Originally extracted from these two guides which I combined in one: How to setup Git for Windows and Configure MinGW-W64+MSYS to use PuTTY Plink/Pageant.)


I've fixed the above issue by creating


file and put:

IdentityFile C:\Users\adria\.ssh\mysshkey
  • 1
    – Rainb
    Commented Jul 4, 2020 at 21:08

I had similar issues and none of the answers here solved the problem. It turns out, my key pair were originally generated with an empty passphrase. (I know, dumb.)

Once I created a new keypair and uploaded the public key to GitHub, things started working again.

  • 2
    this. ughhhhhhhhhhhhh. good bye 2 hours
    – Scoop
    Commented Feb 5, 2015 at 10:36

When mixing GitHub for Windows and Git GUI for Windows, you might run into issues where Git GUI keeps prompting you for a username and password. The cure for this is to change the remote URL from https: (which is what GitHub for Windows creates) to the Git protocol. In the .git directory in the configuration file, find:

[remote "origin"]
   url = https://github.com/**username**/**reponame**.git
   fetch = +refs/heads/*:refs/remotes/origin/*

Change it to:

[remote "origin"]
    url = [email protected]:**username**/**reponame**.git
    fetch = +refs/heads/*:refs/remotes/origin/*
  • Yeah it is very annoying. It is natural and easy to clone a repo with github for windows GUI, but when use git cui outside of git shell failed. I wonder how the git command in the git shell works with https url...
    – hiroshi
    Commented Mar 5, 2016 at 1:18
  • for SSH is the prefix always git@{SERVER URL} ?
    – nmz787
    Commented Apr 15, 2016 at 20:41
  • Yes, as far as I've ever seen :) Commented Apr 19, 2016 at 4:11
  • Already had this - still asks me all the time Commented Aug 2, 2017 at 9:04
  • this is not the answer to the question
    – Rainb
    Commented Jul 4, 2020 at 21:05

The standard location for the files is in %USERPROFILE%\.ssh.

%USERPROFILE% is the equivalent of $HOME in Unix (normally maps to something like c:\users\youruserid).

If you are using the SSH tools that came with Git, which are the standard command line Unix-style tools, you can use something like my script here to work with ssh-agent across all shells.

  • For future readers, %USERPROFILE% is the equivalent of $HOME is not the equivalent of $HOME. A lot of bad acting Linux apps ported to Windows treat t the two the same e but they should not be treated the same. Commented Aug 30, 2017 at 18:23
  • Micah, can you inform the differences in intent for that? Also, even with different intent, it would seem that if all the tools use one as the other, then doesn't it effectively become equivalent?
    – Eric Blade
    Commented Aug 31, 2017 at 19:54
  • Tools that use %USERPROFILE% on Windows in the same way as $HOME on Linux are violating well documented best practices/recommendations for Windows development (published by MS long ago and updated over time). There are many tools that do this, but the argument to follow them is much like the argument "X pees in the pool, so we should too." USERPROFILE is where the user stores documents they create/save (e.g., save dialog). APPDATA is for per-user configuration data. LOCALAPPDATA is for per-user caches and large files. PROGRAMDATA is for machine-wide configuration and cache. Commented Aug 31, 2017 at 20:32
  • In general, the only tools that misbehave with USERPROFILE are tools written by Linux developers and then ported to Windows. As a developer, you probably use a lot of these so it feels like "everyone is doing it" but outside of the development tooling ecosystem most Windows applications actually are good citizens. Even Microsoft sometimes makes the mistake of not putting things in the right place (they are a huge company), though in general when you point it out to them they make an effort to resolve the problem and follow OS guidelines. Commented Aug 31, 2017 at 20:34
  • 1
    (sorry, StackExchange character limits on comments). Here is more details about the folders and a brief description of what goes in each. There are other resources as well, including more consumable blog posts, but this one offers the most technical accuracy: technet.microsoft.com/en-us/library/cc749104(v=ws.10).aspx Commented Aug 31, 2017 at 20:39

OK, I looked at the suggestion of ..

But placing in my private SSH keys in public folder I didn't think was a good idea, so I started to look for where the knownhost was.

So if you want to correctly protect your SSH key you need to put your key in the following directory:

For Windows 7, 8, and 8.1 32-bit:

C:\Users\\AppData\Local\VirtualStore\Program Files\Git\

For Windows 7, 8, and 8.1 64-bit:

C:\Users\\AppData\Local\VirtualStore\Program Files (x86)\Git\

  • This was the simplest solution on my Win7 machine. Like you, I searched for known_hosts. Sure enough, it was in C:\Users\Dave\AppData\Local\VirtualStore\Program Files (x86)\Git\.ssh. By placing my key file (id_rsa) in that directory, ssh was able to find it without complaint. I did a little reading - this is how Windows handles (legacy) software attempting to write to forbidden areas (such as "C:\Program Files\"), so Git's ssh is completely unaware that it is writing to the VirtualStore directory, Windows is handling that transparently. At least these files belong to a user!
    – DaveGauer
    Commented Apr 29, 2015 at 23:40

The following answer also applies to this question when running ssh from Windows Service Account: Jenkins (Windows Service) with Git over SSH

  • Following the link you provided I was able to get my Jenkins setup. I needed to set the HOME environment variable to the Git program path which held the .ssh directory I created my SSH key in.
    – Spechal
    Commented Sep 3, 2013 at 18:52

TortoiseGit lets you specify the key to use when cloning a repository. Simply check "Load Putty Key" and browse to the .ppk file, as in the screenshot: https://i.sstatic.net/lAyzT.png

  • If disabled, check Settings... -> Network -> SSH client is set to C:\Program Files\TortoiseGit\bin\TortoiseGitPlink.exe Commented Nov 1, 2017 at 11:49

You can specify both the path to the key and the name of the key file like so (on Ubuntu). For example:

ssh -i /home/joe/.ssh/eui_rsa
  • This absolutely solves the problem and allows you to store your keys where ever you would like.
    – DaveGauer
    Commented Apr 29, 2015 at 23:26
  • The question was specifically about windows. I have git on my Ubuntu machine working like this, but I can't tell what to set GIT_SSH_COMMAND to on my Windows machine.
    – mjaggard
    Commented Sep 6, 2017 at 19:12

Pageant (an SSH agent supplied with the PuTTY bundle) solves the problem for me.

I have a shortcut in my Start Menu's Startup folder (C:\Users\owen.blacker\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) pointing to "C:\Program Files (x86)\PuTTY\pageant.exe" "C:\Users\owen.blacker\Documents\SSH\OwenBlackerPersonal.ppk" "C:\Users\owen.blacker\Documents\SSH\OwenBlackerWork.ppk", so that it loads my SSH keys on startup and this makes Git "just work" :o)

  • 4
    I think you need several other settings correct for this to work (such as GIT_SSH set to TortoisePLink.exe I think?), and although it has worked for me in the past, I often get problems with it on other machines. :-(
    – Simon East
    Commented Jun 12, 2014 at 4:08
  • I get 'Unable to open the file' from Pageant :( Which I know is set up correctly as I'm using it for TortoiseGit :( Commented Aug 2, 2017 at 9:02

My msysgit OpenSSL/Bash Git experience (not PuTTY's plink) is that the search order for your the .ssh/ folder is as follows.

  1. %HOME%/.ssh/
  3. %USERPROFILE%/.ssh/

Hence why so many people suggest setting HOME if one of the others is not what you expect. More importantly, you can check for yourself; to debug use ssh -v to a server that uses public key authentication as follows:

$ ssh -v [email protected]
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Reading configuration data /d/.ssh/config
debug1: identity file /d/.ssh/identity type -1
debug1: identity file /d/.ssh/id_rsa type 1
debug1: identity file /d/.ssh/id_dsa type -1
debug1: Next authentication method: publickey
debug1: Trying private key: /d/.ssh/identity
debug1: Offering public key: /d/.ssh/id_rsa
Hi kcd83! You've successfully authenticated, but GitHub does not provide shell access.

We found ssh searching on an obscure drive and none of the previous answers seemed to explain what we saw.

Sometimes %HOMEDRIVE%%HOMEPATH% is a mapped network drive (e.g. H:/) which causes unnecessary failures when there are network/fileserver issues, even when %USERPROFILE%/.ssh is C:/Users/Username/.ssh and has the keys locally. Setting %HOME% to %USERPROFILE% stops it looking at the remote home drive.

  • this answer helped me solve a very peculiar issue where the encryption algorithm of my key wasn't supported by one of the operating systems I was using
    – maja
    Commented Jan 11, 2022 at 14:10

Using Windows 10, I could not get the pageant generated SSH key working (at least for Git on the command line, using SourceTree I didn't have an issue) when running:

git push origin master

So my solution:

  1. I opened 'Git Bash'
  2. Ran

  3. Confirmed keys now exist

    ls ~/.ssh
  4. Opened id_rsa.pub in Notepad++, selected all the contents

  5. Added a new key in Bitbucket, https://bitbucket.org/account/user/myusername/ssh-keys/

  6. Labelled and pasted contents into the key field --> Add Key

After that, command line Git worked. It appears that it wants the old PEM format, because if I try to import this key into pageant it says as much.


Many answers say this, but for me not fast enough!

in windows using msys (standard windows console) C:\Users\{you}\.ssh\id_rsa

Basically it doesn't bother scanning installed keys (at least not on my new laptop) and so needs specifically id_rsa

I encountered this wanting to clone some private work repo's in ruby MSYS CLI for windows 10 64-bit


If you're on Windows 7/8, you should look in C:\Users\Your_User_Name.ssh Just copy & paste your id_rsa file here and it will all work out-of-the-box.


One mistake I made when using SSH on Windows was that when I attempted to use the keys through the Git Bash client, all of the files within ~/.ssh were the wrong permissions, yet it did not attempt to tell me that it was a problem.

Just as a test, make sure you've set everything in your ~/.ssh directory to chmod 600.


If you have the necessary permissions on the Windows machine, and your policies permit it, I would suggest installing Cygwin (https://cygwin.com/), especially considering that you have prior experience with Linux. Cygwin will make it possible to handle your ssh-keys as you would on any other Linux/Unix machine. And it provides access to almost all of the cli tools of Linux.

  • 1
    It is perfectly reasonable to make suggestions like this as comments. But as the question explicitly requests git for windows you should expect down votes for posting this as an answer.
    – rob
    Commented May 16, 2017 at 8:33

Reading your comment to Declan's answer, try opening a command prompt first (Start → Runcmd) and then navigate to that git/bin folder and run ssh-keygen. Theoretically that will generate an RSA key and place it in the appropriate directory. Then you just have got to find it and share your public key with the world.

The reason that the window "blinks" is because Windows runs the program, and when it executes, it closes the command prompt, thinking you're done with it, when you really need the output.


Using v0.17 of Git Gui on Windows I clicked on the following menu command: HelpShow SSH Key.

A dialog appeared entitled Your OpenSSH Public Key. I generated a key and copied it to the clipboard. Then I continued to follow the setup-ssh instructions on githelp from Step Three onwards. Afterwards Git Gui communicated with GitHub silently - no need to enter any credentials.


On my Windows 7 system Git Gui looks for the RSA key in the userprofile/.ssh folder or more specifically c:/users/yourusername/.ssh/.

The tricky part for my setup was getting the shared host at hostmonster to accept the key. The only way I could get it to work was by using Git Gui to create the key pairs (without a password) and then copy and pasting the public key via the control panel, ssh, manage keys.

To start at the beginning, you have to create the keys in Git Gui by going to menu Help, Show SSH key, then Generate Key. Now you will have two new keys in the .ssh directory. Open the .pub file and copy the contents.

Log in to your control panel on the shared host and go into SSH, Manage SSH keys, and Import key. Paste into the Public box, and make sure you name it the right name without the extension-- mine was id_rsa. Now you must authorize the key using the manage authorization link, so it will get concatenated into the authorized_keys file.

Now your Git Gui and your Git Bash should be able to push using SSH without having to type the password. Oddly, I was able to push using SSH via Git Bash and Git Gui just fine on my own servers running Linux, it was just the shared hosting that was giving me fits. I hope this helps someone as it took me hours of trial and error to come up with this--and it's so simple!


If you are using the Git command line for Windows you can do as follows:

Open cmd.exe and execute setx HOME c:\PATH_TO_PRIVATE_KEY.

Create a new folder, .ssh, (if not exist) inside c:\PATH_TO_PRIVATE_KEY and copy your id_rsa file (your private key) into it.

Done. Now you can use the Git command line normally.


You can also load PuTTY Agent (pageant) and add the private key you generated with PuTTY for the server.

Git recognizes this and uses that for push/pull.


I was using TortoiseGit as well as Git Bash on Windows, depending on need. I've added everything into TortoiseGit, and it worked fine, but Git Bash wasn't picking it up even though the keys were in the correct directory. It turns out I had to do this from Git Bash:

ssh-add C:\\Users\\<YOUR_USER>\\.ssh\\id_rsa

You can of course change the path to wherever your key is located, remembering to use \\ as the separator.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .