From: "W. Trevor King" <wking@tremily.us>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
util-linux@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: Re: Unprivileged containers and co-ordinating user namespaces
Date: Thu, 28 Apr 2016 16:00:46 -0700 [thread overview]
Message-ID: <20160428230045.GS22888@odin.tremily.us> (raw)
In-Reply-To: <1461880928.2307.48.camel@HansenPartnership.com>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Thu, Apr 28, 2016 at 03:02:08PM -0700, James Bottomley wrote:
> /etc/usernamespaces
>
> and the format be <user>:<start>:<length>:<flags>
>
> …
>
> 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
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-28 23:08 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 [this message]
2016-04-29 15:38 ` James Bottomley
2016-04-29 15:53 ` Serge E. Hallyn
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=20160428230045.GS22888@odin.tremily.us \
--to=wking@tremily.us \
--cc=James.Bottomley@HansenPartnership.com \
--cc=containers@lists.linux-foundation.org \
--cc=systemd-devel@lists.freedesktop.org \
--cc=util-linux@vger.kernel.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