From: "Serge E. Hallyn" <serue@us.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Kerrisk <mtk-manpages@gmx.net>,
"Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Kirill Korotaev <dev@openvz.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Andrey Savochkin <saw@sw.ru>, Adrian Bunk <bunk@stusta.de>,
Cedric Le Goater <clg@fr.ibm.com>,
Chris Wright <chrisw@sous-sol.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>, Andrew Morgan <agm@google.com>
Subject: Re: CLONE_NEWUSER documentation
Date: Mon, 6 Aug 2007 08:09:04 -0500 [thread overview]
Message-ID: <20070806130904.GC23642@sergelap.austin.ibm.com> (raw)
In-Reply-To: <m1643ukviw.fsf@ebiederm.dsl.xmission.com>
Quoting Eric W. Biederman (ebiederm@xmission.com):
> Michael Kerrisk <mtk-manpages@gmx.net> writes:
>
> > Hello Serge,
> >
> > In 2.6.23-rc, your patch to add support for CLONE_NEWUSER is included. Is
> > there there some for-userland-programmers documentation of this flag
> > somewhere? Would you be able to send some documentation to me (ideally as
> > a patch to the clone.2 man page, but otherwise some plain text will do).
> >
> > If this flag is also supported for unshare(), then could you please send me
> > a patch/text for that too?
>
> Currently this namespace is a work in progress marked with CONFIG_EXPERIMENTAL
> because it is very much still experimental and under development.
>
> There may be other omissions but the one I am most aware of is that
> the in kernel user and group equality comparisons have not become been
> transformed from the form uid1 == uid2 to user_namespace1 == user_namespace2 &&
> uid1 == uid2.
I think the two main omissions are that one, and the fact that there is
no concept of a capability mask or per-namespace/cross-namespace
capabilities. What is implemented is separate accounting for the same
uid in different namespaces.
Until the shortcomings are addressed, depending on one's use case, one
may want to use selinux to control access across user namespaces.
> Until that happens that user namespace remains incomplete and not very
> useful. So the advice to users for now that unless they want to help
> finish this up do not use.
thanks,
-serge
prev parent reply other threads:[~2007-08-06 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 9:35 Michael Kerrisk
2007-08-05 12:36 ` Eric W. Biederman
2007-08-06 6:36 ` Michael Kerrisk
2007-08-06 6:48 ` Eric W. Biederman
2007-08-06 13:09 ` Serge E. Hallyn [this message]
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=20070806130904.GC23642@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=agm@google.com \
--cc=bunk@stusta.de \
--cc=chrisw@sous-sol.org \
--cc=clg@fr.ibm.com \
--cc=dev@openvz.org \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=saw@sw.ru \
--cc=sds@tycho.nsa.gov \
/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®