From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 4913a44798caa0a190aef6cfced766e713ea260a
Date: Fri, 20 Sep 2024 10:22:34 +0000 [thread overview]
Message-ID: <4X97k24njLz2xn5@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1743 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 4913a44798caa0a190aef6cfced766e713ea260a (commit)
from 3cd62a7c4cacd3e2821658f9e36667e81b17cf11 (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 4913a44798caa0a190aef6cfced766e713ea260a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Sep 20 10:21:19 2024 +0000
core189: Regenerate Suricata rulefiles again
This is needed for people who have missed this in Core Update 188.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/189/update.sh | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/189/update.sh b/config/rootfiles/core/189/update.sh
index 149f8f677..3bcbcb3bb 100644
--- a/config/rootfiles/core/189/update.sh
+++ b/config/rootfiles/core/189/update.sh
@@ -352,6 +352,10 @@ telinit u
/usr/local/bin/openvpnctrl -s
/usr/local/bin/openvpnctrl -sn2n
+# Regenerate Suricata rule files
+perl -e "require '/var/ipfire/ids-functions.pl'; &IDS::write_used_rulefiles_file();"t
+/etc/init.d/suricata reload
+
# Build initial ramdisks
dracut --regenerate-all --force
KVER="xxxKVERxxx"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-09-20 10:22 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=4X97k24njLz2xn5@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