linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: postmaster@intel.com, linux-kernel@vger.kernel.org
Subject: Please switch intel.com DKIM signatures to c=relaxed/simple
Date: Tue, 14 Dec 2021 10:00:32 -0500	[thread overview]
Message-ID: <20211214150032.nioelgvmase7yyus@meerkat.local> (raw)

Dear Intel Postmaster:

The intel.com domain has recently started DKIM-signing all outgoing mail,
which is great news, as it helps to add a degree of cryptographic attestation
to smtp-exchanged messages.

Unfortunately, your DKIM c= (canonicalization) setting is currently configured
as simple/simple, which is unnecessarily fragile and will likely result in a
greater degree of quarantined mail, especially for messages traversing a
mailing list service.

To explain, the first "simple" in simple/simple means that the message headers
are signed without any whitespace normalization. If an SMTP-processing gateway
even so much as rewraps a header by adding or deleting newlines (which it is
perfectly allowed per RFC), the DKIM signature will stop validating and the
message will likely be quarantined by the recipient's SMTP gateway. This is
happening right now for any intel.com messages sent via vger.kernel.org --
they are marked as spam by services like Gmail.

So, please reconfigure intel.com's DKIM signature setting to use
c=relaxed/simple. It will have the exact same security effect (nobody cares
about whitespace in headers), and it will greatly improve the lives of many
kernel developers at Intel.

Best regards,
-- 
Konstantin Ryabitsev
Director, Core IT Projects
The Linux Foundation

             reply	other threads:[~2021-12-14 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 15:00 Konstantin Ryabitsev [this message]
2021-12-15 18:46 ` Please switch intel.com DKIM signatures to c=relaxed/simple Konstantin Ryabitsev

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=20211214150032.nioelgvmase7yyus@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postmaster@intel.com \
    /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).