From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b8fcb4956758b88b8a46eff5641aa80f244ed605
Date: Wed, 08 Apr 2020 15:44:47 +0000 [thread overview]
Message-ID: <48y7rJ25FFz2y0q@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2392 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 b8fcb4956758b88b8a46eff5641aa80f244ed605 (commit)
from b518bee95c15ce626dc93e4aa7e39282448ee0b6 (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 b8fcb4956758b88b8a46eff5641aa80f244ed605
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 8 15:43:35 2020 +0000
suricata: update ET rulesets sources for suricata 5
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/143/filelists/files | 1 +
config/suricata/ruleset-sources | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/143/filelists/files b/config/rootfiles/core/143/filelists/files
index 9cb36e78c..34e9b92df 100644
--- a/config/rootfiles/core/143/filelists/files
+++ b/config/rootfiles/core/143/filelists/files
@@ -21,3 +21,4 @@ var/ipfire/backup/bin/backup.pl
var/ipfire/backup/include
var/ipfire/ids-functions.pl
var/ipfire/suricata/oinkmaster.conf
+var/ipfire/suricata/ruleset-sources
diff --git a/config/suricata/ruleset-sources b/config/suricata/ruleset-sources
index 814a3e0d1..8b25346b5 100644
--- a/config/suricata/ruleset-sources
+++ b/config/suricata/ruleset-sources
@@ -8,8 +8,8 @@ subscripted = https://www.snort.org/rules/snortrules-snapshot-29151.tar.gz?oinkc
community = https://www.snort.org/rules/community
# Emerging threads community rules.
-emerging = https://rules.emergingthreats.net/open/suricata-4.0/emerging.rules.tar.gz
+emerging = https://rules.emergingthreats.net/open/suricata-5.0/emerging.rules.tar.gz
# Emerging threads pro rules.
-emerging_pro = https://rules.emergingthreatspro.com/<oinkcode>/suricata-4.0/etpro.rules.tar.gz
+emerging_pro = https://rules.emergingthreatspro.com/<oinkcode>/suricata-5.0/etpro.rules.tar.gz
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-08 15:44 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=48y7rJ25FFz2y0q@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