Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.security > #756
| From | Allodoxaphobia <trepidation@example.net> |
|---|---|
| Newsgroups | comp.os.linux.security |
| Subject | Re: current public ip blocklists |
| Date | 2022-05-24 13:32 +0000 |
| Message-ID | <slrnt8pni4.2tsc.trepidation@vps.jonz.net> (permalink) |
| References | <t01f6a$6k5$1@gioia.aioe.org> <t01idh$epm$1@tncsrv09.home.tnetconsulting.net> |
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
Back to comp.os.linux.security | Previous | Next — Previous in thread | Next in thread | Find similar
current public ip blocklists Supratim Sanyal <supratim@riseupdeleteme.net> - 2022-03-06 00:00 -0500
Re: current public ip blocklists Grant Taylor <gtaylor@tnetconsulting.net> - 2022-03-05 22:56 -0700
Re: current public ip blocklists Allodoxaphobia <trepidation@example.net> - 2022-05-24 13:32 +0000
Re: current public ip blocklists Supratim Sanyal <supratim@riseupdeleteme.net> - 2022-06-08 00:11 -0400
Re: current public ip blocklists rek2 hispagatos <rek2@hispagatos.org.invalid> - 2022-07-08 14:56 +0000
Re: current public ip blocklists Supratim Sanyal <supratim@riseupdeleteme.net> - 2022-06-08 00:07 -0400
csiph-web