linux-kernel - Re: [PATCH] proc: fixup (c) sign

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: <20180411161748.870b31eb6293070f9928589f@linux-foundation.org>
Date:   Wed, 11 Apr 2018 16:17:48 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Alexey Dobriyan <adobriyan@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] proc: fixup (c) sign

On Wed, 11 Apr 2018 15:41:26 -0700 Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Wed, Apr 11, 2018 at 1:24 PM, Alexey Dobriyan <adobriyan@...il.com> wrote:
> >
> > It got sent from here as iso8859-1.
> 
> It's probably a good idea to just move away from Latin1 entirely, and
> encourage people to just use utf-8.

I had "set ttycharset=utf8" in .mailrc and when presented with Alexey's
patch heirloom-mailx said "Failed to create encoded message: Invalid or
incomplete multibyte or wide character".

After removing that line from .mailrc, hairloom-mailx did the offending
corruption.

Adding "set ttycharset=iso8859-1" to .mailrc permits Alexey's patch to
go through as-is.  But I assume it has broken something else :(

> But yes, Andrew's scripts clearly do a horrible job at looking at
> email encoding, and that really should be fixed.
> 
> I worry less about silly copyright signs than about peoples actual
> _names_, but we've certainly seen problems there too.

That's all fixed, afaik.