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 15:51:51 +0100
From:	Paul LeoNerd Evans <leonerd@...nerd.org.uk>
To:	Martin Mares <mj@....cz>
Cc:	"Antonino A. Daplas" <adaplas@...il.com>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Paul LeoNerd Evans <leonerd@...nerd.org.uk>
Subject: Re: [PATCH] vt: Do not clear UTF when resetting console

On Tue, Apr 03, 2007 at 01:41:27PM +0200, Martin Mares wrote:
> > Resetting the console, either by ANSI escape sequences or by the reset utility,
> > will drop the console back to legacy (non-UTF-8) mode.
> 
> Yes, and as far as I understand the logic behind these escape sequences,
> it's the intended behavior, not a bug.
> 
> The escape sequence for terminal reset should reset as much as possible,
> I see no reason for making an exception for the UTF-8 mode.

Does whatever defines what these escapes mean, have any comment to make
about UTF-8? If not, why can't we declare that UTF-8 mode is the "reset"
mode, the default that would be dropped to on a full reset, and if
anyone wanted to switch that out to non-default not-UTF-8 mode, they
could, but that a reset will always reenable it again..?

-- 
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)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ