linux-kernel - Re: [PATCH] vt: Do not clear UTF when resetting console

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:	Tue, 3 Apr 2007 22:14:38 +0100
From:	Paul LeoNerd Evans <leonerd@...nerd.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	"Antonino A. Daplas" <adaplas@...il.com>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vt: Do not clear UTF when resetting console

On Mon, 02 Apr 2007 17:55:43 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> I think you're missing the whole point of console reset.  Its purpose is 
> to force the console into a known-good state.  The fewer pieces of state 
> it leaves unset, the better.  To some degree it's less important what 
> that state actually is.

Ultimately, does the patch actually change that?

Without this change, utf mode gets reset to zero because that's what the
kernel source code says.

With this change, utf mode gets reset to zero because that's what the
module parameter says and the user hasn't changed it..

.. only with the change, users get the ability to change that policy.

For the last 2 years since I originally submitted that patch, I've been
running it on my box. For those last 2 years, finally, UTF-8 input
actually worked on the VTs. Previous to that, lots of things broke.

-- 
Paul "LeoNerd" Evans

leonerd@...nerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)