Your message dated Thu, 03 Aug 2006 09:19:03 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367990: fixed in fail2ban 0.6.1-10
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.6.0-6
Severity: important
I have some servers&routers with logcheck&fail2ban installed.
Until 0.6.0-6, fail2ban worked well and logcheck reported only 5 or less
breakin attempts from variour IPs on the Internet. This was a great
help and convenience from fail2ban. With 0.6.0-6, logcheck started to
report that fail2ban went out of effect and whoever could again attempt
as many breakins as he wishes. And ban/unban records stopped to appear
in fail2ban.log.
I use certain set of iptables rules on each host, but fail2ban was able
to add its chain to these rules without any problems. Don't know what to
do next except rollback to 0.6.0-5.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.1
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Versions of packages fail2ban depends on:
ii iptables 1.3.3-2 Linux kernel 2.4+ iptables adminis
ii python 2.4.2-0ubuntu2 An interactive high-level object-o
fail2ban recommends no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.6.1-10
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.6.1-10.dsc
to pool/main/f/fail2ban/fail2ban_0.6.1-10.dsc
fail2ban_0.6.1-10.tar.gz
to pool/main/f/fail2ban/fail2ban_0.6.1-10.tar.gz
fail2ban_0.6.1-10_all.deb
to pool/main/f/fail2ban/fail2ban_0.6.1-10_all.deb
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, 6 Jul 2006 20:19:54 -0400
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.6.1-10
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: 363391 367990
Changes:
fail2ban (0.6.1-10) unstable; urgency=low
.
* Adjusted to comply with recent changes in debian python policy and use
pycentral to byte compile modules
* Filtered out empty entries for ignoreip to reduce confusing WARNING log
message
* Added configuration parameter "locale" to specify LC_TIME for time
pattern matching (closes: #367990,363391)
* Verbosity is chosen to be max between cmdline parameters and config file
Files:
7507a5165df582c57b565b15a0e17d1f 673 net optional fail2ban_0.6.1-10.dsc
065676e58571d83b37eeb866214e4378 92007 net optional fail2ban_0.6.1-10.tar.gz
de47f19e0a93ac5b84bc1ccb537658b6 51794 net optional fail2ban_0.6.1-10_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFE0WQCLz4Gnv7CP7IRAonUAKCAtYaIOE+QP6MYVgMa9gNvx4ilNACglg4F
//XrQ/p0EONZw9KU7ZNRTbk=
=ULwt
-----END PGP SIGNATURE-----
--- End Message ---
