[pkg-gnupg-maint] Bug#850982: Bug#850982: closed by Daniel Kahn Gillmor <dkg at fifthhorseman.net> (Bug#850982: fixed in gnupg2 2.1.17-6)

[Daniel Kahn Gillmor]

On Sat 2017-01-28 11:48:05 -0500, Yuri D'Elia wrote:
> On Wed, Jan 18 2017, Debian Bug Tracking System wrote:
>> Their explanation is attached below along with your original report.
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then please contact Daniel Kahn Gillmor <dkg at fifthhorseman.net> by
>> replying to this email.
>
> I'm not completely satisfied, unfortunately.
> I'd like to disable this service for *all* users by default on servers.
>
> It seems there's no systemctl command for this.

Sure there is, you can use --global to affect user services for all
users.  This creates the symlinks in /etc/systemd/user.

> You can mask the service by creating links in /etc/systemd/user/, but
> then each user session generates the following warning:
>
>   gpg-agent.socket: Cannot add dependency job, ignoring: Unit gpg-agent.socket is masked.

Yes, that's true.  I'm not sure i understand your concern though, or why
you want these things masked.  Can you explain what you're aiming to
avoid?

If the user doesn't try to use the agent, no gpg-agent will be launched.
If the user tries to use the agent from gpg or related tools anyway,
then the agent will be auto-launched (by gpg!) even if you've disabled
the systemd socket.  What's the harm in leaving the sockets enabled?

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170203/02d35878/attachment.sig>