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

add_key.2: srcfix: Update FIXMEs 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-12-17 14:26:53 +01:00
parent 5834768eaf
commit 0978f70669
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
man2/add_key.2
View File

@ -47,15 +47,16 @@ already contains a key that matches the specified
and
.IR description ,
then, if the key type supports it,
.\" FIXME Which key types support this?
.\" FIXME The aforementioned phrases begs the question:
.\" which key types support this?
that key will be updated rather than a new key being created;
if not, a new key (with a different ID) will be created
and it will displace the link to the extant key from the keyring.
.\" FIXME Perhaps elaborate the implications here? Namely, the new
.\" key will have a new ID, and if the old key was a keyring that
.\" is consequently unlinked, then keys that it was anchrorin
.\" will have their refgerence count decreased by one (and ma
.\" consequently be garbage collected).
.\" is consequently unlinked, then keys that it was anchroring
.\" will have their reference count decreased by one (and may
.\" consequently be garbage collected). Is this all correct?
.P
The destination
.I keyring
@ -63,7 +64,7 @@ serial number may be that of a valid keyring for which the caller has
.I write
permission.
Alternatively, it may be one of the following special keyring IDs:
.\" FIXME Perhaps have a separate page describing special keyring IDs?
.\" FIXME . Perhaps have a separate page describing special keyring IDs?
.TP
.B KEY_SPEC_THREAD_KEYRING
This specifies the caller's thread-specific keyring