public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] sources: Replacement of Feodo Recommended Tracker list to ipblocklist sources file
Date: Mon, 09 Dec 2024 12:42:50 +0100	[thread overview]
Message-ID: <20241209114251.6249-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]

- FEODO_RECOMMENDED list is still being updated but the number of events can be very
   low. However as it is still active then it has been added back in as discussed in
   the Dev Conf Call on Nov 4th.
- FEODO_IP list covers any IP that has been detected as a botnet in the last 30 days.
   This could lead to false positives if the botnet has been fixed within one day of
   being detected. So it was agreed that this list would stay removed.
- FEODO_AGGRESSIVE list contains all IP's that havce ever been detected as botnets since
   the list was started. It is not intended to be used for blocking as it would have a
   huge false positive effect. This list will also stay removed as it should not have
   been included originally.
- This patch set adds back in the FEODO_RECOMMENDED list into the sources file and in the
   associated patch for the update.sh file removes the lines that removed the files
   related to FEODO_RECOMMENDED.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/ipblocklist/sources | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/config/ipblocklist/sources b/config/ipblocklist/sources
index c2fc40d5b..158c8bc20 100644
--- a/config/ipblocklist/sources
+++ b/config/ipblocklist/sources
@@ -61,6 +61,12 @@ our %sources = ( 'EMERGING_FWRULE' => { 'name'     => 'Emerging Threats Blocklis
                                     'parser'   => 'dshield',
                                     'rate'     => '1h',
                                     'category' => 'attacker' },
+             'FEODO_RECOMMENDED'=> {'name'     => 'Feodo Trojan IP Blocklist (Recommended)',
+                                    'url'      => 'https://feodotracker.abuse.ch/downloads/ipblocklist_recommended.txt',
+                                    'info'     => 'https://feodotracker.abuse.ch/blocklist',
+                                    'parser'   => 'ip-or-net-list',
+                                    'rate'     => '5m',
+                                    'category' => 'c and c' },
              'CIARMY'          => { 'name'     => 'The CINS Army List',
                                     'url'      => 'https://cinsscore.com/list/ci-badguys.txt',
                                     'info'     => 'https://cinsscore.com/#list',
-- 
2.47.1


             reply	other threads:[~2024-12-09 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 11:42 Adolf Belka [this message]
2024-12-09 11:42 ` [PATCH 2/2] update.sh: Remove the lines related to FEODO_RECOMMENDED Adolf Belka

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=20241209114251.6249-1-adolf.belka@ipfire.org \
    --to=adolf.belka@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