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
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Cc: dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Michael Kerrisk (man-pages) <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-12-15 10:17 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-04 15:45 Revised request_key(2) man page for review Michael Kerrisk (man-pages) [not found] ` <528b203d-ac72-e4a6-8517-e8c5c11055a4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2016-11-21 20:59 ` [PATCH 0/5] " Eugene Syromyatnikov 2016-11-21 22:33 ` Michael Kerrisk (man-pages) 2016-11-21 20:59 ` [PATCH 1/5] request_key.2: add information regarding default keyring Eugene Syromyatnikov 2016-11-21 22:08 ` Michael Kerrisk (man-pages) 2016-11-25 10:01 ` Michael Kerrisk (man-pages) [not found] ` <54aa766c-25de-74ba-fba5-59cd95b2ae91-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2016-11-25 20:11 ` Eugene Syromyatnikov 2016-12-13 13:20 ` Michael Kerrisk (man-pages) 2016-12-17 12:21 ` Michael Kerrisk (man-pages) [not found] ` <6df2c812-c2d6-321c-902f-93b4d3aaa953-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2016-12-18 6:40 ` Eugene Syromyatnikov 2016-12-19 8:19 ` David Howells [not found] ` <15546.1482135577-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org> 2016-12-19 8:47 ` Michael Kerrisk (man-pages) [not found] ` <f06829ea-1d7c-3f9a-1f4b-e6880aacbdc2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2016-12-19 9:31 ` Eugene Syromyatnikov 2016-12-20 9:14 ` David Howells 2016-11-21 20:59 ` [PATCH 2/5] requesT_key.2: add information regarding minimal kernel version for key instantiation on request Eugene Syromyatnikov 2016-11-21 22:00 ` Michael Kerrisk (man-pages) 2016-11-21 20:59 ` [PATCH 3/5] request_key.2: whitespace fix Eugene Syromyatnikov 2016-11-21 21:59 ` Michael Kerrisk (man-pages) 2016-11-21 21:00 ` [PATCH 4/5] request_key.2: wfix Eugene Syromyatnikov 2016-11-21 21:59 ` Michael Kerrisk (man-pages) 2016-11-21 21:00 ` [PATCH 5/5] request_key.2: additional error information Eugene Syromyatnikov 2016-11-21 22:00 ` Michael Kerrisk (man-pages) 2016-12-14 14:23 ` Revised request_key(2) man page for review Michael Kerrisk (man-pages) 2016-12-15 10:10 ` David Howells [this message] 2016-12-15 10:10 ` David Howells 2016-12-17 10:34 ` Michael Kerrisk (man-pages) 2016-12-17 10:34 ` Michael Kerrisk (man-pages) 2016-12-19 8:13 ` David Howells 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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.