[pkg-gnupg-maint] Bug#853905: Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

[Yuri D'Elia]

On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote:
> What are you doing with gpg?  if whatever you're doing needs the secret
> keyring, the agent will be launched.  if it doesn't need the secret
> keyring, the agent will not be launched.

In one instance, I have a couple of gpg --batch processes that are run
via cron to encrypt some files.

There's no secret key available for the recipient, but the agent is
somehow started, and actually gets stale.

Now cron will actually create an user slice for root, meaning that
there's some extra interplay with cron that I'm trying to exclude.

I was assuming the agent wouldn't be started at all, but it still is.

> With gpg-agent as a systemd user service, when the user completely logs
> out of the system, any services launched (socket-activated or otherwise)
> will be stopped automatically.

Extra question, if this would be true for an user with lingering
enabled? Because on servers we have those enabled for all users.

> Yuri, it sounds like you've got a particular scenario that you don't
> like, and you're trying lots of things to change it, but i don't
> understand what the scenario is.

Not fully, no :/

Bug debugging some of these runaway processes is tricky and time
consuming.