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

2020-11-04 Thread Oz Tiram via Gnupg-users
Hi Andrew! I solved this issue finally! What a weird UI ... So ..., apparently, it's not enough to tell the gpg-agent which tty needs to be used via GPG_TTY! You also have to do: > I guess something is wrong on the local machine. > export GPG_TTY=$(tty) gpg-connect-agent updatestartuptty /bye >

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

2020-11-04 Thread 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 ```

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

2020-11-03 Thread Oz Tiram via Gnupg-users
Hi, I spend quite sometime trying to set up gpg agent forwarding between two machines (running debian). But I can't get this work with the instructions from the gpg wiki. My ssh config: Host debian-remote Hostname 192.168.122.72 RemoteForward /run/user/1000/gnupg/S.gpg-agent /run/user/100

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

2020-11-03 Thread Oz Tiram via Gnupg-users
Apologies, I accidentally posted the complete SO question in my previous email. That was not my intention. I hope I can still find some answers with the help from subscribers of this list. Best wishes Oz -- --- Imagine there's no countries it isn't hard to do Nothing to kill or die for And no