[pkg-gnupg-maint] Bug#842015: Merging bugs about pinentry failing without GNOME-connected d-bus
Vincent Lefevre
vincent at vinc17.net
Sat Nov 5 10:31:39 UTC 2016
Control: reopen 842015
Control: found 842015 0.9.7-7
On 2016-11-04 23:23:43 -0400, Daniel Kahn Gillmor wrote:
> The three bugs above are all caused by a situation where the user wants
> to use secret key material with gpg, while relying on pinentry-gnome3
> with access to a d-bus session, but where that d-bus session has no
> access to an expected GNOME session.
[...]
The problem is still there. Note that I've tried after upgrading then
rebooting the machine to make sure that nothing from old software was
running (in particular, I've noticed that otherwise, gpg-agent is
still running after I log out of all my X / SSH / screen sessions).
Basically:
1. Upgrade and reboot the machine A.
2. Log in with X.
3. Type "gpg -d file.gpg" and cancel at the pinentry-gnome3 prompt.
4. On some other machine, ssh to machine A.
5. In this ssh session, type "gpg -d file.gpg".
Result: A pinentry window is opened on the X display of machine A
and this gpg "freezes".
I confirm that the workaround (unset DBUS_SESSION_BUS_ADDRESS and
kill gpg-agent) still works.
--
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
More information about the pkg-gnupg-maint
mailing list