mirror of https://github.com/mkerrisk/man-pages
request_key.2: srcfix: FIXME tidyup
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
f3ff1d07b4
commit
a2333608a4
|
@ -42,7 +42,8 @@ attached to the calling process.
|
|||
The keyrings are searched in the order: thread-specific keyring,
|
||||
process-specific keyring, and then session keyring.
|
||||
.P
|
||||
.\" FIXME: The following paragraph could be clearer
|
||||
.\" FIXME: The following paragraph could be clearer. What precisely is
|
||||
.\" the scenario here?
|
||||
If
|
||||
.BR request_key ()
|
||||
is called from a program invoked by
|
||||
|
@ -223,8 +224,9 @@ and a temporary negative key will be installed in the keyring specified by
|
|||
.\" as specified by KEYCTL_SET_REQKEY_KEYRING.
|
||||
This will expire after a few seconds, but will cause subsequent calls to
|
||||
.BR request_key ()
|
||||
.\" FIXME Need an explanation here of why this is done.
|
||||
to fail until it does.
|
||||
.\" FIXME Need an explanation above of why we want to use a temporary
|
||||
.\" negative key to cause subsequent calls to request_key() to fail.
|
||||
|
||||
If a key is created, then\(emregardless of whether it is a valid key or
|
||||
a negative key\(emit will displace any other key with
|
||||
|
|
Loading…
Reference in New Issue