linux-kernel - Re: [GIT PULL] SPI updates for v3.14 remerged

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140123180410.GA9571@sirena.org.uk>
Date:	Thu, 23 Jan 2014 18:04:10 +0000
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 v3.14 remerged

On Thu, Jan 23, 2014 at 09:40:44AM -0800, Linus Torvalds wrote:
> On Thu, Jan 23, 2014 at 5:19 AM, Mark Brown <broonie@...nel.org> wrote:

> > spi: Updates for v3.14

> gmail hates you. I just found four of your emails in my spam-box.

> I don't know why, since it's not the (somewhat) common issue with bad
> or missing SPF information. The only thing I can imagine is that gmail
> thinks you're not you, since your "From:" line says

>    From: Mark Brown <broonie@...nel.org>

> but then the SPF is validated as coming from
> smtp.mail=broonie@...ena.org.uk with that as a return path:

>    Return-Path: <broonie@...ena.org.uk>

> so gmail may be dinging you for not using your real "From:". I dunno.
> Nothing else looks odd about the email.

Possibly - I've noticed the same problem myself in incoming non-upstream
mail hosted on gmail, they seem to have recently introduced new checks
there which aren't playing well with some mailing lists and e-mail
forwarding either.  For some mails it's explicitly saying that it thinks
it's forged.

Dunno if the fact that one of the VMs that handles my outgoing mail is
now in Japan (so I can have something a bit less laggy when I travel in
Asia) is hurting too but that'd be a bit odd.

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