summaryrefslogtreecommitdiffstats
path: root/man7/persistent-keyring.7
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
commit3af6d22bb3850ab2bac67287e3a3d3b0e32868e5 (patch)
tree3ee7a3ec64525911fa865bb984c86d997d855527 /man7/persistent-keyring.7
parentAdding debian version 6.05.01-1. (diff)
downloadmanpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.tar.xz
manpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.zip
Merging upstream version 6.7.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'man7/persistent-keyring.7')
-rw-r--r--man7/persistent-keyring.718
1 files changed, 9 insertions, 9 deletions
diff --git a/man7/persistent-keyring.7 b/man7/persistent-keyring.7
index 472782a..0db4940 100644
--- a/man7/persistent-keyring.7
+++ b/man7/persistent-keyring.7
@@ -3,7 +3,7 @@
.\"
.\" SPDX-License-Identifier: GPL-2.0-or-later
.\"
-.TH persistent-keyring 7 2023-02-08 "Linux man-pages 6.05.01"
+.TH persistent-keyring 7 2023-10-31 "Linux man-pages 6.7"
.SH NAME
persistent-keyring \- per-user persistent keyring
.SH DESCRIPTION
@@ -15,7 +15,7 @@ The persistent keyring has a name (description) of the form
where
.I <UID>
is the user ID of the corresponding user.
-.PP
+.P
The persistent keyring may not be accessed directly,
even by processes with the appropriate UID.
.\" FIXME The meaning of the preceding sentence isn't clear. What is meant?
@@ -25,34 +25,34 @@ by virtue of its possessor permits.
This linking is done with the
.BR keyctl_get_persistent (3)
function.
-.PP
+.P
If a persistent keyring does not exist when it is accessed by the
.BR keyctl_get_persistent (3)
operation, it will be automatically created.
-.PP
+.P
Each time the
.BR keyctl_get_persistent (3)
operation is performed,
the persistent keyring's expiration timer is reset to the value in:
-.PP
+.P
.in +4n
.EX
/proc/sys/kernel/keys/persistent_keyring_expiry
.EE
.in
-.PP
+.P
Should the timeout be reached,
the persistent keyring will be removed and
everything it pins can then be garbage collected.
The keyring will then be re-created on a subsequent call to
.BR keyctl_get_persistent (3).
-.PP
+.P
The persistent keyring is not directly searched by
.BR request_key (2);
it is searched only if it is linked into one of the keyrings
that is searched by
.BR request_key (2).
-.PP
+.P
The persistent keyring is independent of
.BR clone (2),
.BR fork (2),
@@ -72,7 +72,7 @@ The persistent keyring can thus be used to
hold authentication tokens for processes that run without user interaction,
such as programs started by
.BR cron (8).
-.PP
+.P
The persistent keyring is used to store UID-specific objects that
themselves have limited lifetimes (e.g., kerberos tokens).
If those tokens cease to be used