2005-07-06 23:10:26 +00:00
|
|
|
Source: fail2ban
|
|
|
|
|
Section: net
|
|
|
|
|
Priority: optional
|
2020-01-12 22:14:30 +00:00
|
|
|
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
|
|
|
|
|
Uploaders: Yaroslav Halchenko <debian@onerussian.com>
|
2018-01-22 03:45:32 +00:00
|
|
|
Build-Depends:
|
|
|
|
|
debhelper (>= 9)
|
|
|
|
|
, debhelper (>= 9.20160709) | dh-systemd
|
2018-04-04 05:06:14 +00:00
|
|
|
, dh-python
|
2018-01-22 03:45:32 +00:00
|
|
|
, python3
|
2018-04-04 05:06:14 +00:00
|
|
|
, python3-setuptools
|
2018-01-22 03:45:32 +00:00
|
|
|
, python3-pyinotify
|
2018-01-22 04:31:17 +00:00
|
|
|
, sqlite3
|
2007-11-23 16:09:34 +00:00
|
|
|
Homepage: http://www.fail2ban.org
|
2020-01-12 22:14:30 +00:00
|
|
|
Vcs-Git: https://salsa.debian.org/python-team/applications/fail2ban.git
|
|
|
|
|
Vcs-Browser: https://salsa.debian.org/python-team/applications/fail2ban
|
2018-01-22 03:45:32 +00:00
|
|
|
Standards-Version: 4.1.3
|
2005-07-06 23:10:26 +00:00
|
|
|
|
2007-11-23 16:09:34 +00:00
|
|
|
|
2005-07-06 23:10:26 +00:00
|
|
|
Package: fail2ban
|
|
|
|
|
Architecture: all
|
2014-09-12 05:08:56 +00:00
|
|
|
Depends: ${python3:Depends}, ${misc:Depends}, lsb-base (>=2.0-7)
|
2018-03-10 13:34:41 +00:00
|
|
|
Recommends: python, iptables|nftables, whois, python3-pyinotify, python3-systemd
|
2018-01-22 04:31:17 +00:00
|
|
|
Suggests: mailx, system-log-daemon, monit, sqlite3
|
2011-03-23 20:00:01 +00:00
|
|
|
Description: ban hosts that cause multiple authentication errors
|
|
|
|
|
Fail2ban monitors log files (e.g. /var/log/auth.log,
|
2006-09-05 06:10:29 +00:00
|
|
|
/var/log/apache/access.log) and temporarily or persistently bans
|
2015-08-01 01:50:00 +00:00
|
|
|
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.
|
2011-03-23 20:00:01 +00:00
|
|
|
.
|
|
|
|
|
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
|
2015-08-01 01:50:00 +00:00
|
|
|
to be used with a variety of files and firewalls. Following recommends
|
|
|
|
|
are listed:
|
|
|
|
|
.
|
2018-03-09 12:00:03 +00:00
|
|
|
- iptables/nftables -- default installation uses iptables for banning.
|
2018-04-04 05:12:18 +00:00
|
|
|
nftables is also supported. You most probably need it
|
2015-08-01 01:50:00 +00:00
|
|
|
- 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
|
