From: Rik van Riel <riel@redhat.com>
To: David Howells <dhowells@redhat.com>,
ksummit-discuss@lists.linuxfoundation.org
Cc: ikent@redhat.com, oleg@redhat.com
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Containerisation, namespaces and keyrings
Date: Fri, 22 Jul 2016 09:29:48 -0400 [thread overview]
Message-ID: <1469194188.30053.79.camel@redhat.com> (raw)
In-Reply-To: <15842.1469185302@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Fri, 2016-07-22 at 12:01 +0100, David Howells wrote:
> I'm not sure this is the right venue for this, but keyrings will need
> to be
> namespaced/containerised at some point.
>
> The problem is that it's an icky problem given that different key
> types really
> want to live in different namespaces, and upcalls may want to done in
> different containers, depending on the key type.
>
> For example, DNS resolver keys - should they be in the network, the
> filesystem
> namespace or neither? Should the upcall be in the current container
> or the
> root container?
>
> Authentication keys, such as used by kafs and AF_RXRPC - should they
> be in the
> filesystem namespace (kafs is an fs), the network namespace (AF_RXRPC
> is a net
> protocol) or the user namespace?
>
> Should crypto keys, such as the asymmetric key type, be in the user
> namespace?
> What about use by module signing? Should key operations in the
> current
> container have access to a blacklist in the root container? Should
> key
> verification in the current container have access to system
> keyrings? The
> TPM?
>
> This might actually be right for a hallway track.
>
While figuring out the answers might be right for a hallway
track, it seems that enough maintainers might run into this
stuff later on that sharing the understanding could be good
for a general session.
There is no need to keep this knowledge obscure, especially
given that the more maintainers understand it, the less likely
it is that future mistakes will get merged.
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-22 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 11:01 David Howells
2016-07-22 13:29 ` Rik van Riel [this message]
2016-07-22 14:51 ` James Bottomley
2016-07-26 13:30 ` Serge E. Hallyn
2016-07-26 13:38 ` Laurent Pinchart
2016-07-26 14:16 ` James Bottomley
2016-07-27 19:47 ` Mimi Zohar
2016-07-30 17:50 ` Eric W. Biederman
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=1469194188.30053.79.camel@redhat.com \
--to=riel@redhat.com \
--cc=dhowells@redhat.com \
--cc=ikent@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=oleg@redhat.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