From: "Serge E. Hallyn" <serge@hallyn.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "W. Trevor King" <wking@tremily.us>,
Linux Containers <containers@lists.linux-foundation.org>,
systemd-devel@lists.freedesktop.org, util-linux@vger.kernel.org
Subject: Re: Unprivileged containers and co-ordinating user namespaces
Date: Fri, 29 Apr 2016 10:53:03 -0500 [thread overview]
Message-ID: <20160429155303.GA8900@mail.hallyn.com> (raw)
In-Reply-To: <1461944328.2311.10.camel@HansenPartnership.com>
Quoting James Bottomley (James.Bottomley@HansenPartnership.com):
> On Thu, 2016-04-28 at 16:00 -0700, W. Trevor King wrote:
> > On Thu, Apr 28, 2016 at 03:02:08PM -0700, James Bottomley wrote:
> > > /etc/usernamespaces
> > >
> > > and the format be :::
> > >
> > > …
> > >
> > > If this sounds OK to people, I can code up a utility that does this,
> > > which should probably belong in util-linux.
> >
> > This sounds a lot like shadow's newuidmap and newgidmap [1,2,3].
> >
> > Cheers,
> > Trevor
> >
> > [1]: https://github.com/shadow-maint/shadow/commit/673c2a6f9aa6c69588f4c1be08589b8d3475a520
> > [2]: http://man7.org/linux/man-pages/man1/newuidmap.1.html
> > [3]: http://man7.org/linux/man-pages/man5/subuid.5.html
>
> I think that mostly works. No-one's packaging it yet, which is why I
https://packages.debian.org/jessie/uidmap
https://launchpad.net/ubuntu/yakkety/+package/uidmap
http://rpm.pbone.net/index.php3/stat/45/idpl/28763248/numer/1/nazwa/newuidmap
> didn't notice. It also looks like the build dependencies have vastly
> expanded, so I can't get it to build in the build service yet.
>
> It looks like the only addition it needs is the setgroups flag for
> newgidmap, which the security people will need, so I can patch that.
> Plus it's trying to install newgidmap/newuidmap as setuid root rather
> than cap_setuid/cap_setgid, but that's fixable in the spec file.
That would prevent it being installed inside user namespaces, until
the user namespaced file capabilities (see separate thread :) hit.
-serge
next prev parent reply other threads:[~2016-04-29 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:02 Unprivileged containers and co-ordinating user namespaces James Bottomley
2016-04-28 23:00 ` W. Trevor King
2016-04-29 15:38 ` James Bottomley
2016-04-29 15:53 ` Serge E. Hallyn [this message]
2016-04-29 18:34 ` W. Trevor King
2016-04-29 21:50 ` Serge E. Hallyn
2016-04-29 22:18 ` James Bottomley
2016-05-01 16:37 ` Serge Hallyn
2016-05-01 23:29 ` James Bottomley
2016-05-02 4:13 ` Serge E. Hallyn
2016-05-04 15:02 ` Eric W. Biederman
2016-05-04 15:21 ` Phil Estes
2016-05-04 18:17 ` James Bottomley
2016-05-04 18:21 ` James Bottomley
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=20160429155303.GA8900@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=containers@lists.linux-foundation.org \
--cc=systemd-devel@lists.freedesktop.org \
--cc=util-linux@vger.kernel.org \
--cc=wking@tremily.us \
/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