From de193ee3635ae199a62f7a54322b4ef84c83eb10 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Vorburger=20=E2=9B=91=EF=B8=8F?= Date: Mon, 16 Sep 2019 23:59:50 +0200 Subject: [PATCH 1/2] clarify that SSH_AUTH_SOCK should only be set locally, not on the remote server --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 00da18a..4b6958c 100644 --- a/README.md +++ b/README.md @@ -1592,7 +1592,7 @@ export SSH_AUTH_SOCK="/run/user/$UID/gnupg/S.gpg-agent.ssh" gpg-connect-agent updatestartuptty /bye > /dev/null ``` -On some systems, you may need to use the following instead: +On modern systems, you can use the following instead, as `gpgconf --list-dirs agent-ssh-socket` will automatically set `SSH_AUTH_SOCK` to the correct value; and is therefore typically better than hard-coding to `run/user/$UID/gnupg/S.gpg-agent.ssh`, if available: ```console export GPG_TTY="$(tty)" @@ -1600,6 +1600,9 @@ export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket) gpgconf --launch gpg-agent ``` +Note that `SSH_AUTH_SOCK` normally only needs to be set on the *local* laptop (workstation), where the YubiKey is plugged in. On the *remote* server that we SSH into, `ssh` will automatically set `SSH_AUTH_SOCK` to something like `/tmp/ssh-mXzCzYT2Np/agent.7541` when we connect. We therefore do **NOT** manually set `SSH_AUTH_SOCK` on the server. (Doing so would break [SSH Agent Forwarding](#remote-machines-agent-forwarding).) + + ## Copy public key **Note** It is *not* necessary to import the corresponding GPG public key in order to use SSH. @@ -1848,7 +1851,9 @@ RemoteForward /tmp/S.weasel-pageant #### Remote host configuration -Add the following to the shell rc file: +You may have to add the following to the shell rc file (on Linux, this is only required on the laptop/workstation +where the YubiKey is plugged in, and **NOT** on the remote host server that you connect to; in fact at least on +some Linux distributions, changing SSH_AUTH_SOCK on the server breaks agent forwarding): ``` export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket) From 42065a3b658feee4be5b96ee6e047a50e3f0fc3f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Vorburger=20=E2=9B=91=EF=B8=8F?= Date: Tue, 17 Sep 2019 20:12:16 +0200 Subject: [PATCH 2/2] put additional information into single line --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index 4b6958c..d2345d7 100644 --- a/README.md +++ b/README.md @@ -1851,9 +1851,7 @@ RemoteForward /tmp/S.weasel-pageant #### Remote host configuration -You may have to add the following to the shell rc file (on Linux, this is only required on the laptop/workstation -where the YubiKey is plugged in, and **NOT** on the remote host server that you connect to; in fact at least on -some Linux distributions, changing SSH_AUTH_SOCK on the server breaks agent forwarding): +You may have to add the following to the shell rc file: _(On Linux, this is only required on the laptop/workstation where the YubiKey is plugged in, and **NOT** on the remote host server that you connect to; in fact at least on some Linux distributions, changing SSH_AUTH_SOCK on the server breaks agent forwarding.)_ ``` export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)