From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com,
keyrings@linux-nfs.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: RFC: 'ioctl' for keyrings
Date: Thu, 13 Mar 2014 16:17:39 +0000 [thread overview]
Message-ID: <22093.1394727459@warthog.procyon.org.uk> (raw)
In-Reply-To: <21625.1394725646@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> I can fix this in one of a number of ways:
>
> (1) Provide a generic control operation (analogous with ioctl()) that allows
> the user to make some general operation on a key (querying it, altering
> it, interacting with hardware).
>
> (2) Provide an alter operation that only allows the key to be altered.
> Looking at trusted_update(), though, I have a suspicion that this may not
> be sufficient as that also seems to invoke an interaction with the TPM.
>
> (3) Provide separate, specific keyctl functions for the special operations
> required by encrypted and trusted keys (and other key types potentially)
> that are then validated in the core and routed to the key type.
(4) Simply make key_update() look for the encrypted and trusted key types
and call a special key type op for those. The main ->update op will be
taking preparsed data and would no longer be callable in this situation.
David
next prev parent reply other threads:[~2014-03-13 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:47 David Howells
2014-03-13 16:17 ` David Howells [this message]
2014-03-13 16:40 ` Mimi Zohar
2014-03-13 16:57 ` Mimi Zohar
2014-03-14 17:14 ` David Howells
2014-03-14 17:53 ` Mimi Zohar
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=22093.1394727459@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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®