linux-kernel - Re: [patch] vt: deactive Shift In/Out in unicode mode

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: <alpine.LSU.2.01.1004221013430.27555@obet.zrqbmnf.qr>
Date:	Thu, 22 Apr 2010 10:39:29 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Alexander E. Patrakov" <patrakov@...il.com>
Subject: Re: [patch] vt: deactive Shift In/Out in unicode mode


On Wednesday 2010-04-21 01:49, H. Peter Anvin wrote:
>> Alexander mentioned:
>> [quoting the gmane nntp posting which was stripped of To:s and Cc:s]
>>>
>>> Since KOI7 is not used by any glibc locale, your use case is now 
>>> extinct. I think that, unless someone finds out a different use case, 
>>> these SI and SO characters should be deactivated completely (and not 
>>> just in unicode mode).
>> 
>> Alan, do you agree that the entire SI/SO can/should be removed?
>
>VT line drawing characters are generally assumed to be accessible using
>SI/SO (as they are by default.)

Indeed 0x0e 0x71 0x0f generates the same output as U+2501.

I can't say when the last time was that I saw SISO in use, though.
At least UTF-8 programs just print U+2501, so it should
be fine to exclude SISO handling there.
With

	echo -en "\e%@"; setfont r -u /usr/share/kbd/unimaps/cp437.uni;
	LC_CTYPE=C mc

it would also output no SISO and use 0xc4 for U+2501.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/