security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-05-24 16:43:28 +02:00
Code Activity

doc: Add a note to READ on how to disable the systemd activation.

Browse Source 
--

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.
This commit is contained in:
Werner Koch 2025-05-20 10:22:40 +02:00
parent eb9c39ac5b
commit 2bbcbbcbe8
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README
View File

@ -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