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: <20230726-armless-ungodly-a3242f@meerkat>
Date: Wed, 26 Jul 2023 20:24:06 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, 
	Joe Perches <joe@...ches.com>, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
	geert@...ux-m68k.org, gregkh@...uxfoundation.org, netdev@...r.kernel.org, 
	workflows@...r.kernel.org, mario.limonciello@....com
Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from using
 file paths

On Wed, Jul 26, 2023 at 05:11:23PM -0700, Jakub Kicinski wrote:
> Hm, hm. I wasn't thrilled by the idea of sending people a notification
> that "you weren't CCed on this patch, here's a link". But depending on
> your definition of "hitting the feed" it sounds like we may be able to
> insert the CC into the actual email before it hits lore? That'd be
> very cool! At least for the lists already migrated from vger to korg?

No, inserting their addresses into message headers would invalidate DKIM,
which is not what we want to do. However, the idea is that they would receive
the actual patches in the same way they would receive them if they were
subscribed to a mailing list.

Think as if instead of being Cc'd on patches, they got Bcc'd on them.

-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ