From: Andrew Morton <akpm@linux-foundation.org>
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
Pavel Emelianov <xemul@openvz.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Kirill Korotaev <dev@sw.ru>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH -mm 1/2] user namespace : add unshare
Date: Fri, 8 Jun 2007 12:22:15 -0700 [thread overview]
Message-ID: <20070608122215.5da4fa87.akpm@linux-foundation.org> (raw)
In-Reply-To: <4669723F.1040406@fr.ibm.com>
On Fri, 08 Jun 2007 17:14:07 +0200
Cedric Le Goater <clg@fr.ibm.com> wrote:
> Basically, it will allow a process to unshare its user_struct table, resetting
> at the same time its own user_struct and all the associated accounting.
>
> A new root user (uid == 0) is added to the user namespace upon creation. Such
> root users have full privileges and it seems that theses privileges should be
> controlled through some means (process capabilities ?)
This second paragraph is distressingly indecisive. How much thought has
gone into this??
For a start, it seems wrong for the kernel to hardwire knowledge about UID
0 in this fashion.
I'd have thought that a better model for user-namespace unsharing would be
to do a copy-by-value of the entire namespace, then permit a
suitably-privileged application to go through and kill off any unwanted
users from the now-unshared user namespace.
Or maybe just remove that "Insert new root user" altogether? What would
then go wrong?
next prev parent reply other threads:[~2007-06-08 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 15:14 [PATCH -mm 1/2] user namespace : add unshare Cedric Le Goater
2007-06-08 15:22 ` Cedric Le Goater
2007-06-08 19:22 ` Andrew Morton [this message]
2007-06-11 15:33 ` Serge E. Hallyn
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=20070608122215.5da4fa87.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=xemul@openvz.org \
/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