From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
James Morris <jmorris@namei.org>,
keyrings <keyrings@linux-nfs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 2/6] KEYS: Reinstate EPERM for a key type name beginning with a '.'
Date: Thu, 11 Sep 2014 22:26:52 +0100 [thread overview]
Message-ID: <11932.1410470812@warthog.procyon.org.uk> (raw)
In-Reply-To: <1410443212.5187.59.camel@dhcp-9-2-203-236.watson.ibm.com>
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> The concept of dot prefixing should probably be documented either in the
> code and/or documentation. At this point, both types and keyring names
> are reserved.
Indeed. There is one type whose name begins with a '.' that's sort of
internal to the kernel (".request_key_auth") that I definitely don't want
userspace to try creating.
The question of whether the description of a non-keyring key is permitted to
begin with a '.' is a separate issue to this patch. We'd have to be sure that
no one is using keys of such a form.
David
next prev parent reply other threads:[~2014-09-11 21:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 21:21 [PATCH 0/6] KEYS: Miscellaneous fixes David Howells
2014-09-10 21:22 ` [PATCH 1/6] KEYS: Fix termination condition in assoc array garbage collection David Howells
2014-09-10 21:22 ` [PATCH 2/6] KEYS: Reinstate EPERM for a key type name beginning with a '.' David Howells
2014-09-10 23:36 ` Mimi Zohar
2014-09-11 11:43 ` Mimi Zohar
2014-09-11 12:09 ` David Howells
2014-09-11 12:27 ` Dmitry Kasatkin
2014-09-11 12:28 ` Dmitry Kasatkin
2014-09-11 13:46 ` Mimi Zohar
2014-09-11 21:26 ` David Howells [this message]
2014-09-10 21:22 ` [PATCH 3/6] KEYS: Fix missing statics David Howells
2014-09-10 21:22 ` [PATCH 4/6] PKCS#7: Add a missing static David Howells
2014-09-10 21:22 ` [PATCH 5/6] PKCS#7: Provide a single place to do signed info block freeing David Howells
2014-09-10 21:22 ` [PATCH 6/6] PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs David Howells
2014-09-15 13:04 ` [PATCH 0/6] KEYS: Miscellaneous fixes David Howells
2014-09-16 2:15 ` James Morris
2014-09-16 9:07 ` 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=11932.1410470812@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.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®