On 2016-11-02 23:52:43 -0400, Daniel Kahn Gillmor wrote: > I think we ought to take the "systemd" meme out of discussion here. I > think it's being used by conflation with "d-bus", and that confusion is > unlikely to be helpful in resolving these issues. [...]
Thanks for the explanations. So, the problem seems to be related to d-bus (which itself may be related to systemd). When I ssh to my machine with sysvinit (for which there are no problems), DBUS_SESSION_BUS_ADDRESS is unset, while when I ssh to my machine with systemd, DBUS_SESSION_BUS_ADDRESS is set to "unix:path=/run/user/1000/bus" (i.e. the same as in the physical X session, so I'm wondering whether this is correct!). When I ssh to my machine where DBUS_SESSION_BUS_ADDRESS is set, if I run "gpg -d file.gpg", it doesn't work. If I unset this environment variable and try again, it still doesn't work, but that's probably because the gpg-agent that is running (due to the previous test) has DBUS_SESSION_BUS_ADDRESS set in its environment. So, if I try again after killing the running gpg-agent, it works, i.e. I can type my passphrase from the curses UI. -- Vincent Lefèvre <vinc...@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)