From: "Serge E. Hallyn" <serge@hallyn.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Serge Hallyn <serge.hallyn@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
Colin Walters <walters@verbum.org>,
Linux Containers <containers@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Seth Forshee <seth.forshee@canonical.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Stephane Graber <stgraber@ubuntu.com>
Subject: Re: Thoughts on tightening up user namespace creation
Date: Tue, 8 Mar 2016 16:41:16 -0600 [thread overview]
Message-ID: <20160308224116.GA17693@mail.hallyn.com> (raw)
In-Reply-To: <CALCETrUx_O7Uiyxjs8H++bAR34dSvWny+HsVzXasCVE9wHFGFA@mail.gmail.com>
Quoting Andy Lutomirski (luto@amacapital.net):
> On Mar 7, 2016 10:06 PM, "Serge E. Hallyn" <serge.hallyn@ubuntu.com> wrote:
> >
> > On Mon, Mar 07, 2016 at 09:15:25PM -0800, Andy Lutomirski wrote:
> > > - Ubuntu requires CAP_SYS_ADMIN
> >
> > No, it does not. It has temporarily re-added a sysctl which can enable
> > that behavior, but it's not set by default. The reason for providing it
> > is not a distrust of user namespaces in general, but because we're enabling
> > some bleeding edge patches which haven't been accepted upstream yet. Once
> > they're accepted upstream I expect that patch to be dropped again, unless
> > it has gone upstream.
> >
> > Debian does afaik still have a version of a patch I'd originally written
> > before user namespaces were upstream which defaulted unprivileged userns
> > cloning to off. Did you mean Debian here?
>
> I meant Ubuntu 14.04, which I tested, possibly poorly.
Weird, 14.04 with the default kernel (3.13.0-79-generic #123-Ubuntu)
doesn't have the sysctl at all.
-serge
next prev parent reply other threads:[~2016-03-08 22:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 5:15 Thoughts on tightening up user namespace creation Andy Lutomirski
2016-03-08 6:06 ` Serge E. Hallyn
2016-03-08 18:31 ` Andy Lutomirski
2016-03-08 22:41 ` Serge E. Hallyn [this message]
2016-03-08 10:05 ` Alexander Larsson
2016-03-08 16:31 ` Eric W. Biederman
2016-03-09 18:14 ` Kees Cook
2016-03-09 18:51 ` Colin Walters
2016-03-09 19:04 ` Austin S. Hemmelgarn
2016-03-09 19:21 ` Serge E. Hallyn
2016-03-09 19:25 ` Kees Cook
2016-03-09 19:07 ` Serge E. Hallyn
2016-03-09 19:12 ` Kees Cook
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=20160308224116.GA17693@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=serge.hallyn@ubuntu.com \
--cc=seth.forshee@canonical.com \
--cc=stgraber@ubuntu.com \
--cc=walters@verbum.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).