[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bn89sbc2.fsf@x220.int.ebiederm.org>
Date: Mon, 25 Jan 2016 13:33:49 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Kees Cook <keescook@...omium.org>
Cc: Andy Lutomirski <luto@...capital.net>, Andrew Morton
<akpm@...ux-foundation.org>, Al Viro <viro@...iv.linux.org.uk>, Richard
Weinberger <richard@....at>, Robert Święcki
<robert@...ecki.net>, Dmitry Vyukov <dvyukov@...gle.com>, David Howells
<dhowells@...hat.com>, Miklos Szeredi <mszeredi@...e.cz>, Kostya
Serebryany <kcc@...gle.com>, Alexander Potapenko <glider@...gle.com>,
Eric Dumazet <edumazet@...gle.com>, Sasha Levin
<sasha.levin@...cle.com>, "linux-doc\@vger.kernel.org"
<linux-doc@...r.kernel.org>, "linux-kernel\@vger.kernel.org"
<linux-kernel@...r.kernel.org>, "kernel-hardening\@lists.openwall.com"
<kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled
Kees Cook <keescook@...omium.org> writes:
>
> Well, I don't know about less weird, but it would leave a unneeded
> hole in the permission checks.
To be clear the current patch has my:
Nacked-by: "Eric W. Biederman" <ebiederm@...ssion.com>
The code is buggy, and poorly thought through. Your lack of interest in
fixing the bugs in your patch is distressing.
So broken code, not willing to fix. No. We are not merging this sysctl.
Eric
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
