[PATCH] vulnerabilities.cgi: Use orange instead of blue for mitigated issues

Peter Müller peter.mueller at ipfire.org
Mon Jun 10 20:24:00 BST 2019


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üller <peter.mueller at ipfire.org>
---
 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 = $Lang::tr{'mitigated'};
 		$colour = "white";
-		$bgcolour = ${Header::colourblue};
+		$bgcolour = ${Header::colourorange};
 
 	# Unknown report from kernel
 	} else {
-- 
2.16.4


More information about the Development mailing list