All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: List change - munging for From addresses
Date: Mon, 5 Aug 2024 12:42:04 +1000	[thread overview]
Message-ID: <20240805124204.49ed65df@canb.auug.org.au> (raw)
In-Reply-To: <20240802-agile-manipulative-dog-df4487@lemur>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Hi Konstantin,

On Fri, 2 Aug 2024 11:54:06 -0400 Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>
> Not really, for two reasons:
> 
> - X-Original-From is widely used, but isn't really a standard header.

In our case, Mailman puts the original address in the Reply-To header.

> - From-munging breaks end-to-end attestation, so we consider x-original-from
>   and similar headers a potential impersonation attempt and ignore them.

OK.

> I would generally say that From-munging isn't a great option for any list that
> receives patches. A much better approach is to just not modify the message
> headers or message body. This should be possible with mailman.

Unfortunately, I have not found a way to ensure Mailman (v2, at least)
will not modify messages in all cases e.g. in some circumstances it
will modify the To/Cc list.

So, an alternative for us (though considerable more work) is to change
mailing list software.  Mailmanv3 would be an option, but seems overly
complex.  I see vger.kernel.org is now using mlmmj - is that a
reasonable option for us (i.e. is it able to not modify messages but
still have enough features)?  If so any hints about migrating? ;-)
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-08-05  2:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  3:03 List change - munging for From addresses Stephen Rothwell
2024-08-02  3:19 ` Stephen Rothwell via Linuxppc-dev
2024-08-02 15:54 ` Konstantin Ryabitsev
2024-08-05  2:42   ` Stephen Rothwell [this message]
2024-08-05 14:54     ` Konstantin Ryabitsev
2024-08-12  5:54       ` Stephen Rothwell
2024-08-12  6:19         ` Stephen Rothwell
2024-08-12  6:32           ` Michael Ellerman
2024-08-12 13:53           ` Konstantin Ryabitsev
2024-08-25 22:41             ` Stephen Rothwell

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=20240805124204.49ed65df@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=konstantin@linuxfoundation.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.