Date: Fri, 7 Apr 2023 19:56:13 -0700 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Andrea Venturoli <ml@netfence.it>, freebsd-ports@freebsd.org Subject: Re: security/portsentry removal Message-ID: <3d779c56-236d-f18b-5ac0-71f6580bb498@bluerosetech.com> In-Reply-To: <0bfd94dd-5be3-6461-cb98-db1a1664e220@netfence.it> References: <0bfd94dd-5be3-6461-cb98-db1a1664e220@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-04-01 10:14, Andrea Venturoli wrote: > Hello. > > I switched from Q1 to Q2 port tree today and was surprised to see this > port gone. > I try to avoid complaining, but it was marked deprecated on Feb 26 and > removed on Mar 30: I agree that a software that was abandoned in 2003 or > so should go away, but I believe this time window was too short, as > those of us using quarterly ports didn't even see the deprecation notice. > I don't think postponing the deprecation for two days would have had any > big drawback... > In any case, enough of that. > > Can anyone suggest something equivalent in the port tree? Have a look at fail2ban. It's design intent is monitoring running services, but really it's just a set of log file regex filters. Anything that logs network activity can feed it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3d779c56-236d-f18b-5ac0-71f6580bb498>