linux-kernel - Re: [GIT PULL] 9p update for 5.10-rc7 (restore splice ops)

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] [day] [month] [year] [list]

Message-ID: <CAHk-=wjh2=Afx3Eb18RW_APaBKMppmpCpAfFd+n_4DttWJeFow@mail.gmail.com>
Date:   Thu, 3 Dec 2020 14:34:36 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Dominique Martinet <asmadeus@...ewreck.org>
Cc:     v9fs-developer@...ts.sourceforge.net,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] 9p update for 5.10-rc7 (restore splice ops)

On Thu, Dec 3, 2020 at 2:15 PM Dominique Martinet
<asmadeus@...ewreck.org> wrote:
>
> The problems I had with dkim are all lists that add footers so really
> not much to do about header filtering

Yeah, that's obviously always going to be a problem with DKIM.

But I think all the kernel mailing lists are good now - at least
partly because I used to complain about it.

The one thing that vger still does - or at least did not that long ago
- is to change whitespace in headers. But that is perfectly acceptable
SMTP behavior, and it's a problem only when somebody is using
"c=strict/strict" in their DKIM setup. And honestly, that's a
completely invalid DKIM setting, I don't understand how the DKIM
people ever thought it was ok (probably some company politics or other
because some vendor was too incompetent to implement the proper
relaxed hashing).

          Linus