linux-kernel - Re: [GIT PULL] arm64 updates 6.15-rc1

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAHk-=wg_HipugbtswxFnekQy2g_ksKKXj+yht8naj2FEMtRMgA@mail.gmail.com>
Date: Tue, 25 Mar 2025 17:48:12 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Will Deacon <will@...nel.org>, linux-arm-kernel@...ts.infradead.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] arm64 updates 6.15-rc1

On Tue, 25 Mar 2025 at 17:18, Catalin Marinas <catalin.marinas@....com> wrote:
>
> Hmm, I thought that setting "Return-Path: cmarinas@...nel.org" would be
> enough.

No, DKIM is designed to make forging emails hard, and that very much
means that it checks the "from" address, not some random header that
humans never look at.

> This header left my machine but seems to have disappeared in the
> lore archive. Not sure how much difference it would have made, IIUC
> that's more for SPF than DKIM.

I do see the

   Return-Path: <cmarinas@...nel.org>

but no, that shouldn't make any difference at all, because that's not
what dkim matches.

The spf is fine, but honestly, spf on its own is kind of useless.

> If the envelope sender doesn't work, I may have to switch to using
> cmarinas@...nel.org, at least for pull requests.

That's fine, and is probably the easiest thing to do.

            Linus