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]

Date:   Thu, 12 Apr 2018 13:16:06 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Alexey Dobriyan <adobriyan@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] proc: fixup (c) sign

On Thu, Apr 12, 2018 at 12:50 PM, Alexey Dobriyan <adobriyan@...il.com> wrote:
>
> I've checked earlier mails, mutt has been "guessing" outgoing encoding
> by default. Let's try again.

I think it still does. This email came with

    Content-Type: text/plain; charset=us-ascii

which is what I'd expect if Mutt has a "use the least complex charset
that can fit the message".

If you look at my emails, you should see

    Content-Type: text/plain; charset="UTF-8"

even for an email like this, that only has 7-bit ascii.

I'm not a Mutt user, so I don't know what the magic is for "just force
utf-8 when sending".

For alpine, it's

    posting-character-set=UTF-8

in the .pinerc file.

For gmail there used to be an "outgoing message encoding" setting, but
it seems to have been removed (and now utf-8 is always on).

             Linus