[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BD9581DF-19D1-4A22-BE03-65E383C8A3D3@kernel.org>
Date: Wed, 20 Nov 2024 18:29:44 -0800
From: Kees Cook <kees@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>
CC: linux-kernel@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Dan Carpenter <dan.carpenter@...aro.org>, Nir Lichtman <nir@...htman.org>,
syzbot+03e1af5c332f7e0eb84b@...kaller.appspotmail.com,
Tycho Andersen <tandersen@...flix.com>,
Vegard Nossum <vegard.nossum@...cle.com>,
Zbigniew Jędrzejewski-Szmek <zbyszek@...waw.pl>
Subject: Re: [GIT PULL] execve updates for v6.13-rc1
On November 20, 2024 6:23:55 PM PST, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>But we're *not* adding a new complete garbage "copy random stuff badly
>from user space" thing.
I'll drop this and resend the PR.
I think using the dentry should work, as you say. Though with a more paranoid hat on, I wonder if it could be an info leak if the original filename isn't "visible" in the context it's running in; containers do weird stuff. (But I'm hard-pressed to imagine how the filename would actually be a useful "secret".)
-Kees
--
Kees Cook
Powered by blists - more mailing lists