public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <tcminyard@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
	"Corey Minyard" <cminyard@mvista.com>,
	containers@lists.linux-foundation.org,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Move console redirect to pid namespace
Date: Fri, 15 Feb 2013 08:50:26 -0600	[thread overview]
Message-ID: <511E4B32.3030003@acm.org> (raw)
In-Reply-To: <87d2w29pdo.fsf@xmission.com>

On 02/14/2013 10:23 PM, Eric W. Biederman wrote:
>
>>> With recent changes this is tied to the initial user namespace.  So the
>>> simple solution to this and so many other similiar security problems is
>>> to run your container in a user namespace.
>>>
>>> The permission check currently is capable(CAP_SYS_ADMIN) which requires
>>> the caller to have the CAP_SYS_ADMIN in the initial user namespace.
>> I'm not sure I follow.  Are these changes in k.org, or in another
>> repository someplace?
> In k.org. 3.7 would work. 3.8-rcX would work even better.
>
> root in a user namespace does not have permission to call TIOCCONS.

Ok, that's good enough for me.  I don't have a compelling reason to make 
it work, beyond liking consistency.

Thank you,

-corey

      reply	other threads:[~2013-02-15 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09  2:28 [PATCH] Move console redirect to pid namespace minyard
2013-02-09 18:14 ` Bruno Prémont
2013-02-13 19:08   ` Eric W. Biederman
2013-02-15  2:08     ` Corey Minyard
2013-02-15  4:23       ` Eric W. Biederman
2013-02-15 14:50         ` Corey Minyard [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=511E4B32.3030003@acm.org \
    --to=tcminyard@gmail.com \
    --cc=bonbons@linux-vserver.org \
    --cc=cminyard@mvista.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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