diff options
Diffstat (limited to 'man7/persistent-keyring.7')
| -rw-r--r-- | man7/persistent-keyring.7 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man7/persistent-keyring.7 b/man7/persistent-keyring.7 index e910a3921a..48e219b0cd 100644 --- a/man7/persistent-keyring.7 +++ b/man7/persistent-keyring.7 @@ -21,7 +21,7 @@ The persistent keyring has a name (description) of the form where .I <UID> is the user ID of the corresponding user. - +.PP 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? @@ -31,30 +31,30 @@ by virtue of its possessor permits. This linking is done with the .BR keyctl_get_persistent (3) function. - +.PP 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 Each time the .BR keyctl_get_persistent (3) operation is performed, the persistent key's expiration timer is reset to the value in: - +.PP /proc/sys/kernel/keys/persistent_keyring_expiry - +.PP Should the timeout be reached, the persistent keyring will be removed and everything it pins can then be garbage collected. The key will then be re-created on a subsequent call to .BR keyctl_get_persistent (3). - +.PP 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 The persistent keyring is independent of .BR clone (2), .BR fork (2), @@ -74,7 +74,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 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 |