Daniel Kahn Gillmor <d...@fifthhorseman.net>, 2017-02-20 15:27 -0500: > On Sun 2017-02-19 21:20:52 -0500, Michael[tm] Smith wrote: > > "Michael[tm] Smith" <m...@w3.org>, 2017-02-20 11:11 +0900: > > > > Can you confirm what the exact command is for globally disabling the > > gpg-agent > > user service? Is it the following? > >... > > systemctl --global mask --now gpg-agent.service gpg-agent.socket > > gpg-agent-ssh.socket gpg-agent-extra.socket gpg-agent-browser.socket > > Yes, look at the per-user command in > /usr/share/doc/gnupg-agent/README.Debian and replace --user with > --global.
OK, thanks > If you're using systemd, i don't think doing this is a good idea, and if > you find problems with managing gpg-agent on a system that you've > configured like this, i'll probably be grumpy about supporting it. > > If you think it's a good idea for some reason, i'd really like to > understand what that reason is so we can fix it. > > You understand that no daemon is launched at all if no process ever > tries to use the agent, right? Yes, but how is that any different from the state my system was in before the change was made in 2.1.17 to have systemd automatically launch gpg-agent? I mean, the way it worked previously caused no observable problems for me. As far I understand it, the way it works without systemd getting involved is that calling gpg2 launches gpg-agent the first time it’s needed, and then it just stays running and everything works fine for me from a user point of view. I observe nothing broken or undesirable in that behavior. —Mike -- Michael[tm] Smith https://sideshowbarker.net/
signature.asc
Description: PGP signature
