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 2/2] ipblocklist-sources: Update to include the Abuse.ch Botnet C2 ip blocklist
Date: Mon, 24 Jun 2024 17:10:39 +0200	[thread overview]
Message-ID: <20240624151039.51194-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20240624151039.51194-1-adolf.belka@ipfire.org>

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

- Blocklist addition was discussed and agreed at IPFire dev conf call in June 2024.
- Tested on vm system.

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

diff --git a/config/ipblocklist/sources b/config/ipblocklist/sources
index 69f964dd9..1cef06dd1 100644
--- a/config/ipblocklist/sources
+++ b/config/ipblocklist/sources
@@ -142,5 +142,11 @@ our %sources = ( 'EMERGING_FWRULE' => { 'name'     => 'Emerging Threats Blocklis
 					 'info'     => 'https://blacklist.3coresec.net',
 					 'parser'   => 'ip-or-net-list',
 					 'rate'     => '1d',
-					 'category' => 'attacker' }
+					 'category' => 'attacker' },
+	      'ABUSECH_BOTNETC2'  => { 'name'	=> 'ABUSE.ch Botnet C2 IP Blocklist',
+					   'url'	=> 'https://sslbl.abuse.ch/blacklist/sslipblacklist.txt',
+					   'info'	=> 'https://sslbl.abuse.ch/blacklist#botnet-c2-ips-csv',
+					   'parser'	=> 'ip-or-net-list',
+					   'rate'	=> '5m',
+					   'category'	=> 'reputation' }
            );
-- 
2.45.2


  reply	other threads:[~2024-06-24 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 15:10 [PATCH 1/2] ipblocklist-sources: Update to include the 3CORESec ip blocklists Adolf Belka
2024-06-24 15:10 ` Adolf Belka [this message]
2024-07-03 12:59   ` [PATCH 2/2] ipblocklist-sources: Update to include the Abuse.ch Botnet C2 ip blocklist Charles Brown
2024-07-03 13:03     ` Charles Brown
2024-07-03 14:06       ` Charles Brown

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=20240624151039.51194-2-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