netdev - Re: iproute2: color output should assume dark background

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <36106338ae3105ba9ef6c858f30efd67@manjaro.org>
Date: Thu, 23 May 2024 16:29:10 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Gedalya <gedalya@...alya.net>
Cc: Sirius <sirius@...dheim.com>, netdev@...r.kernel.org
Subject: Re: iproute2: color output should assume dark background

On 2024-05-23 16:28, Dragan Simic wrote:
> On 2024-05-23 16:19, Gedalya wrote:
>> On 5/23/24 10:11 PM, Sirius wrote:
>>> For the colours like blue and magenta, using \e[34;1m and \e[35;1m 
>>> would
>>> make it more readable against dark background. And testing with a 
>>> dark
>>> background right now, that would suffice the other colours are not
>>> problematic to read. (It uses the "bright" version of the two colours
>>> rather than the usual.)
>>> 
>>> That would be a miniscule change to iproute2 and would resolve the
>>> problem no matter what background is used. I need to test with 
>>> schemas
>>> like solarized light and dark as well, as they are finicky.
>> 
>> I find this constructive.
> 
> Agreed, find such a balance would be a really good stopgap measure.

Oops...  s/find/finding/

>> BTW I find that both current iproute2 palettes work with a light gray
>> background.
>> 
>> It stands to reason that foreground colors could be chosen such that
>> they work with black, several dark and several light background
>> colors.
>> 
>> And yes please iproute2 should not be built with colors 
>> default-enabled!