summaryrefslogtreecommitdiffstats
path: root/man7/session-keyring.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/session-keyring.7')
-rw-r--r--man7/session-keyring.718
1 files changed, 9 insertions, 9 deletions
diff --git a/man7/session-keyring.7 b/man7/session-keyring.7
index d8a950f..d67de25 100644
--- a/man7/session-keyring.7
+++ b/man7/session-keyring.7
@@ -3,7 +3,7 @@
.\"
.\" SPDX-License-Identifier: GPL-2.0-or-later
.\"
-.TH session-keyring 7 2023-03-12 "Linux man-pages 6.05.01"
+.TH session-keyring 7 2023-10-31 "Linux man-pages 6.7"
.SH NAME
session-keyring \- session shared process keyring
.SH DESCRIPTION
@@ -18,17 +18,17 @@ may revoke the session keyring on logout.
(In typical configurations, PAM does do this revocation.)
The session keyring has the name (description)
.IR _ses .
-.PP
+.P
A special serial number value,
.BR KEY_SPEC_SESSION_KEYRING ,
is defined that can be used in lieu of the actual serial number of
the calling process's session keyring.
-.PP
+.P
From the
.BR keyctl (1)
utility, '\fB@s\fP' can be used instead of a numeric key ID in
much the same way.
-.PP
+.P
A process's session keyring is inherited across
.BR clone (2),
.BR fork (2),
@@ -40,7 +40,7 @@ is preserved across
even when the executable is set-user-ID or set-group-ID or has capabilities.
The session keyring is destroyed when the last process that
refers to it exits.
-.PP
+.P
If a process doesn't have a session keyring when it is accessed, then,
under certain circumstances, the
.BR user\-session\-keyring (7)
@@ -76,11 +76,11 @@ identical security attributes and must be single threaded.
.BR keyctl (2)
.B KEYCTL_SESSION_TO_PARENT
operation.)
-.PP
+.P
These operations are also exposed through the
.BR keyctl (1)
utility as:
-.PP
+.P
.in +4n
.EX
keyctl session
@@ -88,9 +88,9 @@ keyctl session \- [<prog> <arg1> <arg2> ...]
keyctl session <name> [<prog> <arg1> <arg2> ...]
.EE
.in
-.PP
+.P
and:
-.PP
+.P
.in +4n
.EX
keyctl new_session