Package: fail2ban Version: 0.10.3.1-1 Architecture: all Maintainer: Yaroslav Halchenko Installed-Size: 1764 Depends: python3:any (>= 3.3.2-2~), init-system-helpers (>= 1.18~), lsb-base (>= 2.0-7) Recommends: python, iptables | nftables, whois, python3-pyinotify, python3-systemd Suggests: mailx, system-log-daemon, monit, sqlite3 Filename: ./all/fail2ban_0.10.3.1-1_all.deb Size: 395492 MD5sum: 83e539dd4bc028d3504ef98073cf6a7a SHA1: 78efb2d22a846228744efead648880fcf5e9a3f9 SHA256: 0a37d866433dc66ca96e2ea942c969e8451742be64dac350e626c534cc8ce5b9 Section: net Priority: optional Homepage: http://www.fail2ban.org Description: ban hosts that cause multiple authentication errors Fail2ban monitors log files (e.g. /var/log/auth.log, /var/log/apache/access.log) and temporarily or persistently bans failure-prone addresses by updating existing firewall rules. Fail2ban allows easy specification of different actions to be taken such as to ban an IP using iptables or hostsdeny rules, or simply to send a notification email. . By default, it comes with filter expressions for various services (sshd, apache, qmail, proftpd, sasl etc.) but configuration can be easily extended for monitoring any other text file. All filters and actions are given in the config files, thus fail2ban can be adopted to be used with a variety of files and firewalls. Following recommends are listed: . - iptables/nftables -- default installation uses iptables for banning. nftables is also suported. You most probably need it - whois -- used by a number of *mail-whois* actions to send notification emails with whois information about attacker hosts. Unless you will use those you don't need whois - python3-pyinotify -- unless you monitor services logs via systemd, you need pyinotify for efficient monitoring for log files changes