From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: 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: Wed, 04 May 2016 14:21:33 -0400 [thread overview]
Message-ID: <1462386093.14310.93.camel@HansenPartnership.com> (raw)
In-Reply-To: <1462385876.14310.90.camel@HansenPartnership.com>
On Wed, 2016-05-04 at 14:17 -0400, James Bottomley wrote:
> > Certainly it has been that way for quite a while now.
>
> I don't quite get this. If setgroups is set to deny and I have a set
> of group mappings, I still can't get rid of the negative acl group.
> I can map it to a different gid inside my container, or I can not
> map it at all, but in either case I still can't get access to
> anything with the negative acl group marker because the group
> permission checks occurs with the kguid_t set which includes my
> mapped or unmapped group. The only way I can lose it is to call
> sys_setgroups().
Sorry, this next bit should be at the end of the email (I was playing
and typing at the same time):
> It's a bit ugly because I have to enter the container with --preserve
> -credentials and I can't su to myself if I enter as root (-S 0), I
> have to re-enter as myself instead, but it works.
>
> > Except for the negative acl aspect there are no issues with
> > dropping groups, as setgroups will limit you to the groups allowed
> > in your user namespace.
>
> Well, notwithstanding the merits of negative acls, which I don't want
> to debate because I don't think they're that useful, the use case
> might be that a user possessing a negative acl still wants to use an
> architecture emulation container for building. Installing such a
> container requires being able to set a set of groups and uids
> (required by the installer), but it doesn't require the
> sys_setgroups() system call, so they could reasonably be given the
> ability to set one up with the nosetgroups flag and a range of gids
> allocated in subgid to ensure they still can't get access to
> resources denied by the negative acl group.
It's a bit ugly because I have to enter the container with --preserve
-credentials and I can't su to myself if I enter as root (-S 0), I have
to re-enter as myself instead, but it works.
James
prev parent reply other threads:[~2016-05-04 18:21 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
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 [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=1462386093.14310.93.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--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