mirror of
https://github.com/fail2ban/fail2ban.git
synced 2026-11-21 15:42:28 +00:00
58 lines
2 KiB
Text
58 lines
2 KiB
Text
Source: fail2ban
|
|
Section: net
|
|
Maintainer: Debian Python Team <team+python@tracker.debian.org>
|
|
Uploaders:
|
|
Yaroslav Halchenko <debian@onerussian.com>,
|
|
Sylvestre Ledru <sylvestre@debian.org>,
|
|
Build-Depends:
|
|
debhelper-compat (= 13),
|
|
dh-sequence-cruft,
|
|
dh-sequence-python3,
|
|
pkgconf,
|
|
python3,
|
|
python3-pyinotify,
|
|
python3-setuptools,
|
|
sqlite3,
|
|
systemd-dev,
|
|
Homepage: https://www.fail2ban.org
|
|
Vcs-Git: https://salsa.debian.org/python-team/packages/fail2ban.git
|
|
Vcs-Browser: https://salsa.debian.org/python-team/packages/fail2ban
|
|
Standards-Version: 4.7.4
|
|
|
|
Package: fail2ban
|
|
Architecture: all
|
|
Depends:
|
|
python3-systemd,
|
|
${misc:Depends},
|
|
${python3:Depends},
|
|
Recommends:
|
|
nftables | iptables,
|
|
python3-pyinotify,
|
|
whois,
|
|
Suggests:
|
|
mailx,
|
|
monit,
|
|
sqlite3,
|
|
system-log-daemon,
|
|
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, 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 supported. 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
|