From 2bbcbbcbe8c52b3f6710be246a90bda95b75ab46 Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Tue, 20 May 2025 10:22:40 +0200 Subject: [PATCH] doc: Add a note to READ on how to disable the systemd activation. -- A common problem with a self-build gnupg is that systemd starts another version of a daemon while the self-build gnupg has a different idea on the provided features of those daemons. --- README | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/README b/README index ba80dba0b..e9e317a0d 100644 --- a/README +++ b/README @@ -222,8 +222,18 @@ remote use gpg-agent because the no-autostart feature on the remote site will not work as expected. - Thus the recommendation is not to use the --supervised option. All - GnuPG components handle the startup of their daemons on their own. + 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. The only problem is that for using GnuPG's ssh-agent protocol support, the gpg-agent must have been started before ssh. This can