Why exactly does pinentry fails with gpg-agent and ssh support?
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Mon Jan 22 11:34:10 CET 2018
On Mon 2018-01-22 08:43:41 +0100, Werner Koch wrote:
> Another problem with ssh is that ssh can't start gpg-agent on the the
> fly. Thus you need to make sure that gpg-agent has already been started
> when you use ssh. A way to ensure this is to run
>
> gpg -K
the systemd user service takes care of automatically launching the
gpg-agent when the user connects to it via the ssh-agent protocol, so
this isn't required when using systemd.
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180122/10d7ebea/attachment.sig>
More information about the Gnupg-users
mailing list