From: David Howells <dhowells@redhat.com>
To: mtk.manpages@gmail.com
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-man <linux-man@vger.kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Revised request_key(2) man page for review
Date: Thu, 15 Dec 2016 10:10:56 +0000 [thread overview]
Message-ID: <23323.1481796656@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAKgNAkiOzLwoLN-Kaa3-jHUJuYxp-YcL-5FbCe-pOkxGq_u5-g@mail.gmail.com>
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).
> > # echo 'create user mtk:* * /bin/keyctl instantiate %k %c %S' \
> > > /etc/request-keys.conf
There's a /etc/request-keys.d/ directory now.
David
next prev parent reply other threads:[~2016-12-15 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 15:45 Michael Kerrisk (man-pages)
2016-12-14 14:23 ` Michael Kerrisk (man-pages)
2016-12-15 10:10 ` David Howells [this message]
2016-12-17 10:34 ` Michael Kerrisk (man-pages)
2016-12-19 8:13 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23323.1481796656@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=evgsyr@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®