lkml.org 
[lkml]   [2016]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Revised request_key(2) man page for review
From
Date
Hello David,

On 12/15/2016 11:10 AM, David Howells wrote:
> Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
>
>>> │Is 'keyring' allowed to be 0? Reading the source, it │
>>> │appears so. In this case, by default, the key is │
>>> │assigned to the session keyring. But, the │
>>> │KEYCTL_SET_REQKEY_KEYRING also seems to have an │
>>> │influence here. What are the details here? │
>
> Yes, the destination keyring can be 0. If you don't specify a destination
> keyring, then:
>
> (1) If the key is found to already exist, the serial number is returned, but
> no extra link is made.
>
> (2) If an error occurs other than "this key doesn't exist", then you'll just
> get the error.
>
> (3) If we have to construct a new key, this will be attached to the default
> keyring (as there's no destination keyring to attach to).

Okay. Please take a look at the revised text that I'll send out
after applying Eugene's patch. (Mail in a few minutes.)

>>> # echo 'create user mtk:* * /bin/keyctl instantiate %k %c %S' \
>>> > /etc/request-keys.conf
>
> There's a /etc/request-keys.d/ directory now.

Yes, I'm aware. Did you mean I should fix something on this page?

Cheers,

Michael


--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

\
 
 \ /
  Last update: 2016-12-17 11:35    [W:0.082 / U:0.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site