mirror of https://github.com/mkerrisk/man-pages
request_key.2: Minor wording fixes
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
2bcf858070
commit
6dfb4dda6e
|
@ -104,15 +104,16 @@ When the
|
|||
.I dest_keyring
|
||||
is specified to
|
||||
.BR 0 ,
|
||||
and no key construction have been performed, then no additional linking is done.
|
||||
Otherwise, if new key is constructed, it would be linked to the "default"
|
||||
and no key construction have been performed,
|
||||
then no additional linking is done.
|
||||
Otherwise, if a new key is constructed, it will be linked to the "default"
|
||||
keyring (which can be specified via the
|
||||
.BR keyctl (2)
|
||||
command
|
||||
.BR KEYCTL_SET_REQKEY_KEYRING ).
|
||||
More specifically, when kernel tries to determine to which keyring the
|
||||
newly constructed key should be linked, it tries the following options, starting
|
||||
from the value set via
|
||||
More specifically, when the kernel tries to determine to which keyring the
|
||||
newly constructed key should be linked, it tries the following options,
|
||||
starting from the value set via
|
||||
.BR KEYCTL_SET_REQKEY_KEYRING " " keyctl (2)
|
||||
command until it finds the first available one:
|
||||
.IP \(bu 3
|
||||
|
|
Loading…
Reference in New Issue