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: <7cfcca05-95d0-4be0-9b50-ec77bf3e766c@gedalya.net>
Date: Thu, 23 May 2024 21:50:38 +0800
From: Gedalya <gedalya@...alya.net>
To: Dragan Simic <dsimic@...jaro.org>
Cc: Sirius <sirius@...dheim.com>, netdev@...r.kernel.org
Subject: Re: iproute2: color output should assume dark background

On 5/23/24 9:23 PM, Dragan Simic wrote:
>> And what about linux virtual terminals (a.k.a non-graphical consoles)?
>
> In my 25+ years of Linux experience, I've never seen one with a 
> background
> color other than black. 

You kind of missed my question: Do we make a new rule where a correctly 
set COLORFGBG is mandatory for linux vt?

That's what I meant. The fact that both vt and graphical terminal 
emulators tend to be dark is another point.

My point is you can't rely on COLORFGBG. You can only use it if/when set.

A reasonable default is needed.



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ