Gecko [ www.jobworksschool.com ]

Linux jobworks 6.8.0-136-generic #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 x86_64
Apache/2.4.58 (Ubuntu)
Server IP : 10.0.1.5 & Your IP : 216.73.216.61
Domains : Cant Read [ /etc/named.conf ]
User : www-data

Name	Size	Permission	Date
NEWS.Debian.gz	725 B	-rw-r--r--	2026-01-05 22:01
README.Debian	1.5 KB	-rw-r--r--	2024-03-01 08:25
changelog.Debian.gz	6.59 KB	-rw-r--r--	2026-01-05 22:01
copyright	12.33 KB	-rw-r--r--	2024-03-01 08:25

Rename

keyboxd system integration
==========================

Since 2.4.x, gpg and most related processes will auto-launch keyboxd
if needed.  These auto-launched processes will inherit whatever
environment they started from, and they will not terminate
automatically.

systemd
=======

Since 2.4.1, users on machines with systemd will have a keyboxd
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 keyboxd.socket

Doing this means that keyboxd 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 keyboxd.socket
unit.

Manual keyboxd startup and teardown
===================================

Any user who wants to launch keyboxd 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 keyboxd

If keyboxd 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 keyboxd

If you're not using systemd, you may wish to add this command to your
session logout scripts.

-- NIIBE Yutaka <gniibe@fsij.org>, Tue, 22 Aug 2023 13:52:11 +0900