Date: Tue, 09 May 2017 10:44:21 -0500 From: Mark Felder <feld@FreeBSD.org> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Updating sshguard Message-ID: <1494344661.3162227.970925584.48647D64@webmail.messagingengine.com> In-Reply-To: <CO1PR20MB06952DEDD5493A8B52AC181280EE0@CO1PR20MB0695.namprd20.prod.outlook.com> References: <CO1PR20MB06952DEDD5493A8B52AC181280EE0@CO1PR20MB0695.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 8, 2017, at 05:21, Gerard Seibert wrote: > I was wondering if there was any news regarding updating the "sshguard" > port, specifically the "sshguard-ipfw" one? > > Version 2.0 was released March 7, 2017. The ports system still has > version 1.7.1. Moreover, the new version has a fix for the ipfw backend > on FreeBSD 11. > > -- > Carmel The version in ports works with IPFW in FreeBSD 11, you just have to manually define the sshguard table(22) in your IPFW config. I assume you're already manually choosing where in your firewall rules to block the traffic from these abusers, so just add the table creation to your IPFW config and it will work fine. As Kurt pointed out, the update is non-trivial and I haven't had enough time to dig into it. If I blindly update the port without enough testing and people install the update and it's no longer blocking abusers... that would be bad. -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1494344661.3162227.970925584.48647D64>