[pkg-gnupg-maint] Bug#845565: Bug#853066: gnupg-agent: opens dialog on the wrong computer.

[Charles Plessy]

Control: forcemerge -1 845565

Le Sun, Jan 29, 2017 at 10:35:10PM +0900, Charles Plessy a écrit :
> 
> when I am logged on my desktop computer directly with a GNOME shell
> session, and remotly via SSH, attempts to use gpg from the SSH session
> will open a popup on my desktop computer's screen to enter the
> passphrase, which obviously prevents me from entering the passphrase
> when I am far from the desktopp computer (which is why I connect to it
> via SSH).

> I am not completely sure if it is the same as with #559101, therefore
> I open a new bug.

Hi Daniel and everybody,

I figured out that it is the problem described in #845565 and #842015.

Like in Adam's and Vincent's cases, if I have a graphical session open,
then my passphrase will be asked in this graphical session, even if I ran
gpg in a SSH sesion and I have no physical access to my graphical
sesssion.  This happens regardless of the screen being locked or not, and
setting GPG_TTY or unsetting DBUS_SESSION_BUS_ADDRESS did not help to
solve the problem.

Here are the related packages installed on my system.

    ii  dbus-user-session 1.10.14-1  
    ii  gnupg-agent       2.1.18-3   
    ii  gnupg2            2.1.17-2   
    ii  pinentry-gnome3   1.0.0-1    

I would expect that if I type a command in one shell (SSH or GNOME),
then related dialogs gets prompted in the same shell.  Thus, I do not
understand why pinentry-gnome3 is being used when I am not calling GPG
from a terminal started in the GNOME shell.  To me, it is a big
regression from Jessie, where I was able to SSH to my home computer and
run gpg from my SSH session.

Do you think it might help to put the Debian GNOME maintainers in the
loop ?  Perhaps there is a GNOMEish way to ensure that the GNOME tools
are launched in GNOME context, and text tools are launched in text
context.

Have a nice day,

Charles

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan