[PATCH] dirmngr: implement --supervised command (for systemd, etc)

Justus Winter justus at g10code.com
Thu Aug 11 15:21:44 CEST 2016

Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:

> On Wed 2016-08-10 02:45:49 -0400, Justus Winter wrote:
>> I agree with this change.  If I were to implement starting gpg-agent on
>> demand on the Hurd using translator records (think generalized decentral
>> socket activation from the nineties, everything old is new again), I'd
>> also need such an interface.
> cool, i'm glad it's also useful for this use case.

I'm not gonna do that of course, I was merely trying to foster your

Having said that, there are concerns with this kind of feature.  First
of all, this must not change where the log messages go.  What good is it
if they are collected by systemd but are missing in the gnupg log?

Then, how are we going to tell from bug reports that a user is using
some service manager, as opposed to letting gnupg handle its background
servers by itself?

Worse, if users are having trouble with this, how are we going to debug
it, given that we do not use e.g. systemd ourself?

Furthermore, it is not clear what benefits users will have if systemd
manages our services.  And please don't say that the benefit is that
things are continue to work despite the fact that systemd starts to
randomly kill services that are neither managed by it nor are
communicating their with to live via some dbus interface.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: </pipermail/attachments/20160811/7140e46b/attachment.sig>

More information about the Gnupg-devel mailing list