Just to expand on tillda’s answer, that config can be placed in an ansible.cfg file alongside your playbook. e.g.: ansible.cfg [defaults] transport = ssh [ssh_connection] ssh_args = -o ForwardAgent=yes I’d say it’s better to do that than setting as an env variable, as placing it in a conf file is both more declarative and also … Read more
You can kill ssh-agent by running: ssh-agent -k !NB, -k argument works only if $SSH_AGENT_PID environment variable is set. eval “$(ssh-agent -s)” sets the variable, but there’re also other methods to start the agent without setting the environment variable. E.g., connecting to a remote server implicitly starts the agent without setting the variable. In this … Read more
I tried the option to add AddKeysToAgent yes to ~/.ssh/config but it doesn’t keep it between new tabs on the terminal. The best solution I found so far is to do the following: sudo apt install keychain Find your hostname using the terminal: hostname Then add the following to your ~/.bashrc or ~/.zshrc file: /usr/bin/keychain … Read more
I had the same problem as you, then I tried adding this code #! /bin/bash eval `ssh-agent -s` ssh-add ~/.ssh/*_rsa into file .bashrc in my home directory. And it works!
Depending on your distribution and on the version of ssh-add you may be able or not to use the -p option of ssh-add that reads the passphrase from stdin in this way: cat passfile | ssh-add -p keyfile If this is not working you can use Expect, a Unix tool to make interactive applications non-interactive. … Read more
From here: $SSH_AUTH_SOCK contains the path of the unix file socket that the agent uses for communication with other processes. This is essential for ssh-add.
Did You Start ssh-agent? You might need to start ssh-agent before you run the ssh-add command: eval `ssh-agent -s` ssh-add Note that this will start the agent for msysgit Bash on Windows. If you’re using a different shell or operating system, you might need to use a variant of the command, such as those listed … Read more
I had the similar problem and my problem was solved by running the following command to add my key to the list of known keys: ssh-add ~/.ssh/id_rsa Hope it solves yours too. 😉
posh-git and git for windows 2.7 should include everything you need to setup an ssh-agent. Once you have the module installed you can start the agent using something like: Import-Module ~\Documents\WindowsPowerShell\Modules\posh-git\posh-git Set-Alias ssh-agent “$env:ProgramFiles\git\usr\bin\ssh-agent.exe” Set-Alias ssh-add “$env:ProgramFiles\git\usr\bin\ssh-add.exe” Start-SshAgent -Quiet You then should see the SSH_AUTH_SOCK environmental variable is set: C:\Code\Go\src\bosun.org\cmd\scollector [master]> gci env:SSH_AUTH_SOCK Name Value … Read more
No tweaks needed. Just make TortoiseGit point to the same ssh client used by git itself, see the screenshot: This should be C:\Program Files\Git\usr\bin\ssh.exe in latest version of Git as mentioned by Aleksey Kontsevich in the comments.