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: Windows password security audit tool. GUI, reports in PDF.

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

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

On 2024-05-23 15:19, Sirius wrote:
> In days of yore (Thu, 23 May 2024), Gedalya thus quoth:
>> Yes, echo -ne '\e]11;?\a' works on _some_ (libvte-based) terminals but 
>> not
>> all. And a core networking utility should be allowed to focus on, 
>> ehhm,
>> networking rather than oddities of a myriad terminals.
> 
> Then it perhaps should not add colour to the output in the first place 
> and
> focus solely on the networking.
> 
> A suggestion would be the iproute2 package revert the option to compile
> colourised output as default, sticking to plain text output as that
> require zero assumptions about the user terminal. Carry on offering the
> '-c' switch to enable it at runtime.

Frankly, a better suggestion would be to leave that compile-time option
supported, but to suggest that it isn't used until the current issues 
are
resolved, or until some stopgap measures are in place.