From: Adam Gibbons <adam.gibbons@ipfire.org>
To: Development <development@lists.ipfire.org>
Subject: [PATCH] ruleset-sources: Require an Auth-Key for ThreatFox downloads
Date: Mon, 26 Oct 2026 11:07:50 +0000 [thread overview]
Message-ID: <241bd42817b9c5a0a2f5384921da9d84@ipfire.org> (raw)
Since 21 October 2026, ThreatFox file exports require an abuse.ch
Auth-Key.
News link:
https://www.linkedin.com/posts/abuse-ch_authenticate-steadyplatform-steadysignal-activity-7518660733203832832-ohAX
IPFire's ThreatFox provider still uses the unauthenticated download URL,
which prevents ruleset updates.
I have tested a two-line change that marks ThreatFox as requiring a
subscription code and uses the authenticated v2 export URL. This reuses
the existing WUI "Subscription Code" field, stored provider settings and
URL substitution.
Fixes bug report: https://bugzilla.ipfire.org/show_bug.cgi?id=14664
Signed-off-by: Adam Gibbons <adam.gibbons@ipfire.org>
---
diff --git a/config/suricata/ruleset-sources
b/config/suricata/ruleset-sources
index 3cef7c657..71d18c780 100644
--- a/config/suricata/ruleset-sources
+++ b/config/suricata/ruleset-sources
@@ -143,8 +143,8 @@ our %Providers = (
summary => "ThreatFox Indicators Of Compromise Rules",
website => "https://threatfox.abuse.ch/",
tr_string => "threatfox rules",
- requires_subscription => "False",
- dl_url =>
"https://threatfox.abuse.ch/downloads/threatfox_suricata.rules",
+ requires_subscription => "True",
+ dl_url =>
"https://threatfox-api.abuse.ch/v2/files/exports/<subscription_code>/threatfox_suricata.rules",
dl_type => "plain",
sid_range => ["91000000", "91999999"],
},
reply other threads:[~2026-10-26 11: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=241bd42817b9c5a0a2f5384921da9d84@ipfire.org \
--to=adam.gibbons@ipfire.org \
--cc=development@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