Contents
Can a gpg agent be forwarded to a remote system?
Forwarding gpg-agent to a remote system over SSH. GnuPG 2.1 enables you to forward the GnuPG-Agent to a remote system. That means that you can keep your secret keys on a local machine (or even a hardware token like a smartcard or on a GNUK). You need at least GnuPG 2.1.1 on both systems.
What does it mean when SSH remote port forwarding failed?
Going into the sshd /var/log/secure on the server shows these errors: Solving requires rebooting the VPS. Until then, all attempts to reconnect give the “remote port forwarding failed” message and will not work. It’s now to the point where the tunnel only lasts about 4 hours before stopping.
Do you need GnuPG 2.1 for agent forwarding?
GnuPG 2.1 enables you to forward the GnuPG -Agent to a remote system. That means that you can keep your secret keys on a local machine (or even a hardware token like a smartcard or on a GNUK ). You need at least GnuPG 2.1.1 on both systems.
Is there a way to Remot SSH with gpg?
SSH remoting works flawlessly, signing with a passphrase protected key has to be done on the command-line, as the GUI fails to present the dialog needed to enter the passphrase. So far, I’ve had no luck setting up Gpg4Win (Kleopatra?) and gpg-agent so that my local pinentry program is used to display the passphrase prompt.
What to do if gpg agent is not running?
To workaround this you can put gpgconf –create-socketdir in the startup script of your shell e.g. ~/.bashrc or ~/.zshrc. Remote gpg will try to start gpg-agent if it’s not running. Remote gpg-agent which will delete your forwarded socket and set up it’s own.
Is there a way to connect to gpgtunnel with GnuPG?
With StreamLocalBindUnlink yes you can connect with ssh gpgtunnel and just use GnuPG as usual. Note: On Systems where systemd controls the directories under /var/run/user/ it may be that the socket forwarding fails because /var/run/user/ /gnupg is deleted on logout.
How to configure an extra socket in GnuPG?
For really old versions of GnuPG (< 2.1.17) you need to edit your gpg-agent.conf to configure an extra socket. The extra socket is more restricted then the normal socket and Pinentry messages will differ when gpg-agent is accessed over this socket: Replace with your actual username.
Is the ssh agent forwarding for WSL2 working?
Furthermore I tested now also with SSH Auth but that does not work either. Then the my SSH key is not found an ssh-add -l (inside the container) says Could not open a connection to your authentication agent. But inside the WSL 2 distro it works also using SSH. (ssh-agent is running on the WSL2 distro).