LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

add_key.2: Various fixes after review by David Howells 

Reported-by: David Howells <dhowells@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-12-13 12:22:20 +01:00
parent eebdcb80a8
commit 1d452eeca3
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
man2/add_key.2
View File

@ -61,7 +61,8 @@ The destination
.I keyring
serial number may be that of a valid keyring for which the caller has
.I write
permission, or it may be one of the following special keyring IDs:
permission.
Alternatively, it may be one of the following special keyring IDs:
.\" FIXME Perhaps have a separate page describing special keyring IDs?
.TP
.B KEY_SPEC_THREAD_KEYRING
@ -99,9 +100,9 @@ are the following:
.I """keyring"""
Keyrings are special key types that may contain links to sequences of other
keys of any type.
If this interface is used to create a keyring, then a NULL
If this interface is used to create a keyring, then
.I payload
should be specified, and
should be NULL and
.I plen
should be zero.
.TP
@ -116,7 +117,7 @@ of up to 32,767 bytes.
.\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
This key type is essentially the same as
.IR """user""" ,
but it does not provide reading.
but it does not permit the key to read.
This is suitable for storing payloads
that you do not want to be readable from user space.
@ -133,8 +134,8 @@ This key type is similar to
.IR """user""" ,
but may hold a payload of up to 1 MiB.
If the key payload is large enough,
then it may be stored in tmpfs (which can be swapped out) rather than kernel
memory.
then it may be stored encrypted in tmpfs
(which can be swapped out) rather than kernel memory.
.PP
For further details on these key types, see
.BR keyrings (7).