From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b23db9b97b897b40daf2da7d94b655f58d54fe27
Date: Wed, 22 May 2019 09:32:18 +0100 [thread overview]
Message-ID: <20190522083219.1BA6B84FDC8@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2410 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via b23db9b97b897b40daf2da7d94b655f58d54fe27 (commit)
from 716f00b1165d492479e7ec24a6b3cf14ea17b89d (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit b23db9b97b897b40daf2da7d94b655f58d54fe27
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed May 22 10:22:53 2019 +0200
vulnerablities.cgi: add colours for vuln,smt and unknown output.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/vulnerabilities.cgi | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/vulnerabilities.cgi b/html/cgi-bin/vulnerabilities.cgi
index 371ffa547..91db2f4c3 100644
--- a/html/cgi-bin/vulnerabilities.cgi
+++ b/html/cgi-bin/vulnerabilities.cgi
@@ -125,14 +125,22 @@ for my $vuln (sort keys %VULNERABILITIES) {
$colour = "white";
$bgcolour = ${Header::colourred};
+ # Mitigated but smt is enabled
+ } elsif ($status eq "Mitigation-SMT") {
+ $status_message = $Lang::tr{'mitigated'};
+ $colour = "black";
+ $bgcolour = ${Header::colourorange};
+
# Mitigated
} elsif ($status eq "Mitigation") {
$status_message = $Lang::tr{'mitigated'};
$colour = "black";
- $bgcolour = ${Header::colourorange};
+ $bgcolour = ${Header::colouryellow};
} else {
- next;
+ $status_message = $status;
+ $colour = "white";
+ $bgcolour = ${Header::colourblue};
}
my $table_colour = ($id++ % 2) ? $color{'color22'} : $color{'color20'};
@@ -224,6 +232,14 @@ sub check_status($) {
my $status = <FILE>;
close(FILE);
+ if ($status =~ /^(Vulnerable): (.*)$/) {
+ return ($1, $2);
+ }
+
+ if ($status =~ /^(Mitigation): (.*vulnerable.*)$/) {
+ return ("Mitigation-SMT", $2);
+ }
+
if ($status =~ /^(Mitigation): (.*)$/) {
return ($1, $2);
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-05-22 8:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190522083219.1BA6B84FDC8@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox