Your message dated Thu, 04 Jan 2007 22:47:02 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#404060: fixed in fail2ban 0.7.6-1 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: fail2ban Version: 0.7.5-2 Severity: important Since the upgrade to 0.7, fail2ban does not ban vsftpd erroneous logins. The severity I've chosen is important because ssh bad login attempts are correctly stopped by fail2ban, so it is not critical. As stated in /etc/fail2ban/jail.conf, I created a jail.local; it's just a copy of jail.conf, but with vsftpd section enabled. Don't know if I need something else to make it work... I'm willing to perform any necessary test to solve the problem, don't hesitate in contacting me about this. Thanks Antonio -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (700, 'testing'), (650, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-vserver-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ Versions of packages fail2ban depends on: ii iptables 1.3.6.0debian1-5 administration tools for packet fi ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii python 2.4.4-1 An interactive high-level object-o ii python-central 0.5.12 register and build utility for Pyt ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
--- End Message ---
--- Begin Message ---Source: fail2ban Source-Version: 0.7.6-1 We believe that the bug you reported is fixed in the latest version of fail2ban, which is due to be installed in the Debian FTP archive: fail2ban_0.7.6-1.diff.gz to pool/main/f/fail2ban/fail2ban_0.7.6-1.diff.gz fail2ban_0.7.6-1.dsc to pool/main/f/fail2ban/fail2ban_0.7.6-1.dsc fail2ban_0.7.6-1_all.deb to pool/main/f/fail2ban/fail2ban_0.7.6-1_all.deb fail2ban_0.7.6.orig.tar.gz to pool/main/f/fail2ban/fail2ban_0.7.6.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko <[EMAIL PROTECTED]> (supplier of updated fail2ban package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 4 Jan 2007 15:24:52 -0500 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.7.6-1 Distribution: unstable Urgency: low Maintainer: Yaroslav Halchenko <[EMAIL PROTECTED]> Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]> Description: fail2ban - bans IPs that cause multiple authentication errors Closes: 404060 404487 404921 Changes: fail2ban (0.7.6-1) unstable; urgency=low . * New upstream release, which incorporates fixes introduced in 3~pre non-released versions (which were suggested to the users to overcome problems reported in bug reports). In particular attention should be paid to upstream changelog entries - Several "failregex" and "ignoreregex" are now accepted. Creation of rules should be easier now. This is an alternative solution to 'multiple <HOST>' entries fix, which is not applied to this shipped version - pay caution if upgrading from 0.7.5-3~pre? - Allow comma in action options. The value of the option must be escaped with " or '. That allowed to implement requested ability to ban multiple ports at once (See 373592). README.Debian and jail.conf adjusted to reflect possible use of iptables-mport - Now Fail2ban goes in /usr/share/fail2ban instead of /usr/lib/fail2ban. This is more compliant with FHS. Patch 00_share_insteadof_lib no longer applied * Refactored installed by debian package jail.conf: - Added option banaction which is to incorporate banning agent (usually some flavor of iptables rule), which can then be easily overriden globally or per section - Multiple actions are defined as action_* to serve as shortcuts * Initd script was modified to inform about present socket file which would forbid fail2ban-server from starting * Adjusted default log file for postfix to be /var/log/mail.log (Closes: #404921) . fail2ban (0.7.5-3~pre6) unstable; urgency=low . * Fail2ban now bans vsftpd logins (corrected logfile path and failregex) (Closes: #404060) * Made fail2ban-server tollerate multiple <HOST> entries in failregex * Moved call to dh_pycentral before dh_installinit * Removed unnecessary call of dh_shlibdeps * Added filter ssh-ddos to fight DDOS attacks. Must be used with caution if there is a possibility of valid clients accessing through unreliable connection or faulty firewall (Closes: #404487) * Not applying patch any more for rigid python2.4 - it is default now in sid/etch * Moving waiting loop for fail2ban-server to stop under do_stop function, so it gets invoked by both 'restart' and 'stop' commands * do_status action of init script is now using 'fail2ban-client ping' instead of '... status' since we don't really use returned status information, besides the return error code Files: e69fc0db6f06eb618a467840054c2b93 694 net optional fail2ban_0.7.6-1.dsc f9cc999177657c209d6c4c206e20b598 55454 net optional fail2ban_0.7.6.orig.tar.gz 286573b35c89087742e5039aac4d4469 21518 net optional fail2ban_0.7.6-1.diff.gz 143efc04900a873d47ce18204ea4f349 67408 net optional fail2ban_0.7.6-1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFnWZWjRFFY3XAJMgRAg3ZAKDDk1ZX39gWEgenlR4riKZS/MEH6wCgmYkx UDryigRfHUeUE4ry8/h7TwE= =auNx -----END PGP SIGNATURE-----
--- End Message ---
