From: Kees Cook <keescook@chromium.org>
To: tools@linux.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: injected body trailers
Date: Thu, 21 Oct 2021 13:22:31 -0700 [thread overview]
Message-ID: <202110211313.B5C5C61@keescook> (raw)
Hi!
So, I just saw a DKIM failure, and it was entirely justified. :)
Grabbing thread from lore.kernel.org/all/20211021142516.1843042-1-ardb%40kernel.org/t.mbox.gz
Checking for newer revisions on https://lore.kernel.org/all/
Analyzing 1 messages in the thread
Checking attestation on all messages, may take a moment...
---
✓ [PATCH] ARM: stackprotector: prefer compiler for TLS based per-task protector
✓ Signed: openpgp/ardb@kernel.org
✗ BADSIG: DKIM/kernel.org
✓ Signed: DKIM/lists.infradead.org (From: ardb@kernel.org)
---
This is https://lore.kernel.org/all/20211021142516.1843042-1-ardb@kernel.org/
and for some reason, the linux-arm-kernel mailing list is injecting a
body trailer.
I just downloaded this directly and removed the trailer, and the DKIM
passed. This experience has raise a few questions...
1) Can (should) b4 grow logic to progressively strip lines off the end
of a body until DKIM passes?
2) Can the linux-arm-kernel mailing list please stop breaking DKIM?
Who should authorize this change (rmk, Catalin)? And who can make
the change (peterz)?
(I realize now that all the mail from linux-arm-kernel has been
getting dropped into my Spam folder -- I normally don't notice since
I'm usually CCed directly or via some other list on things I wanted
to see.)
3) Are there other lists for which lore is collecting emails where DKIM
is persistently broken, and can we fix those lists too?
Thoughts?
-Kees
--
Kees Cook
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-10-21 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 20:22 Kees Cook [this message]
2021-10-21 20:44 ` injected body trailers Konstantin Ryabitsev
2021-10-21 21:21 ` Kees Cook
2021-10-21 21:29 ` Catalin Marinas
2021-10-21 21:42 ` David Woodhouse
2021-10-21 22:57 ` Konstantin Ryabitsev
2021-10-21 23:00 ` David Woodhouse
2021-10-21 23:33 ` Konstantin Ryabitsev
2021-10-21 23:41 ` David Woodhouse
2021-10-22 3:53 ` Kees Cook
2021-10-22 7:32 ` Russell King (Oracle)
2021-10-22 8:05 ` Arnd Bergmann
2021-10-22 9:41 ` Ard Biesheuvel
2021-10-22 11:43 ` Catalin Marinas
2021-10-26 8:30 ` Will Deacon
2021-10-21 22:23 ` Russell King (Oracle)
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=202110211313.B5C5C61@keescook \
--to=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tools@linux.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).