Package: fail2ban
Version: 0.8.4-3
Severity: normal
*** Please type your report below this line ***
Fail2ban counts entries in various logs, but does not react when it gets
last message repeated x times
Discovered when a student tested fail2ban, and it did not ban him
despite many wrong passwords. Syslog logged only the first attempt,
and then resorted to "last message repeated x times"
Ideal fix: have fail2ban understand "last message repeated" and add up
the numbers.
Minimal fix: Document that the user may want to turn off such line
compression. Some recent versions of syslog can do that. But fixing
fail2ban would be better. log compression is useful, and a
program that calls itself a "log parser" ought to understand.
Helge Hafting
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable'),
(700, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fail2ban depends on:
ii lsb-base 3.2-27 Linux Standard Base 3.2
init scrip
ii python 2.6.6-3+squeeze6 interactive high-level
object-orie
ii python-central 0.6.16+nmu1 register and build utility
for Pyt
Versions of packages fail2ban recommends:
ii iptables 1.4.10-1 administration tools for
packet fi
ii whois 5.0.11 an intelligent whois client
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent
ii mailx 1:20081101-2 Transitional package for
mailx ren
pn python-gamin <none> (no description available)
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org