mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Nir Lichtman" <nir@lichtman.org>,
	syzbot+03e1af5c332f7e0eb84b@syzkaller.appspotmail.com,
	"Tycho Andersen" <tandersen@netflix.com>,
	"Vegard Nossum" <vegard.nossum@oracle.com>,
	"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Subject: Re: [GIT PULL] execve updates for v6.13-rc1
Date: Wed, 20 Nov 2024 18:29:44 -0800	[thread overview]
Message-ID: <BD9581DF-19D1-4A22-BE03-65E383C8A3D3@kernel.org> (raw)
In-Reply-To: <CAHk-=wifNC+AAGVDN-B1gGNhKGqhnkoqWKCknAo6107oD0zGWA@mail.gmail.com>



On November 20, 2024 6:23:55 PM PST, Linus Torvalds <torvalds@linux-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

  reply	other threads:[~2024-11-21  2:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 17:00 Kees Cook
2024-11-20 22:32 ` Linus Torvalds
2024-11-20 22:33   ` Linus Torvalds
2024-11-20 22:50     ` Linus Torvalds
2024-11-21  2:36       ` Al Viro
2024-11-21  2:41         ` Al Viro
2024-11-21  2:51         ` Linus Torvalds
2024-11-21  0:54   ` Eric W. Biederman
2024-11-21  2:23     ` Linus Torvalds
2024-11-21  2:29       ` Kees Cook [this message]
2024-11-21  2:45       ` Linus Torvalds
2024-11-21 17:22       ` Zbigniew Jędrzejewski-Szmek
2024-11-21 17:28         ` Linus Torvalds
2024-11-21 17:47           ` Linus Torvalds
2024-11-21 18:00           ` Zbigniew Jędrzejewski-Szmek
2024-11-21 18:02             ` Linus Torvalds
2024-11-21 18:47               ` Zbigniew Jędrzejewski-Szmek
2024-11-21 18:50               ` Kees Cook
2024-11-21 19:23                 ` Linus Torvalds
2024-11-21 21:31                   ` Zbigniew Jędrzejewski-Szmek
2024-11-21 21:48                     ` Linus Torvalds
2024-11-21 22:24                       ` Zbigniew Jędrzejewski-Szmek
2024-11-21 22:06                   ` Kees Cook
2024-11-21 22:38                     ` Linus Torvalds
     [not found]         ` <87zflrsw1c.fsf@email.froward.int.ebiederm.org>
2024-11-22  7:47           ` Zbigniew Jędrzejewski-Szmek
2024-11-22 10:21             ` Harald Arnesen
     [not found]             ` <87frnjqqh6.fsf@email.froward.int.ebiederm.org>
2024-11-24 15:21               ` Zbigniew Jędrzejewski-Szmek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BD9581DF-19D1-4A22-BE03-65E383C8A3D3@kernel.org \
    --to=kees@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dan.carpenter@linaro.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir@lichtman.org \
    --cc=syzbot+03e1af5c332f7e0eb84b@syzkaller.appspotmail.com \
    --cc=tandersen@netflix.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vegard.nossum@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zbyszek@in.waw.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®