How to use the ~/.ssh/config file with Pageant under windows

pageantssh

I am using Pageant on my Windows machine to manage my SSH key. I have used ssh-agent before, but since Vagrant does not use ssh but net-ssh on vagrant up/provisioning I need to have my key in Pageant to use agent forwarding there.

I heavily use my ~/.ssh/config file to configure host shortcuts, keys they should use etc.

The .ppk file that pageant uses is not compatible with the ssh client, so I can not put it in the IdentifyFile directive.

I could, of course, let my ssh-agent run, too, but this kind of duplicates everything.

How do I combine pageant with my ssh client?

To clarify what I want to do:

Add my SSH-Key to Pageant
Configure user@myhost.com in the ~/.ssh/config as 'myhost'

Host myhost
    User calo
    Hostname myhost.com
    IdentityFile ~/.ssh/myhost

Open up a git bash and type ssh myhost to connect to my host without having to put down my password again, because it would be taken from the pageant.

Best Answer

It can be done. You need to:

create windows environment variable named GIT_SSH
put the path to your plink.exe as value, for me it was:
```
C:\Program Files\PuTTY\plink.exe
```
logout & login (or restart your compouter)
you should be done, you can confirm yourself you have set the variable right by git bash command:
```
$ export
```
(shows all env variables)

Related Solutions

Using IdentityFile Directive in ssh_config with AgentForwarding

You can use the public part of a key to to specify which private key you want to use from the forwarded agent. This requires creating an extra file (the public part of the key) on any “intermediate” machines (machines to which you forward your local ssh-agent).

Arrange for the intermediate machine to have a copy of the public part of the desired key in a convenient location (e.g. ~/.ssh/some_other_key.pub).

From any machine that already has the public part of the key:
```
scp some_other_key.pub intermediate:.ssh/
```
or, on the intermediate machine:
```
ssh-add -L | grep something_unique > ~/.ssh/some_other_key.pub
```
You may want to edit the trailing “comment” part of the public key to better identify the key’s origin/owner/purpose (or attempt to hide the same).
Use the pathname to the above public key file with -i or IdentityFile.
You may also need to use IdentitiesOnly yes (in .ssh/config or -o) to keep ssh from trying to offer any additional identities from your forwarded agent.

Windows – How to set up SSH auth with Windows/git/tortoisegit/putty/Synology

Make sure you have followed heavyd directions on the ssh keys

Windows Git AND TortoiseGit require 2 environment variables set in Windows.

GIT_SSH=C:\Program Files\TortoiseGIT\bin\TortoiseGitPlink.exe

SVN_SSH=C:\Program Files\TortoiseGIT\bin\TortoiseGitPlink.exe

(replace with your paths if different)

You also need to make sure the PLINK_PROTOCOL is not being overridden. Otherwise, PLINK_PROTOCOL=ssh

After making these changes, verify access with the following:

Open a Dos Command window issue the command plink git@your git depot server name

If a list of Git repositories is returned, you are communicating with Git.

If an error is returned, you may need to edit your .ssh/config and/or etc/hosts windows files

Best Answer

Related Solutions

Using IdentityFile Directive in ssh_config with AgentForwarding

Windows – How to set up SSH auth with Windows/git/tortoisegit/putty/Synology

Related Question