mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
	"Serge Hallyn" <serge.hallyn@ubuntu.com>,
	"Seth Forshee" <seth.forshee@canonical.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"Stéphane Graber" <stgraber@ubuntu.com>
Subject: Re: user namespace and fully visible proc and sys mounts
Date: Mon, 07 Mar 2016 22:05:50 -0600	[thread overview]
Message-ID: <87bn6p7gwx.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CALCETrXGr8Trd=N62GvgE_gzYEUxxnSBQefuYPnYna0sCWfpMw@mail.gmail.com> (Andy Lutomirski's message of "Mon, 7 Mar 2016 16:24:21 -0800")

Andy Lutomirski <luto@amacapital.net> writes:

> On Mon, Mar 7, 2016 at 4:07 PM, Eric W. Biederman <ebiederm@xmission.com> wrote:
>> Andy Lutomirski <luto@amacapital.net> writes:
>>
>>> On a related note, can we *please* find a way to constrain namespace
>>> creation in a way that might satisfy the RHEL crowd?
>>
>> I am not certain to what you are referrring.
>>
>> As long as folks are willing to work with me I am happy to help design
>> and design something that makes things better for everyone.  If someone
>> pushes hard, suggestes crappy patches, and does not listen to
>> constructive feedback I will shoot their patches down (especially when I
>> am sick and tired as I have been more than I would like this development
>> cycle).
>
> I think we should add some mechanism that will allow the right to
> create various namespaces to be constrained in a useful and usable
> manner.  I'll start a new thread.

On the general principle that there is more attack surface, and attack
surface reduction is generally good I agree.  I will await your follow
on thread when you are ready.

Eric

      reply	other threads:[~2016-03-08  4:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06  8:28 Serge E. Hallyn
2016-03-06 21:53 ` Eric W. Biederman
2016-03-06 23:38   ` Serge E. Hallyn
2016-03-07  2:24   ` Andy Lutomirski
2016-03-07  3:45     ` Serge E. Hallyn
2016-03-07  3:49       ` Andy Lutomirski
2016-03-07  5:03         ` Serge E. Hallyn
2016-03-08  0:07     ` Eric W. Biederman
2016-03-08  0:24       ` Andy Lutomirski
2016-03-08  4:05         ` Eric W. Biederman [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=87bn6p7gwx.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=serge.hallyn@ubuntu.com \
    --cc=serge@hallyn.com \
    --cc=seth.forshee@canonical.com \
    --cc=stgraber@ubuntu.com \
    /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

all inboxes | Powered by JetHome®