a b c d e f g h i j k l m n o p q r s t u v w x y z
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, 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. Following recommends
are listed:
.
- iptables/nftables -- default installation uses iptables for banning.
nftables is also suported. 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
Description: bans IPs that cause multiple authentication errors
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. The
software was completely rewritten at version 0.7.0 and now 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. Currently, by default, supports ssh/apache/vsftpd
but configuration can be easily extended for monitoring any other ASCII
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.
--- 258354 Thu Jan 1 00:00:00 1970
+++ 40321 Thu Jan 1 00:00:00 1970
@@ -1,22 +1,12 @@
-ban hosts that cause multiple authentication errors
- Fail2ban monitors log files (e.g. /var/log/auth.log,
+bans IPs that cause multiple authentication errors
+ 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
+ failure-prone addresses by updating existing firewall rules. The
- allows easy specification of different actions to be taken such as to ban
+ software was completely rewritten at version 0.7.0 and now allows
- an IP using iptables or hostsdeny rules, or simply to send a notification
+ easy specification of different actions to be taken such as to ban an
- email.
+ IP using iptables or hostsdeny rules, or simply to send a
- .
+ notification email. Currently, by default, supports ssh/apache/vsftpd
- By default, it comes with filter expressions for various services
+ but configuration can be easily extended for monitoring any other ASCII
- (sshd, apache, qmail, proftpd, sasl etc.) but configuration can be
+ file. All filters and actions are given in the config files, thus
- easily extended for monitoring any other text file. All filters and
+ fail2ban can be adopted to be used with a variety of files and
- actions are given in the config files, thus fail2ban can be adopted
+ firewalls.
- 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 suported. 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