From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 185c0c13f929bd33d5200d10c857d9438b226558
Date: Fri, 30 Oct 2026 12:08:07 +0000 (UTC) [thread overview]
Message-ID: <4jGKcR1CPMz2y3W@people01.haj.ipfire.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3451 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, master has been updated
via 185c0c13f929bd33d5200d10c857d9438b226558 (commit)
from a579d5e7fd1ef23523259fbcf2560e12846516d4 (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 185c0c13f929bd33d5200d10c857d9438b226558
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Fri Oct 30 13:03:31 2026 +0100
suricata: Update to version 8.0.8
- Update from version 8.0.7 to 8.0.8
- Update of rootfile
- Changelog
8.0.8
This is a security release, fixing a number of important issues. This is again a
release with a higher number of vulnerability reports, as a result of the rise
of AI(-assisted) analysis, resulting in a higher-than-usual number of issues.
Notable Changes
Various security, performance, accuracy, and stability issues have been fixed.
All tickets for 8.0.8:
https://redmine.openinfosecfoundation.org/versions/238
(note that private Suricata tickets will be opened to the public 2
weeks after the release)
Security Tickets Addressed:
In this release, we’ve fixed 32 vulnerabilities. Overall stats, per OISF
classification:
6 High severity issues
6 Moderate severity issues
20 Low severity issues
Note that no CVEs have been assigned at this time due to a backlog with our CNA
The related Security tickets will be made public within 2 weeks from the
release date.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/suricata | 1 +
lfs/suricata | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/suricata b/config/rootfiles/common/suricata
index 54f02ec89..8f34958b1 100644
--- a/config/rootfiles/common/suricata
+++ b/config/rootfiles/common/suricata
@@ -46,6 +46,7 @@ usr/share/suricata
#usr/share/suricata/rules/pop3-events.rules
#usr/share/suricata/rules/quic-events.rules
#usr/share/suricata/rules/rfb-events.rules
+#usr/share/suricata/rules/sip-events.rules
#usr/share/suricata/rules/smb-events.rules
#usr/share/suricata/rules/smtp-events.rules
#usr/share/suricata/rules/snmp-events.rules
diff --git a/lfs/suricata b/lfs/suricata
index e16117ac4..cd1c7af75 100644
--- a/lfs/suricata
+++ b/lfs/suricata
@@ -24,7 +24,7 @@
include Config
-VER = 8.0.7
+VER = 8.0.8
THISAPP = suricata-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = eb6bda943779f0353a74aa8d783c037f3f08ab311a679962b0742df57c37e2d926a37002085dbff3463212f708f9baf128c4dc15905a0a42458c8a69bcea9e30
+$(DL_FILE)_BLAKE2 = 656608209e1e3dd1812407852c9350370ee446cfe2999e416bf64600a65faed576b70b7f66479a4306163582b90a6be5818180e9cb03469e11171675e9f0fe27
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-10-30 12:08 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=4jGKcR1CPMz2y3W@people01.haj.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