Timeline for gpg-agent instead of ssh-agent
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot |
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
|
|
| Dec 17, 2015 at 21:14 | vote | accept | Wilhelm Erasmus | ||
| Dec 17, 2015 at 21:02 | answer | added | Jakuje | timeline score: 6 | |
| Dec 17, 2015 at 20:49 | history | edited | Wilhelm Erasmus | CC BY-SA 3.0 |
added 342 characters in body
|
| Dec 17, 2015 at 20:49 | comment | added | Wilhelm Erasmus | I had it this way. editing question to include | |
| Dec 17, 2015 at 20:30 | comment | added | Jakuje |
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).
|
|
| Dec 17, 2015 at 20:22 | history | edited | Wilhelm Erasmus | CC BY-SA 3.0 |
added 88 characters in body
|
| Dec 17, 2015 at 20:21 | comment | added | Wilhelm Erasmus | Oh sorry, I meant to add that to the question. Turns out I didn't. Editing now | |
| Dec 17, 2015 at 19:57 | comment | added | Jakuje |
Do you have connection to your agent available? What does ssh-add -l outputs?
|
|
| Dec 17, 2015 at 19:53 | comment | added | Wilhelm Erasmus |
ssh -v wilhelm.co.za
|
|
| Dec 17, 2015 at 19:49 | comment | added | Jakuje | what is the command you are trying to connect? | |
| Dec 17, 2015 at 18:59 | history | asked | Wilhelm Erasmus | CC BY-SA 3.0 |