On Tue, May 20 2025, Werner Koch via Gnupg-users <gnupg-users@gnupg.org> wrote:
> 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. Should we mask ‘dirmngr.service’ and ‘keyboxd.service’, too? For example, with: #v+ systemctl --user mask --now dirmngr.service systemctl --user mask --now keyboxd.service #v- -- English is not my native/mother language. While I can read and understand English fluently, I have problems expressing my thoughts in it. Please, bear with me. Sincerely, Pyromania. PGP fingerprint = 2B24 291E 0637 4D2E 0D14 9EFC D7B3 10D4 5C9D 5892 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
