2005-07-06 23:10:26 +00:00
|
|
|
Source: fail2ban
|
|
|
|
Section: net
|
|
|
|
Priority: optional
|
2005-07-07 01:52:07 +00:00
|
|
|
Maintainer: Yaroslav Halchenko <debian@onerussian.com>
|
2014-09-12 05:08:56 +00:00
|
|
|
Build-Depends: debhelper (>= 9), python3, python3-pyinotify, dh-systemd
|
2007-11-23 16:09:34 +00:00
|
|
|
Homepage: http://www.fail2ban.org
|
2012-01-07 23:54:34 +00:00
|
|
|
Vcs-Git: git://github.com/fail2ban/fail2ban.git
|
|
|
|
Vcs-Browser: http://github.com/fail2ban/fail2ban
|
2014-10-28 02:02:23 +00:00
|
|
|
Standards-Version: 3.9.6
|
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)
|
2015-04-27 01:59:21 +00:00
|
|
|
Recommends: python, iptables, whois, python3-pyinotify, python3-systemd
|
2015-04-26 17:17:01 +00:00
|
|
|
Suggests: mailx, system-log-daemon, monit
|
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:
|
|
|
|
.
|
|
|
|
- iptables -- default installation uses iptables for banning. 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
|