Please sync fail2ban 0.8.1-5 from Debian(Unstable)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fail2ban (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: fail2ban
Explanation of the Ubuntu delta and why it can be dropped:
The only Ubuntu change was the 29th Feb patch. Fixed now also in Debian (Though this occurs 2011 the next time) :)
Changelog since current hardy version 0.31-1ubuntu1:
fail2ban (0.8.1-5) unstable; urgency=low
* manually "cherry picked" f6639981: Fixed "Feb 29" bug. Thanks to
James Andrewartha who pointed this out. Thanks to Yaroslav Halchenko
for the fix (closes: #468382)
-- Yaroslav Halchenko <email address hidden> Thu, 28 Feb 2008 19:51:53 -0500
fail2ban (0.8.1-4) unstable; urgency=low
* Debian packaging switched from git+dpatch into pure git way via
feature-
done of top of vanilla upstream, thus this is the last Debian release
prior 0.8.2 upstream release which will hopefully absorb most of the
patches
* vsftp filter anchoring
* Fix/extension of proftpd failrexes (Closes: #461412). Thanks Guido
Bozzetto
* Added ipmasq rule file (in the examples) to restart fail2ban when
iptables are wiped out (closes: #461417). Thanks Guido Bozzetto
* Extended apache-noscript filter with more file extensions and to
react to "script not found or unable to stat" log message (closes:
#456565). Thanks Tim Connors
* Fixed == bashism (Closes: #464647). Thanks Raphael Geisser
* Confirms to policy 3.7.3 (no changes)
-- Yaroslav Halchenko <email address hidden> Sat, 09 Feb 2008 22:08:55 -0500
Sync request ACK'd. Lots of other handy little fixes as well. On the other hand, I believe the next leap-day is 29th February 2012, rather than 2011.