From: ebiederm@xmission.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH 2/2] user namespaces: require cap_set{ug}id for CLONE_NEWUSER
Date: Fri, 05 Dec 2008 09:17:09 -0800 [thread overview]
Message-ID: <m1k5aepmne.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20081205164552.GA16788@us.ibm.com> (Serge E. Hallyn's message of "Fri, 5 Dec 2008 10:45:52 -0600")
"Serge E. Hallyn" <serue@us.ibm.com> writes:
>> Personally the user namespace only becomes interesting when we
>> start to be able to move in the other direction and remove the
>> set of capabilities requires to create it.
>>
>> Eric
>
> Agreed. Now the thing is I don't think we need full userns
> support to get there. We just need the targeted capabilities
> and the basic dummy fs support - that is, init_user_ns owns
> all vfsmounts, and anyone not in init_user_ns only gets
> user other access to files under those mounts.
Right.
> Of course complete support for targeted caps will in itself
> be a huge effort :)
>
> So my roadmap is: next address the per-user keyring, then
> the targeted caps.
Sounds good.
I expect this means we will pass through a period where the user
namespace is less useful than it is today. But as it will be on
a much firmer foundation that is fine.
Eric
next prev parent reply other threads:[~2008-12-05 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 19:17 [PATCH 1/2] user namespaces: let user_ns be cloned with fairsched Serge E. Hallyn
2008-12-03 19:17 ` [PATCH 2/2] user namespaces: require cap_set{ug}id for CLONE_NEWUSER Serge E. Hallyn
2008-12-05 16:24 ` Eric W. Biederman
2008-12-05 16:45 ` Serge E. Hallyn
2008-12-05 17:17 ` Eric W. Biederman [this message]
2008-12-05 17:14 ` Eric W. Biederman
2008-12-07 22:47 ` James Morris
2008-12-05 10:07 ` [PATCH 1/2] user namespaces: let user_ns be cloned with fairsched James Morris
2008-12-05 14:44 ` Serge E. Hallyn
2008-12-07 22:46 ` James Morris
2008-12-08 16:04 ` Serge E. Hallyn
2008-12-08 21:15 ` James Morris
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=m1k5aepmne.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=serue@us.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