OXIESEC PANEL
- Current Dir:
/
/
usr
/
share
/
doc
/
dirmngr
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
11/10/2024 09:42:49 AM
rwxr-xr-x
📄
AUTHORS
3.71 KB
11/07/2017 09:05:29 AM
rw-r--r--
📄
KEYSERVER
3.02 KB
08/28/2017 10:22:54 AM
rw-r--r--
📄
NEWS.Debian.gz
847 bytes
01/16/2021 02:47:37 PM
rw-r--r--
📄
NEWS.gz
39.16 KB
12/20/2017 07:27:18 AM
rw-r--r--
📄
README.Debian
1.51 KB
01/16/2021 02:47:37 PM
rw-r--r--
📄
THANKS.gz
6.04 KB
08/28/2017 10:22:54 AM
rw-r--r--
📄
TODO
3.71 KB
08/28/2017 10:22:54 AM
rw-r--r--
📄
changelog.Debian.gz
2.37 KB
07/04/2022 04:20:59 PM
rw-r--r--
📄
copyright
9.57 KB
01/16/2021 02:47:37 PM
rw-r--r--
Editing: README.Debian
Close
dirmngr system integration ========================== Since 2.1.x, gpg and most related processes will auto-launch dirmngr if needed. These auto-launched processes will inherit whatever environment they started from, and they will not terminate automatically. systemd ======= Since 2.1.17, users on machines with systemd will have a dirmngr process launched automatically by systemd's user session, upon first access of the standard socket. systemd will also cleanly tear this process down at session logout. Users who don't want systemd to manage their dirmngr in this way for all future sessions should do: systemctl --user mask --now dirmngr.socket Doing this means that dirmngr will fall back to its manual mode of operation. (This decision can be reversed by the user with "unmask" instead of "mask") See systemctl(1) for more details about managing the dirmngr.socket unit. Manual dirmngr startup and teardown =================================== Any user who wants to launch dirmngr manually (e.g., to talk to it with a tool from outside the GnuPG suite) and is *not* using systemd should first ensure that it is launched with: gpgconf --launch dirmngr If dirmngr is launched manually or automatically (but not supervised by systemd), you also probably want to ensure that it terminates when your session ends with: gpgconf --kill dirmngr If you're not using systemd, you may wish to add this command to your session logout scripts. -- Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Mon, 23 Jan 2017 22:49:45 -0500