[pkg-gnupg-maint] Beware of leftover gpg-agent processes

Werner Koch wk at gnupg.org
Sat Aug 6 17:44:44 UTC 2016


On Sat,  6 Aug 2016 18:54, dkg at fifthhorseman.net said:

> they're actually needed.  The current arrangement with systemd doesn't
> do that, because the agent itself wants to open the socket, rather than

I see.

> We could have the best of both worlds with socket activation, though,
> and i don't think it'd be that hard.  If you'd be willing to accept

The problem is that this duplicates what gpg et al are already doing.
And they make sure that only one is started.  Adding this
socket-activation would thus be in conflict with what gpg is already
doing.  Well, unless you can tell systemd to run "gpgconf --launch
gpg-agent" after it detects a connect to an unbound socket (in case
socket activation works this way)


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
 /* Join us at OpenPGP.conf  <https://openpgp-conf.org> */




More information about the pkg-gnupg-maint mailing list