Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • what is the command you are trying to connect?
    – Jakuje
    Commented Dec 17, 2015 at 19:49
  • ssh -v wilhelm.co.za Commented Dec 17, 2015 at 19:53
  • Do you have connection to your agent available? What does ssh-add -l outputs?
    – Jakuje
    Commented Dec 17, 2015 at 19:57
  • Oh sorry, I meant to add that to the question. Turns out I didn't. Editing now Commented Dec 17, 2015 at 20:21
  • when ssh can't open connection to your gpg-agent, it can't use it. It is obvious. You need to add --enable-ssh-support to your gpg-agent as described in the linked question. You need to have at least SSH_AUTH_SOCK environment variable, which should be generated by your agent. Common is to start the agent as eval $(gpg-agent --options).
    – Jakuje
    Commented Dec 17, 2015 at 20:30