Your message dated Tue, 29 Nov 2011 04:18:34 +0000
with message-id <[email protected]>
and subject line Bug#648324: fixed in fail2ban 0.8.6-1
has caused the Debian Bug report #648324,
regarding fail2ban: Problem with time format in proftpd.log (polish version)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
648324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648324
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.4-3
Severity: normal
I have problem with proftpd time format in proftpd.log.
I'm using polish version debian and proftpd. In date are included polish
letter. Maybe the problem is presence polish letters in month names?
In fail2ban.log:
2011-10-31 22:57:55,709 fail2ban.filter : DEBUG Found a match for ' linux
proftpd[4165] 127.0.1.1 (::ffff:80.55.50.174[::ffff:80.55.50.174]): USER
fail2bantest: no such user
' but no valid date/time found for 'paĹş 31 22:57:54'. Please contact the
author in order to get support for this format
Please add support for this date/ time format :)
-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fail2ban depends on:
ii lsb-base 3.2-23.2squeeze1 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.8-3 administration tools for packet fi
ii whois 5.0.10 an intelligent whois client
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent
pn python-gamin <none> (no description available)
-- Configuration Files:
/etc/fail2ban/jail.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.8.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.8.6-1.diff.gz
to main/f/fail2ban/fail2ban_0.8.6-1.diff.gz
fail2ban_0.8.6-1.dsc
to main/f/fail2ban/fail2ban_0.8.6-1.dsc
fail2ban_0.8.6-1_all.deb
to main/f/fail2ban/fail2ban_0.8.6-1_all.deb
fail2ban_0.8.6.orig.tar.gz
to main/f/fail2ban/fail2ban_0.8.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.8
Date: Mon, 28 Nov 2011 22:27:18 -0500
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.8.6-1
Distribution: unstable
Urgency: low
Maintainer: Yaroslav Halchenko <[email protected]>
Changed-By: Yaroslav Halchenko <[email protected]>
Description:
fail2ban - ban hosts that cause multiple authentication errors
Closes: 648324
Changes:
fail2ban (0.8.6-1) unstable; urgency=low
.
* [1efe1bc] Fresh upstream release (Closes: #648324)
* Boosted policy compliance to 3.9.2 -- no changes
* Adjusted debian/watch to fetch tarballs from github
Checksums-Sha1:
451dc5cc2913497320dc52cc4eb17678ae9bdb70 1214 fail2ban_0.8.6-1.dsc
f05df2ac989aec47cc40830aafcd6c945ec575ea 107029 fail2ban_0.8.6.orig.tar.gz
91d2466f2cfa2cb58c94c4c480f6001c84632be3 26055 fail2ban_0.8.6-1.diff.gz
4e87049d88ddf7676053d667bc808d6f0a86fa95 99100 fail2ban_0.8.6-1_all.deb
Checksums-Sha256:
cc3455eeb187c465cc678d7f7fdb3c8baff3a3c77cfdb9837916e3481ba74bf8 1214
fail2ban_0.8.6-1.dsc
24d02422c55f1b7d92bea30a7dde6f72f280eadf09d478fcca8b1dd40fb4e914 107029
fail2ban_0.8.6.orig.tar.gz
947726ca9e0c117699095e0b3212f3573591bf83795f3b9a85993f13ed750220 26055
fail2ban_0.8.6-1.diff.gz
c5576c7cb622e597bde42c5ae84382d8321de981004b1d2e4738b1021302c2a8 99100
fail2ban_0.8.6-1_all.deb
Files:
4c8f701520ca8ee66ddd32f0670a5b64 1214 net optional fail2ban_0.8.6-1.dsc
a5f08a67fe6bfb0580043d90c6f81cfd 107029 net optional fail2ban_0.8.6.orig.tar.gz
64ec1f602cc2b8b7db005d88d59f890f 26055 net optional fail2ban_0.8.6-1.diff.gz
ff7425b340f375ecdfd91791b7fcf13e 99100 net optional fail2ban_0.8.6-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk7UWvsACgkQjRFFY3XAJMgT/gCaA7MY1Pn+TvQabgzQQvtZTra9
31wAoIvfmv+jEaa/hlCMBJ0ZbU57EaVK
=jPcY
-----END PGP SIGNATURE-----
--- End Message ---
