--- man2/keyctl.2 | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/man2/keyctl.2 b/man2/keyctl.2 index 4ce87dcf31af..0c27aaa44d7f 100644 --- a/man2/keyctl.2 +++ b/man2/keyctl.2 @@ -729,7 +729,7 @@ including the terminating null byte), and (cast as .IR char\~* ) contains the description of the key -(a null-terminated character string up to 4096 bytes in size, +(a null-terminated character string up to 4Ki bytes in size, including the terminating null byte). .IP The source keyring must grant @@ -1742,7 +1742,7 @@ was .B KEYCTL_SEARCH and the size of the description in .I arg4 -(including the terminating null byte) exceeded 4096 bytes. +(including the terminating null byte) exceeded 4Ki bytes. .TP .B EINVAL size of the string (including the terminating null byte) specified in @@ -1751,7 +1751,7 @@ size of the string (including the terminating null byte) specified in or .I arg4 (the key description) -exceeded the limit (32 bytes and 4096 bytes respectively). +exceeded the limit (32 bytes and 4Ki bytes respectively). .TP .BR EINVAL " (before Linux 4.12)" .I operation @@ -1822,7 +1822,7 @@ was .B KEYCTL_DH_COMPUTE and the buffer length exceeds .B KEYCTL_KDF_MAX_OUTPUT_LEN -(which is 1024 currently) +(which is 1Ki currently) or the .I otherinfolen field of the @@ -2047,7 +2047,7 @@ and the description of the authorization key, where we can see that the name of the authorization key matches the ID of the key that is to be instantiated -.RI ( 20d035bf ). +.RI ( 20d0\[aq]35bf ). .PP The example program in .BR request_key (2) @@ -2056,12 +2056,12 @@ specified the destination keyring as By examining the contents of .IR /proc/keys , we can see that this was translated to the ID of the destination keyring -.RI ( 0256e6a6 ) +.RI ( 0256\[aq]e6a6 ) shown in the log output above; we can also see the newly created key with the name .I mykey and ID -.IR 20d035bf . +.IR 20d0\[aq]35bf . .PP .in +4n .EX -- 2.39.0
