pinentry fails with gpg-agent for ssh, but works for gpg

[Werner Koch]

On Thu, 25 Jan 2018 09:39, guru at unixarea.de said:

> $ ssh some-host
>
> fails to ask for the PIN.

That is because ssh has no mechanism to tell the ssh-agent (in this case
gpg-agent) the DISPLAY or tty to use for pinentry.  This the pinentry
pops up on the tty or X server gpg-agent was initially started.

Running

  gpg-connect-agent updatestartuptty /bye

on your current tty tells gpg-agent to updates its default tty and
DISPLAY to the one where you run gpg-connect-agent.  ssh will then work
again.  After you switch back to another terminal you need to do the
same.  

I have to use it always when I move from my standalone laptop to the
Xserver connected to that laptop.  It is a bit annoying and the only
clean solution would be to enance the the ssh-agent protocol and
implement that in both, ssh and gpg-agent.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180125/d2bcf456/attachment.sig>