From: James Morris <james.l.morris@oracle.com>
To: "Mahesh Bandewar (महेश बंडेवार)" <maheshb@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
Kernel-hardening <kernel-hardening@lists.openwall.com>,
Linux API <linux-api@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Serge Hallyn <serge@hallyn.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Mahesh Bandewar <mahesh@bandewar.net>
Subject: Re: [PATCHv3 0/2] capability controlled user-namespaces
Date: Mon, 8 Jan 2018 11:35:26 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1801081131190.8436@localhost> (raw)
In-Reply-To: <CAF2d9jiPYvMN=_guoZHyTA5FmMgaJb5mtxroi5D9NvcNrHc5gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Tue, 2 Jan 2018, Mahesh Bandewar (महेश बंडेवार) wrote:
> On Sat, Dec 30, 2017 at 12:31 AM, James Morris
> <james.l.morris@oracle.com> wrote:
> > On Wed, 27 Dec 2017, Mahesh Bandewar (महेश बंडेवार) wrote:
> >
> >> Hello James,
> >>
> >> Seems like I missed your name to be added into the review of this
> >> patch series. Would you be willing be pull this into the security
> >> tree? Serge Hallyn has already ACKed it.
> >
> > Sure!
> >
> Thank you James.
I'd like to see what Eric Biederman thinks of this.
Also, why do we need the concept of a controlled user-ns at all, if the
default whitelist maintains existing behavior?
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2018-01-08 0:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 22:30 [PATCHv3 0/2] capability controlled user-namespaces Mahesh Bandewar
[not found] ` <20171205223052.12687-1-mahesh-bmGAjcP2qsnk1uMJSBkQmQ@public.gmane.org>
2017-12-27 17:09 ` Mahesh Bandewar (महेश बंडेवार)
2017-12-27 20:23 ` Michael Kerrisk (man-pages)
2017-12-28 0:45 ` Mahesh Bandewar (महेश बंडेवार)
[not found] ` <CAF2d9jjCJxu+oiCCSa1zN8OxfdiCMQb4dx7Mc0YdNgJuMNkOzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-30 8:50 ` Michael Kerrisk (man-pages)
2018-01-03 1:35 ` Mahesh Bandewar (महेश बंडेवार)
2017-12-30 8:31 ` James Morris
2018-01-03 1:30 ` Mahesh Bandewar (महेश बंडेवार)
2018-01-08 0:35 ` James Morris [this message]
2018-01-08 6:24 ` Serge E. Hallyn
2018-01-08 9:51 ` James Morris
2018-01-08 15:47 ` Serge E. Hallyn
2018-01-08 17:21 ` Mahesh Bandewar (महेश बंडेवार)
[not found] ` <CAF2d9jgVJpuAH+jgK0v7sQ9Pr75xy=GSnqKDdpeE7d97O0EbcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-08 18:11 ` Serge E. Hallyn
2018-01-08 18:24 ` Mahesh Bandewar (महेश बंडेवार)
2018-01-08 18:36 ` Serge E. Hallyn
2018-01-08 18:55 ` Mahesh Bandewar (महेश बंडेवार)
2018-01-09 22:28 ` Serge E. Hallyn
[not found] ` <20180109222859.GA25956-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2018-01-10 2:08 ` Mahesh Bandewar (महेश बंडेवार)
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=alpine.LFD.2.20.1801081131190.8436@localhost \
--to=james.l.morris@oracle.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).