linux-kernel - Re: [GIT PULL] Landlock fixes for v5.18

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: <CAADWXX_06uyx5KLE-6pv6pqQJ5qH4EqYiYK7rGK3zMyEZjW4dw@mail.gmail.com>
Date:   Mon, 21 Mar 2022 10:37:34 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Mickaël Salaün <mic@...ikod.net>
Cc:     Christian Brauner <brauner@...nel.org>, Tom Rix <trix@...hat.com>,
        lkml <linux-kernel@...r.kernel.org>,
        LSM List <linux-security-module@...r.kernel.org>
Subject: Re: [GIT PULL] Landlock fixes for v5.18

On Mon, Mar 21, 2022 at 4:58 AM Mickaël Salaün <mic@...ikod.net> wrote:
>
> Please pull these Landlock updates for v5.18-rc1 .

Mickaël, both your pull requests (this and the 'trusted_for(2)' one)
were marked as spam for me.

The reason seems to be that you're using a SMTP host that doesn't
actually do modern anti-spam measures (no DKIM), and while it does do
SPF, gmail really dislikes it.

There doesn't seem anything in particular standing out in the email
itself, so I suspect your hosting provider (seems to be infomaniak.ch)
ends up either being in a block of IP addresses that is also being
used for spam, or it's just allowing a lot of spam itself.

Some people think that gmail is being way too restrictive about these
kinds of things, but since I hate spam with a passion, I end up siding
with rather strict spam measures.. Honestly, if an email provider
doesn't do DKIM in this day and age, it's not a very good email
provider imho.

               Linus