Authors of fail2ban have provided following patches (mayby the patch
'fix-leap-year-detection-0.6.2.patch' could be used for Ubuntu 6.06?):
http://sourceforge.net/tracker/index.php?func=detail&aid=1904430&group_id=121032&atid=689044
IMHO this is a security bug and should be fixed. I didn't dare t
I have the same problem (I hadn't thought to look). Unless the logs are
manually flushed, fail2ban will be unusable until the appropriate logs
containing Feb 29 dates are rotated. This is a bit more damaging than I
initially thought. I'm also of the opinion that it should be fixed in
the distro.
-
I faund out today that fail2ban did not start. Today is 2nd of March. I
use Dapper server. smichas solution fixed it though! If fail2ban has
security issues it should be fixed since this is a LTS!
--
fail2ban doesn't handle leap years
https://bugs.launchpad.net/bugs/196854
You received this bug
it is running well since it is already 1st of March ;-)
On Sat, 01 Mar 2008, smicha wrote:
> Hi,
> I have the same problem as Eythian.
> I use the version "Fail2Ban v0.6.0"
> I have solved that problem with following trick.
> (Quick and dirty ;-)
> cat /dev/null > /var/log/auth.log
> cat /dev/
Hi,
I have the same problem as Eythian.
I use the version "Fail2Ban v0.6.0"
I have solved that problem with following trick.
(Quick and dirty ;-)
###
cat /dev/null > /var/log/auth.log
cat /dev/null > /var/log/fail2ban.log
/etc/init.d/fail2ban restart
###
Before you "flush" the a
This bug was fixed in the package fail2ban - 0.8.1-3ubuntu1
---
fail2ban (0.8.1-3ubuntu1) hardy; urgency=low
* Added 11_fix_leap_year.dpatch to fix leap year issues. (LP: #196854)
-- Chuck Short <[EMAIL PROTECTED]> Fri, 29 Feb 2008 16:46:26 -0500
** Changed in: fail2ban (Ubuntu
** Changed in: fail2ban (Ubuntu)
Status: New => Confirmed
--
fail2ban doesn't handle leap years
https://bugs.launchpad.net/bugs/196854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
