GPG agent forward on Debian: setting pinentry mode 'loopback' failed: Forbidden

[Andrew Gallagher]

Hi, Oz.

Does /run/user/1000/gnupg/S.gpg-agent.extra exist on your local machine?
To make it exist I had to add `extra-socket` to my gpg-agent.conf (I'm
on gpg 2.2.12 from vanilla debian):

```
$ cat ~/.gnupg/gpg-agent.conf
enable-ssh-support
extra-socket /run/user/1000/gnupg/S.gpg-agent.extra
```

A.

On 03/11/2020 20:29, Oz Tiram via Gnupg-users wrote:
> ~$ cat .gnupg/gpg.conf 
> use-agent 
> pinentry-mode loopback
> ~$ cat .gnupg/gpg-agent.conf 
> pinentry-program /usr/bin/pinentry
> no-grab
> default-cache-ttl 1800
> enable-ssh-support
> allow-loopback-pinentry
>
> And also:
> 
> Host debian-remote
>     Hostname 192.168.122.72
>     RemoteForward /run/user/1000/gnupg/S.gpg-agent /run/user/1000/gnupg/S.gpg-agent.extra
>     ExitOnForwardFailure yes

-- 
Andrew Gallagher

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20201104/688f2d38/attachment-0001.sig>