linux-kernel - Re: [GIT PULL] spi updates for v5.2

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: <20190507021853.GY14916@sirena.org.uk>
Date:   Tue, 7 May 2019 11:18:53 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     linux-spi@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] spi updates for v5.2

On Mon, May 06, 2019 at 12:01:44PM -0700, Linus Torvalds wrote:
> Mark,
>  gmail once again hates your emails. Your email ends up as spam, due to
> 
>     dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org

That looks like it's a fail on validation of the kernel.org bit of
things which I have no control over and which purposely doesn't
advertise DKIM stuff in the hope that people will actually be able to
send mail from non-kernel.org mail servers.  I'm really unsure why
that's failing at all, there's no policy for kernel.org to fail.

> but it has a DKIM signature for sirena.org.uk:
> 
>     DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
> d=sirena.org.uk; ...

which should match the envelope sender.

As far as I can tell Google is going to be unhappy no matter what unless
I use their services - if there's DKIM records it's not going to like
that the from is from kernel.org and if I don't have DKIM records then
it's not going to like that either and I'll be more vulnerable to the
blacklists that try to extort money out of people for permanent
delisting.

Possibly it's not actually anything to do with the DKIM and it's just
upset that I'm travelling and so the mail was injected from a mobile
broadband IP in Japan which doesn't match up with the .uk domain.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)