2006-10-02 19:03:58 +00:00
|
|
|
fail2ban (0.7.1-1) unstable; urgency=low
|
|
|
|
|
|
|
|
|
|
0.7.x versions of fail2ban is a complete rewrite of the tool since 0.6, and
|
|
|
|
|
is went through restructuring of the configuration files. If you had
|
|
|
|
|
adjusted config file /etc/fail2ban.conf or /etc/defaults/fail2ban, you need
|
|
|
|
|
to adjust new config files (under /etc/fail2ban/ and /etc/default/fail2ban)
|
|
|
|
|
to take advantage of the upgrade. Now fail2ban uses split configs and local
|
|
|
|
|
modifications can be introduced in corresponding .local files. Please
|
|
|
|
|
remove old configuration file /etc/fail2ban.conf thereafter.
|
|
|
|
|
|
|
|
|
|
-- Yaroslav Halchenko <debian@onerussian.com> Tue, 12 Sep 2006 10:31:15 -0400
|
|
|
|
|
|
2006-02-10 18:08:22 +00:00
|
|
|
fail2ban (0.6.0-4) unstable; urgency=low
|
|
|
|
|
|
|
|
|
|
In this version the new section ApacheAttacks was introduced to ban IPs
|
|
|
|
|
which are found to run some known attack on the host. For now it captures
|
2006-02-16 16:19:58 +00:00
|
|
|
just awstats and mambo related attacks. To make this feature work, the bug of
|
2006-02-16 15:53:38 +00:00
|
|
|
wrongly specified timeregexp for Apache's access.log file was fixed.
|
|
|
|
|
Besides that group of log files has changed to be adm, and now they are
|
2006-02-16 16:19:58 +00:00
|
|
|
readable by the group.
|
2006-02-10 18:08:22 +00:00
|
|
|
|
|
|
|
|
-- Yaroslav Halchenko <debian@onerussian.com> Fri, 10 Feb 2006 13:05:07 -0500
|
