linux-kernel - Re: linux 2.6.26 vt back_color

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.LNX.1.10.0810130317450.9172@fbirervta.pbzchgretzou.qr>
Date:	Mon, 13 Oct 2008 03:40:25 -0400 (EDT)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	"Alexander V. Lukyanov" <lav@...is.ru>
cc:	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Ncurses Developers <ncurses-dev@....org>
Subject: Re: linux 2.6.26 vt back_color_erase


On Monday 2008-10-13 01:24, Alexander V. Lukyanov wrote:

>On Fri, Oct 10, 2008 at 01:22:08PM -0400, Jan Engelhardt wrote:
>> >> Current linux kernel has broken bce semantics. Now insert_line and
>> >> delete_line clear the new lines with default color and not with the
>> >> current background as they should, and what is expected by ncurses.
>> 
>> I beg to differ. The Linux VT now does exactly what an xterm does,
>
>I have just tested again: my xterm does erase new lines with current color,
>just as linux console before the change. My xterm version: XTerm(196).
>Please test yours and check the version.

It seems that xterm-235 does indeed erase-with-current on _scrolling_
(i.e. PS1='$'; echo -en "\e[25B\e[44mfoo\n\e[0m") as do urxvt.

>Probably color ls -l is just broken and should be fixed. Why was it
>necessary to change the console color semantics that was there for years?

Because the Linux VT also did erase-with-current on _linewrap_,
which xterm and urxvt certainly do not do.

Mh, this is really unfortunate; I agree something
needs to be backed out.

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