From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: [PATCH] vulnerabilities.cgi: Use orange instead of blue for mitigated issues Date: Mon, 10 Jun 2019 19:24:00 +0000 Message-ID: <7f63ca30-c3cf-e697-4b54-b8669aacc6ef@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0008048398816074564==" List-Id: --===============0008048398816074564== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable A mitigated (CPU) vulnerability is still present and might be just harder to exploit. Using blue as colour for them does not illustrate their dangerousness - orange is a better choice as far as I am concerned. Scaring people away from Intel processors will be a completely unintended side effect. :-) Signed-off-by: Peter M=C3=BCller --- html/cgi-bin/vulnerabilities.cgi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/html/cgi-bin/vulnerabilities.cgi b/html/cgi-bin/vulnerabilities.= cgi index a8746c30c..21d963618 100644 --- a/html/cgi-bin/vulnerabilities.cgi +++ b/html/cgi-bin/vulnerabilities.cgi @@ -129,7 +129,7 @@ for my $vuln (sort keys %VULNERABILITIES) { } elsif ($status eq "Mitigation") { $status_message =3D $Lang::tr{'mitigated'}; $colour =3D "white"; - $bgcolour =3D ${Header::colourblue}; + $bgcolour =3D ${Header::colourorange}; =20 # Unknown report from kernel } else { --=20 2.16.4 --===============0008048398816074564==--