From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <C735CFB9-BC30-43A9-AF10-05EF8AD5E711@ipfire.org>
In-Reply-To:
 <CAD-y=ja5+HB0kKKV900KY1Bab7FsfcTzpjh9rfvRrH_vrRsQZg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7506223749878013637=="
List-Id: <development.lists.ipfire.org>

--===============7506223749878013637==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Chris,

> On 11 Oct 2022, at 14:35, Chris Multari <cmultari(a)gmail.com> wrote:
>=20
> IPFire Devs - The IP Blocklist feature has been absolutely great. =20

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 amo=
unt of IPs depending on your subscription level/account config, but bad actor=
s are picked up quickly.=20

Currently, we only process offline blocklists, since it isn=E2=80=99t feasibl=
e to send any API requests out. A busy firewall might get many thousands of p=
ackets in a second that need checking (and that includes any potential cachin=
g of responses).

As far as I can see, there is no way to download the entire list in text form=
at.

-Michael

>=20
> Thanks!
> Chris


--===============7506223749878013637==--