[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJoqnX54JnHZDVxO4NRCsT6sLH4+-TPk8GqCSVp0mFNLw@mail.gmail.com>
Date: Wed, 13 Feb 2019 16:54:07 -0800
From: Kees Cook <keescook@...omium.org>
To: Samuel Dionne-Riel <samuel@...nne-riel.com>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Graham Christensen <graham@...hamc.com>,
Oleg Nesterov <oleg@...hat.com>,
Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Userspace regression in LTS and stable kernels
On Wed, Feb 13, 2019 at 4:41 PM Samuel Dionne-Riel
<samuel@...nne-riel.com> wrote:
> Before, the interpreter was still used (assuming it wasn't cut by the
> length), and the interpreter was free to re-read the shebang if
> desired.
Oh awesome. Yeah, so, nevermind about the WARN_ONCE().
So, to address the "wrong binary" problem, how about we ENOEXEC only
if no newline or spaces are found in the string?
--
Kees Cook
Powered by blists - more mailing lists