Package: fail2ban
Version: 0.8.1-4
Severity: normal
fail2ban cannot recognize leap-year day. You can find this problem as
follows:
1. Up loglevel to 4 (DEBUG) on your fail2ban.conf
2. Following message is shown at your fail2ban.log
2008-02-29 06:26:37,548 fail2ban.filter : DEBUG Found a match but no valid
date/time found for Feb 29 05:14:55 osdnns sshd[3776]: Invalid user users
from 74.205.125.93
. Please contact the author in order to get support for this format
Maybe it causes at "server/datestrptime.py". python time.strptime() cannot
recognize reap-year day when the year has not specified as follows:
% python
Python 2.4.4 (#2, Apr 5 2007, 20:11:18)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> time.strptime("Feb 29 05:14:55", "%b %d %H:%M:%S")
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.4/_strptime.py", line 425, in strptime
julian = datetime_date(year, month, day).toordinal() - \
ValueError: day is out of range for month
Standard syslogd does not recorded year. Therefore fail2ban failed to
recognize leap-year day.
I've reported this problem to sf.net tracker:
https://sourceforge.net/tracker/index.php?func=detail&aid=1904430&group_id=121032&atid=689044
Thanks,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
