Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Allodoxaphobia <trepidation@example.net>
Newsgroups: comp.os.linux.security
Subject: Re: current public ip blocklists
Date: 24 May 2022 13:32:17 GMT
Lines: 22
Message-ID: <slrnt8pni4.2tsc.trepidation@vps.jonz.net>
References: <t01f6a$6k5$1@gioia.aioe.org> <t01idh$epm$1@tncsrv09.home.tnetconsulting.net>
Reply-To: If_you_must-Reply_to@my.sig.adr
X-Trace: individual.net H9lt0qJ+4+ko+Evo4+IaygqVVH/n/eliunJHBNL78cmS03Z6Km
Cancel-Lock: sha1:Mg1Vy7c5rsM9+hCONHoc4+Eonfg=
User-Agent: slrn/1.0.3 (FreeBSD)
Xref: csiph.com comp.os.linux.security:756

On Sat, 5 Mar 2022 22:56:22 -0700, Grant Taylor wrote:
> On 3/5/22 10:00 PM, Supratim Sanyal wrote:
>> I am currently maintaining the following IP blocklists
>
> I'm curious why you have multiple different lists.
>
> I would think that you would have the systems linked so that they can 
> share IPs and block sources that have attacked other systems.

I was hoping to see some discuss here.
I currently get a list of Bad Actors from

	https://github.com/stamparm/ipsum

  to use as an addendum to the CIDRs I generate from my own pflog 
for my VPS.

Jonesy
-- 
  Marvin L Jones    | Marvin      | W3DHJ.net  | linux
   38.238N 104.547W |  @ jonz.net | Jonesy     |  FreeBSD
    * Killfiling google & XXXXbanter.com: jonz.net/ng.htm