Date: Sat, 8 Apr 2023 16:40:15 +0200 From: Andrea Venturoli <ml@netfence.it> To: ports@freebsd.org Subject: Re: security/portsentry removal Message-ID: <328d3246-b896-2ca2-4dc1-d04bf9801c92@netfence.it> In-Reply-To: <b134b226-0eae-ec7c-b947-b04233d6faef@nomadlogic.org> References: <0bfd94dd-5be3-6461-cb98-db1a1664e220@netfence.it> <3d779c56-236d-f18b-5ac0-71f6580bb498@bluerosetech.com> <a8619455-ae93-6bfd-fc5e-b0f66d8ffde7@netfence.it> <b134b226-0eae-ec7c-b947-b04233d6faef@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/8/23 15:55, Pete Wright wrote: > would blacklistd(8) meet your requirements? I guess not. From the man: > blacklistd is a daemon similar to syslogd(8) that listens to sockets at > paths specified in the sockpathsfile for notifications from other daemons The purpose of portsentry is to listen on ports when there is no deamon there. > i use it to block ssh login spammers with decent success. I use fail2ban for that. > its part of the base system as well, but > does require pf. Which I don't use :) (I use ipfw). bye & Thanks anyway av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?328d3246-b896-2ca2-4dc1-d04bf9801c92>