All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] staging: iio: ad7780: add gain & filter gpio support
Date: Wed, 6 Feb 2019 07:27:25 +0000	[thread overview]
Message-ID: <CAADWXX-nxpVxPmwsKKqeNHZY1OWF=a1YB93Y9g3w87zPSa5=CQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1902052054330.1726@vps.pmeerw.net>

Peter,

 this email was marked as spam for me (and probably others) because of
this DKIM signature:

   DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pmeerw.net; s=mail;
       ....

where the problem is that when the message goes through the
vger.kernel.org mailing list machinery, the header whitespace will be
modified.

As a result, the DKIM signature no longer matched, and at least gmail
will consider the email to be spam.

That's arguably a bug in the vger mail server setup, but equally
arguably the "c=simple/simple" model of hashing in DKIM is just
broken, and shouldn't be used. Whitespace in SMTP headers is simply
not meaningful, and checking whitespace in them (like simple/simple
does) is misguided.

If you have control over the DKIM setup of pmeerw.net, may I suggest
changing the DKIM setup to use "c=relaxed/relaxed", which doesn't
invalidate the signature just for whitespace changes in the headers,
and which is the proper DKIM model to use. The simple canonicalization
really is too simple-minded for  email.

            Linus

On Tue, Feb 5, 2019 at 7:58 PM Peter Meerwald-Stadler <pmeerw@pmeerw.net> wrote:
>
> On Tue, 5 Feb 2019, Renato Lui Geh wrote:
>
> > Previously, the AD7780 driver only supported gpio for the 'powerdown'
> > pin. This commit adds suppport for the 'gain' and 'filter' pin.
>
> comments below
[...]

  parent reply	other threads:[~2019-02-06  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 17:12 [PATCH v3 0/4] staging: iio: ad7780: move out of staging Renato Lui Geh
2019-02-05 17:13 ` [PATCH v3 1/4] staging: iio: ad7780: add gain & filter gpio support Renato Lui Geh
2019-02-05 19:58   ` Peter Meerwald-Stadler
2019-02-05 20:21     ` Renato Lui Geh
2019-02-06  7:27     ` Linus Torvalds [this message]
2019-02-09 16:25   ` Jonathan Cameron
2019-02-14 20:31     ` Renato Lui Geh
2019-02-18 14:48       ` Jonathan Cameron
2019-02-05 17:13 ` [PATCH v3 2/4] staging: iio: ad7780: move regulator to after GPIO init Renato Lui Geh
2019-02-09 16:26   ` Jonathan Cameron
2019-02-05 17:13 ` [PATCH v3 3/4] staging: iio: ad7780: add SPDX identifier Renato Lui Geh
2019-02-05 17:14 ` [PATCH v3 4/4] staging: iio: ad7780: moving ad7780 out of staging Renato Lui Geh
2019-02-09 16:37   ` Jonathan Cameron
2019-02-14 20:48     ` Renato Lui Geh
2019-02-18 14:50       ` Jonathan Cameron

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='CAADWXX-nxpVxPmwsKKqeNHZY1OWF=a1YB93Y9g3w87zPSa5=CQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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.