[pkg-gnupg-maint] Bug#854376: Bug#854376: Unable to use gpg-agent as ssh-agent
Punit Agrawal
punitagrawal at gmail.com
Mon Feb 13 10:26:30 UTC 2017
Hi Daniel,
On Fri, Feb 10, 2017 at 7:37 PM, Daniel Kahn Gillmor
<dkg at fifthhorseman.net> wrote:
> Hi Punit--
>
> On Thu 2017-02-09 07:25:17 -0500, Punit Agrawal wrote:
>> I've got version 2.1.18-3 of the package (I'm running testing)
>
>> % readlink -f $(which pinentry)
>> /usr/bin/pinentry-qt
>
>> sddm
>
>>> * do you have dbus-user-session installed?
>>
>> No.
>
> Thanks for the feedback!
>
> The problem that you're having is because ssh does not tell gpg-agent
> anything about how to contact the user, and gpg-agent is started as a
> service by systemd.
>
> I believe that if you were to install dbus-user-session, fully log out,
> and then log back in again with sddm, gpg-agent would get launched when
> asked with the correct $DISPLAY environment variable, and your ssh
> attempt would just work, without needing to do the updatestartuptty
> dance.
>
> The gnupg-agent package Suggests: dbus-user-session to facilitate
> exactly your use case.
>
> Please let me know if dbus-user-session works for you!
I can confirm that installing dbus-user-session and logging out and
back in fixed the issue. I got asked for the ssh key passphrase and
was able to log in with the key onto a remote machine. :)
I think I found it a bit confusing as I went from a working setup to a
not-working one without me doing anything other than upgrade the
system. Not sure what an be done to ease the transition though.
Thanks a lot for taking the time to dig into the issue and explain
what's going on.
Cheers,
Punit
>
> --dkg
More information about the pkg-gnupg-maint
mailing list