From: yumkam@gmail.com (Yuriy M. Kaminskiy)
To: util-linux@vger.kernel.org
Subject: Re: [PATCH] nsenter: fix ability to enter unprivileged containers
Date: Mon, 18 Apr 2016 17:33:12 +0300 [thread overview]
Message-ID: <m3ega3kmvr.fsf@gmail.com> (raw)
In-Reply-To: 1460982392.2452.6.camel@HansenPartnership.com
James Bottomley
<James.Bottomley@HansenPartnership.com>
writes:
> If you enter it first, you lose privilege for subsequent namespace
> enters,see issue
>
> https://github.com/karelzak/util-linux/issues/315
>
> The fix is to enter the user namespace last of all.
I verified that with *current*/unpatched nsenter,
$ unshare -rm sleep inf &
$ nsenter -t $! -U -m --preserve
works as expected (from regular user [and with unprivileged userns
enabled]).
With this patch it *won't* work [verified], of course (as you'll need
root privileges in userns before joining mount-ns, and you can only
obtain them by entering userns first).
Of course, you can workaround it by invoking nsenter twice:
$ nsenter -t $! -U --preserve nsenter -t $! -m
but same could be said about issue 315: you can workaround it by
manually splitting entering mount-ns and user-ns, something like
# nsenter --mount=/run/build-container/aarch64 nsenter --user=/run/build-container/user
or (if /run/build-container/user is not visible inside mount-ns)
# nsenter --mount=/run/build-container/aarch64 nsenter --user=/dev/fd/3 3</run/build-container/user
(disclaimer: unverified; on my kernel mount-bind fails for mount-ns fds).
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>
> diff --git a/sys-utils/nsenter.c b/sys-utils/nsenter.c
> index d8690db..1525f15 100644
> --- a/sys-utils/nsenter.c
> +++ b/sys-utils/nsenter.c
> @@ -52,13 +52,13 @@ static struct namespace_file {
> * first. This gives an unprivileged user the potential to
> * enter the other namespaces.
> */
> - { .nstype = CLONE_NEWUSER, .name = "ns/user", .fd = -1 },
> { .nstype = CLONE_NEWCGROUP,.name = "ns/cgroup", .fd = -1 },
> { .nstype = CLONE_NEWIPC, .name = "ns/ipc", .fd = -1 },
> { .nstype = CLONE_NEWUTS, .name = "ns/uts", .fd = -1 },
> { .nstype = CLONE_NEWNET, .name = "ns/net", .fd = -1 },
> { .nstype = CLONE_NEWPID, .name = "ns/pid", .fd = -1 },
> { .nstype = CLONE_NEWNS, .name = "ns/mnt", .fd = -1 },
> + { .nstype = CLONE_NEWUSER, .name = "ns/user", .fd = -1 },
> { .nstype = 0, .name = NULL, .fd = -1 }
> };
next prev parent reply other threads:[~2016-04-18 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 12:26 [PATCH] nsenter: fix ability to enter unprivileged containers James Bottomley
2016-04-18 14:33 ` Yuriy M. Kaminskiy [this message]
2016-04-18 15:51 ` Yuriy M. Kaminskiy
2016-04-18 15:37 ` James Bottomley
2016-04-18 15:50 ` James Bottomley
2016-04-18 17:11 ` Karel Zak
2016-04-18 17:28 ` James Bottomley
2016-04-18 18:26 ` Eric W. Biederman
2016-04-18 20:56 ` James Bottomley
2016-04-18 21:31 ` Eric W. Biederman
2016-04-22 9:05 ` Karel Zak
2016-04-18 19:40 ` 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=m3ega3kmvr.fsf@gmail.com \
--to=yumkam@gmail.com \
--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