On Wed, 14 May 2025 18:48, Andreas Metzler said: > systemd then the natural way to fix this is to mask the system > user-units as described in /usr/share/doc/gpg-agent/README.Debian
Thanks for the hint. I have never seen that because only looked into
the doc/gnupg2 directory and not into the multitude of other doc
diretcories. The GnuPG README now tells:
If your systems already comes with a systemd enabled GnuPG, you
should thus tell it not to start its own GnuPG daemons by running
the following three commands once:
systemctl --user mask --now gpg-agent.service \
gpg-agent.socket gpg-agent-ssh.socket \
gpg-agent-extra.socket gpg-agent-browser.socket
systemctl --user mask --now dirmngr.socket
systemctl --user mask --now keyboxd.socket
This way all GnuPG components can handle the startup of their
daemons on their own and start the correct version.
Salam-Shalom,
Werner
--
The pioneers of a warless world are the youth that
refuse military service. - A. Einstein
openpgp-digital-signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
