Return to Answer

Changed pgp to gpg

Source Link

edit approved Dec 17, 2015 at 21:05

ssh can't open connection to your gpg-agent if you will not give it the way to do so.

When you start your pgpgpg-agent with --enable-ssh-support option, it prints out environmental variables that needs to be available in the shell where from you will be using your ssh. There are few possibilities how to get them:

Stop your pgpgpg-agent and start it once more in like this in the shell where from you are using your ssh (this should be the easiest way to test it):
```
 eval $(gpg-agent --daemon --enable-ssh-support --sh)
```
Find the location of authentication socket and set up the environment variable SSH_AUTH_SOCK by hand

Later on, when you will know that it works, you should set up the agent start according to the manual page for pgpgpg-agent(1), so probably in ~/.xsession to let it start automatically.

ssh can't open connection to your gpg-agent if you will not give it the way to do so.

When you start your pgp-agent with --enable-ssh-support option, it prints out environmental variables that needs to be available in the shell where from you will be using your ssh. There are few possibilities how to get them:

Stop your pgp-agent and start it once more in like this in the shell where from you are using your ssh (this should be the easiest way to test it):
```
 eval $(gpg-agent --daemon --enable-ssh-support --sh)
```
Find the location of authentication socket and set up the environment variable SSH_AUTH_SOCK by hand

Later on, when you will know that it works, you should set up the agent start according to the manual page for pgp-agent(1), so probably in ~/.xsession to let it start automatically.

ssh can't open connection to your gpg-agent if you will not give it the way to do so.

When you start your gpg-agent with --enable-ssh-support option, it prints out environmental variables that needs to be available in the shell where from you will be using your ssh. There are few possibilities how to get them:

Stop your gpg-agent and start it once more in like this in the shell where from you are using your ssh (this should be the easiest way to test it):
```
 eval $(gpg-agent --daemon --enable-ssh-support --sh)
```
Find the location of authentication socket and set up the environment variable SSH_AUTH_SOCK by hand

Later on, when you will know that it works, you should set up the agent start according to the manual page for gpg-agent(1), so probably in ~/.xsession to let it start automatically.

Source Link

created Dec 17, 2015 at 21:02

Jakuje

21.4k
7
53
72

ssh can't open connection to your gpg-agent if you will not give it the way to do so.

Stop your pgp-agent and start it once more in like this in the shell where from you are using your ssh (this should be the easiest way to test it):
```
 eval $(gpg-agent --daemon --enable-ssh-support --sh)
```
Find the location of authentication socket and set up the environment variable SSH_AUTH_SOCK by hand

Later on, when you will know that it works, you should set up the agent start according to the manual page for pgp-agent(1), so probably in ~/.xsession to let it start automatically.