From owner-freebsd-ports-bugs@freebsd.org Wed Dec 7 15:30:55 2016 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F59AC6BFC2 for ; Wed, 7 Dec 2016 15:30:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4E6DB1258 for ; Wed, 7 Dec 2016 15:30:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB7FUshH093307 for ; Wed, 7 Dec 2016 15:30:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215120] security/py-fail2ban: fail2ban fails to ban IP address Date: Wed, 07 Dec 2016 15:30:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: olaf@zaplinski.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 15:30:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215120 Bug ID: 215120 Summary: security/py-fail2ban: fail2ban fails to ban IP address Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: olaf@zaplinski.de CC: theis@gmx.at Flags: maintainer-feedback?(theis@gmx.at) CC: theis@gmx.at I just (re-) installed this port and added these files. *** fail2ban.local: [Definition] loglevel =3D DEBUG *** jail.local: [DEFAULT] # -- 3 Tage: bantime =3D 259200 [bsd-sshd] enabled =3D true port =3D ssh filter =3D bsd-sshd logpath =3D /var/log/auth.log banaction =3D zap-em *** action.d/zap-em.conf: [Definition] actionban =3D ipfw table 1 add actionunban =3D ipfw table 1 delete Interesting is the log file's last line here: 2016-12-07 17:28:39,840 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'addaction', 'zap-em'] 2016-12-07 17:28:39,840 fail2ban.CommandAction [17952]: DEBUG Set action zap-em timeout =3D 60 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Set actionstart =3D 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Set action= ban =3D 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Set actionunban =3D 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Set actioncheck =3D 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Set action= stop =3D 2016-12-07 17:28:39,841 fail2ban.CommandAction [17952]: DEBUG Created 2016-12-07 17:28:39,842 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'actionban', 'ipfw table 1 add = '] 2016-12-07 17:28:39,842 fail2ban.CommandAction [17952]: DEBUG Set action= ban =3D ipfw table 1 add 2016-12-07 17:28:39,842 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'actionunban', 'ipfw table 1 delete '] 2016-12-07 17:28:39,842 fail2ban.CommandAction [17952]: DEBUG Set actionunban =3D ipfw table 1 delete 2016-12-07 17:28:39,843 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'port', 'ssh'] 2016-12-07 17:28:39,843 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'protocol', 'tcp'] 2016-12-07 17:28:39,844 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'name', 'bsd-sshd'] 2016-12-07 17:28:39,844 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'chain', 'INPUT'] 2016-12-07 17:28:39,844 fail2ban.transmitter [17952]: DEBUG Command: ['set', 'bsd-sshd', 'action', 'zap-em', 'bantime', '259200'] 2016-12-07 17:28:39,845 fail2ban.transmitter [17952]: DEBUG Command: ['start', 'bsd-sshd'] 2016-12-07 17:28:39,845 fail2ban.jail [17952]: INFO Jail 'bsd-sshd' started 2016-12-07 17:28:39,846 fail2ban.filterpyinotify[17952]: DEBUG pyinotifier started for bsd-sshd. 2016-12-07 17:28:39,847 fail2ban.action [17952]: DEBUG 2016-12-07 17:28:39,851 fail2ban.action [17952]: DEBUG Nothing to= do The last line is missing in my Linux server's fail2ban log, and there fail2= ban does a great job. But this FreeBSD port does not block sshd abusers at all. --=20 You are receiving this mail because: You are the assignee for the bug.=