Your message dated Thu, 18 May 2006 22:26:49 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing pending (missed changelog), and fixed by NMU bugs
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 ---
clone 356112 -1
reopen -1 =
tags -1 - fixed pending
tags -1 + forwarded
merge -1 363391
thanks
All the bugs are believed to be fixed in the recent upload which was NMU
(sponsored) and stepped through 1 changelog entry, so didn't close the
bugs properly. Relevant changelog entries:
Bug 356112 supposed to be cloned and merged with forwarded to upstream locale
bug
in case if you reply, please exclude [EMAIL PROTECTED] from
recepients
fail2ban (0.6.1-3) unstable; urgency=low
* Fixed vsftpd failregexp (closes: #366687)
* Started to use dpatch
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Wed, 10 May 2006 11:45:57 -0400
fail2ban (0.6.1-2) unstable; urgency=low
* Assigned maxreinits to 1000 to be reasonable since otherwise logfile grows
indefinetly if there is a real problem on the system (closes: #359218)
* Adjusted debian/{copyright,watch}
* New version of init.d script (Thanks to Aaron Isotton) (closes: #364278)
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Mon, 27 Mar 2006 12:55:39 -0500
fail2ban (0.6.1-1) unstable; urgency=low
* New upstream release
* In config file added fwchain to ease switching to another input chain
(closes: #357164)
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Sat, 18 Mar 2006 23:11:53 -0500
fail2ban (0.6.0-8) unstable; urgency=low
* Minor adjustments to reduce the deviation from the upstream code
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Sat, 11 Mar 2006 00:48:14 -0500
fail2ban (0.6.0-7) unstable; urgency=low
* Fixed a typo in failregex for SSH section (closes: #356112)
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--- End Message ---
