1 gpg-agent system integration
2 ============================
4 Since 2.1.x, gpg and most related processes will auto-launch gpg-agent
5 if needed. These auto-launched processes will inherit whatever
6 environment they started from, and they will not terminate
12 Users on machines with systemd can ensure that gpg-agent is always
13 available for their session, and that it gets terminated safely at
16 systemctl --user enable gpg-agent.socket
18 If you also want the ssh or extra (restricted) sockets to be
19 available, you might also add:
21 systemctl --user enable gpg-agent-ssh.socket
22 systemctl --user enable gpg-agent-extra.socket
24 If you do this from the middle of a running session, you probably also
25 want to clean up any other running gpg-agent, and ensure that the
26 socket is open and listening is started for the current session as
29 gpgconf --kill gpg-agent
30 systemctl --user start gpg-agent.socket
32 Manual gpg-agent startup
33 ========================
35 Any user who wants to launch gpg-agent manually (e.g., to talk to it
36 with a tool from outside the GnuPG suite) should do so with:
38 gpgconf --launch gpg-agent
40 You may wish to add this to your session login scripts if you're not
46 If gpg-agent is launched manually or automatically (but not supervised
47 by systemd), you probably want to ensure that it terminates when your
50 gpgconf --kill gpg-agent
52 You may wish to add this to your session logout scripts if you're not
55 -- Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Mon, 17 Oct 2016 17:06:22 -0400