fail2ban 0.10.2-2.1 source package in Ubuntu
Changelog
fail2ban (0.10.2-2.1) unstable; urgency=medium * Non-maintainer upload. * Add patch from upstream to fix SyntaxError with Python 3.7. Closes: #902817 -- Mattia Rizzolo <email address hidden> Sun, 23 Sep 2018 20:14:23 +0200
Upload details
- Uploaded by:
- Yaroslav Halchenko
- Uploaded to:
- Sid
- Original maintainer:
- Yaroslav Halchenko
- Architectures:
- all
- Section:
- net
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| fail2ban_0.10.2-2.1.dsc | 1.9 KiB | 118a9d679cdb3512bd5e4be68251a21c72535d724d99a142177735274154d386 |
| fail2ban_0.10.2.orig.tar.gz | 463.6 KiB | 22744cb9f2dbc50ba50873b14dbfc9b4c078c170f4d29b2600faf3da99b4038d |
| fail2ban_0.10.2-2.1.debian.tar.xz | 30.0 KiB | 980f216b5402bc9c9314b7f0f5ad17b953e0652f47227e199c2f2a65319b0e04 |
Available diffs
- diff from 0.10.2-2 to 0.10.2-2.1 (1.8 KiB)
No changes file available.
Binary packages built by this source
- fail2ban: 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
