edit this page - page history - about editing

Getting Git to work over SSH in Windows

Git / Windows

Good luck! You need to do something like this:
  1. Install Cygwin to install bash and openssh
  2. Do not use Cygwin's git; use the Windows installer from git-scm.com, otherwise your text editor (vim) will be all messed up when writing commit messages
  3. You will now have a home directory ~ which will be something like C:/cygwin/home/Jevon
  4. Create new ~/.ssh/id_rsa.pub public keys with ssh-keygen -t rsa by following this article
  5. Import these SSH public keys into your GitHub account SSH keys
  6. Make sure that your GIT_SSH environment variable is set to c:/cygwin/bin/ssh or something similar; if you installed TortoiseGit, this may be messed up to point to a Putty console
  7. Add the ssh-agent script to your ~/.bashrc
  8. Now, you can just run bash in any command prompt, which will ask you for your SSH keyphrase, and you can git push to your hearts content without having to re-enter your passphrase every time
  9. Use this online tool to customise your bash command prompt; this also goes into ~/.bashrc.

It's not remembering my key correctly!


This is wonderful fun. It looks like git push and git pull might use different resolutions of GIT_SSH, i.e. one is working within Cygwin and one is working within Windows.

I found the solution was to, in a normal command prompt, start a SSH agent:

C:>ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-2etb0c3l0U4h/agent.14028; export SSH_AUTH_SOCK;
SSH_AGENT_PID=12016; export SSH_AGENT_PID;
echo Agent pid 12016;

Now, export these variables to your current session, but change /tmp to c:/cygwin/tmp:

C:>SET SSH_AUTH_SOCK=c:/cygwin/tmp/ssh-2etb0c3l0U4h/agent.14028
C:>SET SSH_AGENT_PID=12016

And now it will remember your authentication for this command prompt session. So frustrating. There must be some way to automate this.
Categories: Git | Windows
edit this page - what links to here? - page history - top
Last edited by jevon jevon 25 months ago