linux-kernel - Re: [GIT PULL] s390 patches for the 4.17 merge window #1

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]

Date:   Mon, 9 Apr 2018 09:40:59 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        linux-s390 <linux-s390@...r.kernel.org>,
        Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [GIT PULL] s390 patches for the 4.17 merge window #1

On Mon, Apr 9, 2018 at 9:22 AM, Martin Schwidefsky
<schwidefsky@...ibm.com> wrote:
>>
>> I'm not finding the original at all, and this 'ping' message I found
>> in my spam-box. Maybe the original was marked as spam too and I didn't
>> notice, and it got deleted with the other spam.
>
> Not good, any idea why the ping message has been marked as spam?
> Maybe there is something in the headers that gives a hint.

There's nothing that looks suspicious to me in the headers, and gmail
doesn't leave any lines around either (ie no spamassassin-like scoring
etc: I don't think they want people gaming the spam detector).

There's the IBM internal spam/AV detector markings (but they all say
"not spam") and spf looks fine too (no dkim).

Maybe it was me fat-fingering the original email, causing the ping to
then be marked spam too. No way to know (although mis-marking email as
spam  without even noticing is definitely not a pattern of mine).

So I suspect it was some random word choice that triggered it.
Hopefully the fact that I marked your ping message as non-spam means
that it won't happen again for me.

I actually check my spam box fairly religiously, because I do get a
ton of spam and kernel emails occasionally do end up being false
positives, and so I check it daily to not be overwhelmed. But I also
obviously just scan it quickly, so the first one being missed and just
deleted in my daily scan is not all that surprising if it triggered
the gmail spam detector randomly.

And even if the false-positive rate is pretty darn small, I get _so_
much spam (because my email address is public and has been so long)
that even a low false-positive rate still means "a couple of
mis-marked messages each week".

              Linus