linux-kernel - Re: [PATCH] Input: elantech - Fix V4 report decoding for module with middle key

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]

Date:   Mon, 2 Jul 2018 09:31:10 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Kalle Valo <kvalo@...eaurora.org>
Cc:     Dmitry Torokhov <dmitry.torokhov@...il.com>, kt.liao@....com.tw,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-input <linux-input@...r.kernel.org>,
        ulrik.debie-os@...ig.org, phoenix@....com.tw,
        aaron.ma@...onical.com, josh.chen@....com.tw
Subject: Re: [PATCH] Input: elantech - Fix V4 report decoding for module with
 middle key

On Mon, Jul 2, 2018 at 5:13 AM Kalle Valo <kvalo@...eaurora.org> wrote:
>
> FWIW I use patchwork.kernel.org and I don't have any issues with UTF-8
> characters in the From header. For example, here's one patch which I
> recently applied:
>
> https://git.kernel.org/linus/88001968245c

Well, that one actually has at least two reasons why it might work well:

 - Rafał sends his patches with an explicit "From:" line in the body
of the email itself (probably because he has had problems with email
headers in the past).  So his body itself has

    From: Rafał Miłecki <rafal@...ecki.pl>

 - Also, even ignoring that, he actually uses utf-8 in the headers
too, so his "From" header line looks like

    From:   =?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?= <zajec5@...il.com>

so it is already in UTF-8, it just is rfc2047-encoded.

I suspect it's that first reason that patchwork.kernel.org gets it
right, but it *migth* be the fact that the problematic email is using
the old 'big5'  encoding:

    From:   =?big5?B?ufmxUrph?= <kt.liao@....com.tw>

anyway, it does look like a newer version of patchwork will fix this.

           Linus