[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220201133103.bnqplswevdsdsjfv@wittgenstein>
Date: Tue, 1 Feb 2022 14:31:03 +0100
From: Christian Brauner <brauner@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: Eryu Guan <guan@...u.me>, fstests@...r.kernel.org,
Ariadne Conill <ariadne@...eferenced.org>,
Rich Felker <dalias@...c.org>,
Michael Kerrisk <mtk.manpages@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Eryu Guan <guaneryu@...il.com>
Subject: Re: [PATCH] generic/633: adapt execveat() invocations
On Mon, Jan 31, 2022 at 12:46:27PM -0800, Kees Cook wrote:
> On Mon, Jan 31, 2022 at 06:10:23PM +0100, Christian Brauner wrote:
> > There's a push by Ariadne to enforce that argv[0] cannot be NULL. So far
> > we've allowed this. Fix the execveat() invocations to set argv[0] to the
> > name of the file we're about to execute.
>
> To be clear, these tests are also trying to launch set-id binaries with
> argc == 0, so narrowing the kernel check to only set-id binaries
> wouldn't help here, yes?
Yes, that wouldn't help.
The new approach of mutating argv { NULL } into { "", NULL } is better.
Powered by blists - more mailing lists