From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 6e2c8f48182c169edb177526d7f639b0631d57cc
Date: Sat, 26 Feb 2022 14:21:21 +0000 [thread overview]
Message-ID: <4K5TN14BbXz2xg0@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2408 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 6e2c8f48182c169edb177526d7f639b0631d57cc (commit)
from ad9d6bf585c91e4696bdffbb3bf63ff741b09c81 (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 6e2c8f48182c169edb177526d7f639b0631d57cc
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 26 14:19:45 2022 +0000
suricata: drop unsupported JA3 rule provider
our current suricata version not support JA3 based rules so
this drop the providers from the list.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/suricata/ruleset-sources | 20 --------------------
1 file changed, 20 deletions(-)
Difference in files:
diff --git a/config/suricata/ruleset-sources b/config/suricata/ruleset-sources
index 7da1ecc1d..58ab91aab 100644
--- a/config/suricata/ruleset-sources
+++ b/config/suricata/ruleset-sources
@@ -67,16 +67,6 @@ our %Providers = (
dl_type => "archive",
},
- # Abuse.ch SSLBL JA3 fingerprint rules.
- sslbl_ja3 => {
- summary => "Abuse.ch SSLBL JA3 Rules",
- website => "https://sslbl.abuse.ch/",
- tr_string => "sslbl ja3 fingerprint rules",
- requires_subscription => "False",
- dl_url => "https://sslbl.abuse.ch/blacklist/ja3_fingerprints.rules",
- dl_type => "plain",
- },
-
# Abuse.ch SSLBL Blacklist rules.
sslbl_blacklist => {
summary => "Abuse.ch SSLBL Blacklist Rules",
@@ -87,16 +77,6 @@ our %Providers = (
dl_type => "plain",
},
- # Abuse.ch URLhaus Blacklist rules.
- urlhaus => {
- summary => "Abuse.ch URLhaus Blacklist Rules",
- website => "https://urlhaus.abuse.ch/",
- tr_string => "urlhaus blacklist rules",
- requires_subscription => "False",
- dl_url => "https://urlhaus.abuse.ch/downloads/urlhaus_suricata.tar.gz",
- dl_type => "archive",
- },
-
# Etnetera Aggressive Blacklist.
etnetera_aggresive => {
summary => "Etnetera Aggressive Blacklist Rules",
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-02-26 14:21 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=4K5TN14BbXz2xg0@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