Fail2ban monitors log files and temporarily or persistently bans failure-prone addresses by updating existing firewall rules. The software allows easy specification of different actions to be taken such as to ban an IP address using iptables or hostsdeny rules, or simply to send a notification email. It supports many services, and configuration can be easily extended for monitoring any other ASCII file. All filters and actions are given in the configuration files, thus fail2ban can be adopted to be used with a variety of files and firewalls.
|Tags||Internet Security Monitoring|
|Operating Systems||POSIX Unix|
Release Notes: The inode number is checked for rotation in addition to checking the first line of the file. The shutdown of the logging subsystem was moved out of Server.quit() to the end of Server.start(). This fixes the "cannot release un-acquired lock" error. The "Ban IP" command was added. Two new filters were added: lighttpd-fastcgi and php-url-fopen. The "unexpected communication error" problem was fixed by means of use_poll=False in Python 2.6 and later. Many more changes were made.
Release Notes: failtickets are processed as long as failmanager is not empty. The "pam-generic" filter and more configuration fixes were added. The PID file while started in daemon mode was fixed. The "fail2ban-client get jail logpath" was fixed. The gssftpd filter was added. The "Day/Month/Year Hour:Minute:Second" date template was added. ignoreregex processing was fixed in fail2ban-client. The ISO 8601 date/time format was added. Some logging levels and messages were added and changed. Poll is used instead of select in asyncore.loop. This should solve the "Unknown error 514".
No changes have been submitted for this release.