From: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
To: richard -rw- weinberger
<richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michael Kerrisk-manpages
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Vasily Kulikov <segoon-cxoSlKxDwOJWk0Htik3J/w@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: For review: user_namespaces(7) man page
Date: Mon, 29 Apr 2013 14:45:46 -0500 [thread overview]
Message-ID: <1367264746.18069.186@driftwood> (raw)
In-Reply-To: <CAFLxGvzXkGcR=Wyx8YZKKRACEnNLMA0xQoDfruq7CT1D-FNLnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (from richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org on Mon Apr 29 02:45:45 2013)
On 04/29/2013 02:45:45 AM, richard -rw- weinberger wrote:
> On Thu, Mar 21, 2013 at 4:52 PM, Michael Kerrisk (man-pages)
> <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hi Serge,
> >
> > On Fri, Mar 15, 2013 at 4:38 PM, Serge Hallyn
> <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org> wrote:
> >> Hi,
> >>
> >> you mention that after creating a new user namespace you at first
> have
> >> all capabilities in the new ns. You don't explicitly mention (or I
> >> missed it - I did see the mention of securebits) that if you want
> to
> >> keep those capabilities after doing an exec, you need to first have
> >> something mapped to uid 0 in the userns, and do setuid(0).
> >
> > Good point. I'll add something on that.
> >
> >> You might not want to list manpages from other projects,
> >
> > Actually, not a problem. Many of the pages in my set already do
> this.
> >
> >> but Eric's
> >> shadow patches introduce some good new manpages as well. Those
> aren't yet
> >> accepted upstream, but if/when they are then mention at least of
> >> subuid(5), subgid(5), and newuidmap(1) and newgidmap(1) might be
> good.
> >
> > I'll add those.
> >
> > Cheers,
> >
> > Michael
>
> Can we please also document which capabilities are useless within an
> user namespace?
> E.g. CAP_MKNOD.
> You get this capability but the kernel always checks it against the
> initial userns.
Is there a device namespace?
I vaguely recall OpenVZ implemented moving individual PCI devices into
containers so some large movie company could put one video card in each
container for render farms. There are lots of devices that aren't
_really_ privileged (/dev/zero, /dev/null, /dev/full, /dev/ram) and
more that could be emulated...
(Really this seems like a situation where devtmpfs needs -o newinstance
and a corresponding filtered event netlink feed to pass to udev/mdev.
And that might even have been feasible before Greg decided that
devtmpfs needed to have opinions about uids. Oh well.)
Rob
next prev parent reply other threads:[~2013-04-29 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 6:37 For review: user_namespaces(7) man page Michael Kerrisk (man-pages)
2013-03-15 15:38 ` Serge Hallyn
2013-03-21 15:52 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiMOGtuCyvhSpku65p1ZJ5SfdYcOxxAU+H-mk-76wqOPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 7:45 ` richard -rw- weinberger
[not found] ` <CAFLxGvzXkGcR=Wyx8YZKKRACEnNLMA0xQoDfruq7CT1D-FNLnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 19:45 ` Rob Landley [this message]
2013-04-29 20:35 ` richard -rw- weinberger
2013-05-14 7:54 ` Gao feng
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=1367264746.18069.186@driftwood \
--to=rob-voji6fs/r0vr7s880joybq@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=richard.weinberger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=segoon-cxoSlKxDwOJWk0Htik3J/w@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).