linux-kernel - Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

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: <71b7a3e8-7fb7-5612-e244-8d8295baf943@infradead.org>
Date:   Wed, 19 Jul 2017 18:04:38 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

On 07/19/2017 05:53 PM, Linus Torvalds wrote:
> On Wed, Jul 19, 2017 at 5:35 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>> Your mailer is crap, and destroys utf-8 characters. In particular:
>>
>>     -M:     MichaÅ‚ MirosÅ‚aw <mirq-linux@...e.qmqm.pl>
> 
> Using pseudo-MIME-encoding, that was actually (before my cut-and-paste
> mangled it even more):
> 
>     Micha=c3=85=c2=82 Miros=c3=85=c2=82aw
> 
>> should be
>>
>>     -M:      Michał Mirosław <mirq-linux@...e.qmqm.pl>
> 
> And the correct utf-8 is
> 
>     Micha=C5=82 Miros=C5=82aw
> 
> and it *looks* like what happened is that something thought the input
> was Latin1, and converted the Latin1 to UTF-8.
> 
> So the utf-8 character 'ł' (two bytes: =C5=82) was seen as two Latin1
> character bytes: =c5 and =82.
> 
> And then each of those were converted mindlessly to utf-8, so the 'c5'
> character became '=C3=85' and the '82' character became '=c2=82'.
> 
> So you have something that believes that a source file was latin1.
> 
> May I suggest just making absolutely *everything* on your system use a
> utf-8 locale?
> 
> Because in this day and age, anything but utf-8 is just woefully
> broken crud. "Just say no".

Thanks for the diagnosis.  Will do.


-- 
~Randy