From: ebiederm@xmission.com (Eric W. Biederman)
To: David Howells <dhowells@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org,
Seth Forshee <seth.forshee@canonical.com>,
Lukasz Pawelczyk <l.pawelczyk@samsung.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [LSF/MM TOPIC] Filesystem namespaces and uid/gid/lsm remapping
Date: Mon, 08 Dec 2014 15:59:12 -0600 [thread overview]
Message-ID: <87ppbtrefj.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <31764.1417802507@warthog.procyon.org.uk> (David Howells's message of "Fri, 05 Dec 2014 18:01:47 +0000")
David Howells <dhowells@redhat.com> writes:
> Andy Lutomirski <luto@amacapital.net> wrote:
>
>> - How should LSM security labels be translated?
>
> I'm definitely interested in that. Especially with respect to how to deal
> with SELinux + overlay{fs,}/unionmount.
>
> Also, I'm interested in how keyrings should interact with namespaces. Should
> keys be namespaced?
Key lookups are already per user namespace, so I would call that
namespaced. We do have the question with keys, should we allow
duplicate key values so that checkpoint/restart can carry keys between
different kernels.
> And I'm also interested in how upcalls, including to /sbin/request-key, should
> be dealt with.
Good question. There is some ongoing discussion on that right now.
Eric
next prev parent reply other threads:[~2014-12-08 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 23:47 [LSF/MM TOPIC] Filesystem namespaces and uid/gid/lsm remapping Andy Lutomirski
2014-12-03 3:37 ` Eric W. Biederman
2015-02-22 17:12 ` [Lsf-pc] " James Bottomley
2015-02-23 12:38 ` Jan Kara
2014-12-03 14:48 ` Seth Forshee
2014-12-05 18:01 ` David Howells
2014-12-08 21:59 ` Eric W. Biederman [this message]
2014-12-09 18:51 ` [Lsf-pc] " Jeff Layton
2015-02-22 16:52 ` James Bottomley
2015-02-22 23:51 ` Jeff Layton
2015-02-22 17:01 ` James Bottomley
2015-02-23 15:54 ` Andy Lutomirski
2015-02-23 16:16 ` James Bottomley
2015-03-02 22:34 ` Andy Lutomirski
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=87ppbtrefj.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=dhowells@redhat.com \
--cc=l.pawelczyk@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=luto@amacapital.net \
--cc=richard@nod.at \
--cc=seth.forshee@canonical.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 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.