linux-kernel - Re: [GIT PULL] execve updates for v6.13-rc1 (take 2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <13223528-74FF-4B68-B0CF-25DCC995D0A0@kernel.org>
Date: Fri, 29 Nov 2024 12:08:21 +1000
From: Kees Cook <kees@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
 Al Viro <viro@...iv.linux.org.uk>
CC: linux-kernel@...r.kernel.org,
 Christophe JAILLET <christophe.jaillet@...adoo.fr>,
 "Eric W. Biederman" <ebiederm@...ssion.com>, Nir Lichtman <nir@...htman.org>,
 Tycho Andersen <tandersen@...flix.com>,
 Vegard Nossum <vegard.nossum@...cle.com>
Subject: Re: [GIT PULL] execve updates for v6.13-rc1 (take 2)

On November 28, 2024 12:24:27 PM GMT+10:00, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>But no, I do not accept changing well-documented behaviour of
>AT_EMPTY_PATH, much less the insanity of making "execveat()" have
>completely different semantics for AT_EMPTY_PATH than a plain openat.

Yeah, that was going to be the next question. ;) Okay, so, that last thing I can see here as an option is to add an exec-specific AT flag, and if that isn't workable I don't see a way to make this happen with execveat.

-Kees

-- 
Kees Cook