fail2ban v0.5.1 has been
released. From the announcement on the Linux-Announce mailing list
for Sat, July 23, 2005:
This release fixes bugs discovered in 0.5.0
and add multi targets for the log output including syslog. Default
config creates an iptables chain for each section. ...
fail2ban-0.5.1 is still an unstable version but should work
perfectly.
.debs are available
here.
Here is the Changelog section for v0.5.1:
ver. 0.5.1 (2005/07/23) - beta
----------
- Fixed bugs #1241756, #1239557
- Added log targets in configuration file. Removed -l option
- Changed iptables rules in order to create a separated chain for
each section
- Fixed static banList in firewall.py
- Added an initd script for Debian. Thanks to Yaroslav
Halchenko
- Check for obsolete files after install
v0.5.0 has been running fine on my
linode.com machine (on which this weblog
and my other servers run), and I did the wget and `dpkg -i` for the
v0.5.1 .deb today. Install appeared to go without a hitch and
fail2ban stopped and restarted.
Quoting the fail2ban 'About' section on the site 'Fail2Ban scans
log files like /var/log/pwdfail or /var/log/apache/error_log and
bans IP that makes too many password failures. It updates firewall
rules to reject the IP address. It needs log4py.' I have it running
to drop the IP address, not do an `iptables [blahblah]
REJECT`.