gpg-agent forwarding to remote with systemd - status?

[Chris Coutinho]

I should add that the remote is OpenSUSE Leap 15.0 running GnuPG
2.2.5, and my current client is OpenSUSE Leap 15.0 running WSL on
Windows 10, also running GnuPG 2.2.5. The WSL client doesn't have
systemd installed on it, so it uses the old ~/.gnupg directory for
holding sockets.

On client:
$ gpgconf --list-dir socketdir
/home/chris/.gnupg

On remote:
$ gpgconf --list-dir socketdir
/run/user/1001/gnupg

Regards,
Chris

On Fri, 1 Feb 2019 at 11:42, Chris Coutinho <chrisbcoutinho at gmail.com> wrote:
>
> Hi,
>
> I'm trying to forward my local gpg-agent over ssh to a remote that
> controls the gnupg sockets via systemd. This fails because sshd
> attempts to place the socket in a directory that doesn't exist,
> because that is handled on the remote by systemd.
>
> This issue was raised back in 2016:
>
> https://gnupg-users.gnupg.narkive.com/eYVmOa2h/agent-forwarding-failure-when-the-socketdir-was-autodeleted
>
> It was suggested in that thread to place `gpgconf --create-socketdir`
> in '.bashrc' to create the proper directory, but this doesn't work in
> my case because on the remote the directory is created/deleted by
> systemd and shell scripts are sourced after ssh attempts to place the
> socket.
>
> From my limited understanding of the issue, it seems that it wasn't
> clear in what project the solution should be (openssh, systemd,
> gnupg).
>
> Is there an update regarding this issue, or any proposed workarounds
> for systemd-based remotes?
>
> Regards,
> Chris