From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: abuseipdb IP Blocklist
Date: Wed, 12 Oct 2022 10:35:32 +0100 [thread overview]
Message-ID: <C735CFB9-BC30-43A9-AF10-05EF8AD5E711@ipfire.org> (raw)
In-Reply-To: <CAD-y=ja5+HB0kKKV900KY1Bab7FsfcTzpjh9rfvRrH_vrRsQZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Hello Chris,
> On 11 Oct 2022, at 14:35, Chris Multari <cmultari(a)gmail.com> wrote:
>
> IPFire Devs - The IP Blocklist feature has been absolutely great.
Thanks for the feedback!
> Has been any consideration given to adding something like the abuseipdb.com blocklist? The list does require an API key and will return a different amount of IPs depending on your subscription level/account config, but bad actors are picked up quickly.
Currently, we only process offline blocklists, since it isn’t feasible to send any API requests out. A busy firewall might get many thousands of packets in a second that need checking (and that includes any potential caching of responses).
As far as I can see, there is no way to download the entire list in text format.
-Michael
>
> Thanks!
> Chris
parent reply other threads:[~2022-10-12 9:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAD-y=ja5+HB0kKKV900KY1Bab7FsfcTzpjh9rfvRrH_vrRsQZg@mail.gmail.com>]
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=C735CFB9-BC30-43A9-AF10-05EF8AD5E711@ipfire.org \
--to=michael.tremer@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