From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 3bdac5995e4d2b9f1424e2df2b2b075915fa8b4c
Date: Tue, 19 May 2026 15:23:45 +0000 (UTC) [thread overview]
Message-ID: <4gKdjs0d5Lz2xKy@people01.haj.ipfire.org> (raw)
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 3bdac5995e4d2b9f1424e2df2b2b075915fa8b4c (commit)
from 6d3a3709d4766a98ffc6379ebf5b13a6627a9387 (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 3bdac5995e4d2b9f1424e2df2b2b075915fa8b4c
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue May 19 15:22:55 2026 +0000
suricata: Update to 8.0.5
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/suricata | 2 ++
lfs/suricata | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/suricata b/config/rootfiles/common/suricata
index 2d77b74a9..8b6b21cf7 100644
--- a/config/rootfiles/common/suricata
+++ b/config/rootfiles/common/suricata
@@ -23,6 +23,7 @@ usr/share/suricata
#usr/share/suricata/reference.config
#usr/share/suricata/rules
#usr/share/suricata/rules/app-layer-events.rules
+#usr/share/suricata/rules/bittorrent-events.rules
#usr/share/suricata/rules/decoder-events.rules
#usr/share/suricata/rules/dhcp-events.rules
#usr/share/suricata/rules/dnp3-events.rules
@@ -46,6 +47,7 @@ usr/share/suricata
#usr/share/suricata/rules/rfb-events.rules
#usr/share/suricata/rules/smb-events.rules
#usr/share/suricata/rules/smtp-events.rules
+#usr/share/suricata/rules/snmp-events.rules
#usr/share/suricata/rules/ssh-events.rules
#usr/share/suricata/rules/stream-events.rules
#usr/share/suricata/rules/tls-events.rules
diff --git a/lfs/suricata b/lfs/suricata
index 6ef15b468..992128d9d 100644
--- a/lfs/suricata
+++ b/lfs/suricata
@@ -24,7 +24,7 @@
include Config
-VER = 8.0.4
+VER = 8.0.5
THISAPP = suricata-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = a6c1958d82bb8c288c8d551d99851d19a89073397bda38bc90907950d17c35e40eb4845e9a88913bafc5c56bdad8c026e0fb665c494b102861c2b8f210c72d7f
+$(DL_FILE)_BLAKE2 = b8250ecfa2658e780624eaf2812c8bb758602efce8bce2b216efa8338544c2df4c4909cc23a8ddeca5889cc26b7cc147f3d19646b6894c7d259b13b5c056c91e
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-19 15:23 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=4gKdjs0d5Lz2xKy@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