github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

Changelog and adjusted debian/control description to describe recommends

pull/1858/head
Yaroslav Halchenko 2015-07-31 21:50:00 -04:00
parent bceb35ab34
commit dce6e1cd3a
2 changed files with 22 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
debian/changelog vendored
View File

@ -1,3 +1,11 @@
fail2ban (0.9.3-1) unstable; urgency=medium
* Fresh upstream release
* debian/control -- adjusted description to mention what Recommends
and Suggests are good for (Closes: #767114)
-- Yaroslav Halchenko <debian@onerussian.com> Fri, 31 Jul 2015 21:34:10 -0400
fail2ban (0.9.2-1) unstable; urgency=medium
* Fresh release to celebrate jessie release and upload to unstable

20
debian/control vendored
View File

@ -17,14 +17,22 @@ Suggests: mailx, system-log-daemon, monit
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.
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.
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