Package: fail2ban Version: 0.8.3-2sid1 Severity: wishlist
For diagnostics, it would be helpful if failed attempts would get into the log before a ban is made. Thus, messages such as '3rd failed attempts out of 10' for some port/app would be present in the log, and allow easier testing. Currently DEBUG log level report that it found an IP, but that is a bit detached from the rest of the information, that will allow to follow the situation, and besides, on DEBUG level there is too much clutter. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 2.6.30-bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fail2ban depends on: ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.8 register and build utility for Pyt Versions of packages fail2ban recommends: ii iptables 1.4.2-6 administration tools for packet fi ii whois 4.7.30 an intelligent whois client Versions of packages fail2ban suggests: pn mailx <none> (no description available) 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
