summaryrefslogtreecommitdiffstats
path: root/upstream/debian-unstable/man7/user-keyring.7
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-17 10:51:52 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-17 10:51:52 +0000
commit4ad94864781f48b1a4b77f9cfb934622bf756ba1 (patch)
tree3900955c1886e6d2570fea7125ee1f01bafe876d /upstream/debian-unstable/man7/user-keyring.7
parentAdding upstream version 4.22.0. (diff)
downloadmanpages-l10n-4ad94864781f48b1a4b77f9cfb934622bf756ba1.tar.xz
manpages-l10n-4ad94864781f48b1a4b77f9cfb934622bf756ba1.zip
Adding upstream version 4.23.0.upstream/4.23.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'upstream/debian-unstable/man7/user-keyring.7')
-rw-r--r--upstream/debian-unstable/man7/user-keyring.718
1 files changed, 9 insertions, 9 deletions
diff --git a/upstream/debian-unstable/man7/user-keyring.7 b/upstream/debian-unstable/man7/user-keyring.7
index 7468cc50..68f3f48c 100644
--- a/upstream/debian-unstable/man7/user-keyring.7
+++ b/upstream/debian-unstable/man7/user-keyring.7
@@ -3,7 +3,7 @@
.\"
.\" SPDX-License-Identifier: GPL-2.0-or-later
.\"
-.TH user-keyring 7 2023-02-05 "Linux man-pages 6.05.01"
+.TH user-keyring 7 2024-05-02 "Linux man-pages 6.8"
.SH NAME
user-keyring \- per-user keyring
.SH DESCRIPTION
@@ -15,7 +15,7 @@ The user keyring has a name (description) of the form
where
.I <UID>
is the user ID of the corresponding user.
-.PP
+.P
The user keyring is associated with the record that the kernel maintains
for the UID.
It comes into existence upon the first attempt to access either the
@@ -27,28 +27,28 @@ The keyring remains pinned in existence so long as there are processes
running with that real UID or files opened by those processes remain open.
(The keyring can also be pinned indefinitely by linking it
into another keyring.)
-.PP
+.P
Typically, the user keyring is created by
.BR pam_keyinit (8)
when a user logs in.
-.PP
+.P
The user keyring is not searched by default by
.BR request_key (2).
When
.BR pam_keyinit (8)
creates a session keyring, it adds to it a link to the user
keyring so that the user keyring will be searched when the session keyring is.
-.PP
+.P
A special serial number value,
.BR KEY_SPEC_USER_KEYRING ,
is defined that can be used in lieu of the actual serial number of
the calling process's user keyring.
-.PP
+.P
From the
.BR keyctl (1)
utility, '\fB@u\fP' can be used instead of a numeric key ID in
much the same way.
-.PP
+.P
User keyrings are independent of
.BR clone (2),
.BR fork (2),
@@ -58,14 +58,14 @@ and
.BR _exit (2)
excepting that the keyring is destroyed when the UID record is destroyed when
the last process pinning it exits.
-.PP
+.P
If it is necessary for a key associated with a user to exist beyond the UID
record being garbage collected\[em]for example, for use by a
.BR cron (8)
script\[em]then the
.BR persistent\-keyring (7)
should be used instead.
-.PP
+.P
If a user keyring does not exist when it is accessed, it will be created.
.SH SEE ALSO
.ad l