From: "Serge E. Hallyn" <serge@hallyn.com>
To: Bastian Blank <bastian@waldi.eu.org>,
containers@lists.linux-foundation.org,
kernel list <linux-kernel@vger.kernel.org>,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 4/7] allow killing tasks in your own or child userns
Date: Sat, 15 Jan 2011 00:31:14 +0000 [thread overview]
Message-ID: <20110115003114.GA24569@mail.hallyn.com> (raw)
In-Reply-To: <20110114145001.GB20945@wavehammer.waldi.eu.org>
Quoting Bastian Blank (bastian@waldi.eu.org):
> On Tue, Jan 11, 2011 at 01:31:52AM +0000, Serge E. Hallyn wrote:
> > Quoting Bastian Blank (bastian@waldi.eu.org):
> > > What is this flag used for anyway? I only see it used in the accounting
> > > stuff, and if every user can get it, it is not longer useful.
> > hm, I'm not sure... maybe noone is using it!
>
> This flag is from pre-git.
>
> The only information is:
> | #define ASU 0x02 /* ... used super-user privileges */
>
> However with your patches (or at least the goal), everyone is super-user
> in derived namespaces.
No, a task just sitting in a derived ns won't necessarily need/use
super-user privileges... (and, if we ever get far enough along, it
won't even necessarily have CAP_SYS_ADMIN/etc targeted to the parent
userns, bc it won't need those to do the unshares).
thanks,
-serge
next prev parent reply other threads:[~2011-01-15 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 21:11 userns: targeted capabilities v3 Serge E. Hallyn
2011-01-10 21:13 ` [PATCH 1/7] Add a user_namespace as creator/owner of uts_namespace Serge E. Hallyn
2011-01-10 21:13 ` [PATCH 2/7] security: Make capabilities relative to the user namespace Serge E. Hallyn
2011-01-10 21:13 ` [PATCH 3/7] allow sethostname in a container Serge E. Hallyn
2011-01-10 21:13 ` [PATCH 4/7] allow killing tasks in your own or child userns Serge E. Hallyn
2011-01-10 21:52 ` Bastian Blank
2011-01-10 22:51 ` Serge Hallyn
2011-01-10 23:23 ` Bastian Blank
2011-01-11 1:31 ` Serge E. Hallyn
2011-01-14 14:50 ` Bastian Blank
2011-01-15 0:31 ` Serge E. Hallyn [this message]
2011-01-15 11:30 ` Bastian Blank
2011-01-15 14:12 ` Serge E. Hallyn
2011-01-11 4:22 ` Oren Laadan
2011-01-11 4:32 ` Serge E. Hallyn
2011-01-10 21:13 ` [PATCH 5/7] Allow ptrace from non-init user namespaces Serge E. Hallyn
2011-01-10 21:14 ` [PATCH 6/7] user namespaces: convert all capable checks in kernel/sys.c Serge E. Hallyn
2011-01-10 21:59 ` Bastian Blank
2011-01-10 22:56 ` Serge Hallyn
2011-01-11 5:27 ` Serge E. Hallyn
2011-01-14 15:02 ` Bastian Blank
2011-01-10 21:14 ` [PATCH 7/7] user namespaces: convert several capable() calls Serge E. Hallyn
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=20110115003114.GA24569@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=bastian@waldi.eu.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).