Your message dated Fri, 12 May 2006 02:17:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#359177: fixed in logwatch 7.3-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: logwatch
Version: 7.1-1
Severity: wishlist
Tags: patch
User-Agent: mutt-ng/devel-r782 (Debian)
Dear Debian Developer and Upstream Authors of the LogWatch,
Please find attached scripts/configs for including reports about
fail2ban(http://fail2ban.sourceforge.net/) activity. As the starting
point I took configs provided by "Rarig, Harry" <[EMAIL PROTECTED]>
and logwatch ssh script and also had to generate a new apply*date
script, since the time format in fail2ban logs seems to be not covered
by any present in the shipped logwatch.
I am emailing both DD and upstream since version shipped by Debian (7.1)
seems to be not the most recent stable upstream, and I believe that if
you decide to include the scripts, they will be included just in the
development branch. Dear DD, I would really appreciate if you include
the scripts in logwatch package meanwhile -- quite a few users would
benefit from that.
Here are examples of reports generated with provided scripts:
Verbose (Detail >=10):
--------------------- fail2ban-messages Begin ------------------------
Banned services with Fail2Ban: Bans:Unbans
SSH: [ 6:6 ]
210.103.124.7 1:1
Failed 5 times
210.14.28.59 1:1
Failed 5 times
165.230.95.72 (tractatus.rutgers.edu) 4:4
Failed 5 5 5 5 times
VSFTPD: [ 1:1 ]
72.9.234.170 (star.dnsprotect.com) 1:1
**Unmatched Entries**
2006-03-05 18:13:24,365 WARNING: is not a valid IP address
2006-03-12 07:50:09,404 WARNING: is not a valid IP address
<SKIPPED>
Regular (Detail==5)
--------------------- fail2ban-messages Begin ------------------------
Banned services with Fail2Ban: Bans:Unbans
SSH: [ 6:6 ]
210.103.124.7 1:1
210.14.28.59 1:1
165.230.95.72 (tractatus.rutgers.edu) 4:4
VSFTPD: [ 1:1 ]
72.9.234.170 (star.dnsprotect.com) 1:1
**Unmatched Entries**
2006-03-05 18:13:24,365 WARNING: is not a valid IP address
2006-03-12 07:50:09,404 WARNING: is not a valid IP address
<SKIPPED>
Minimal verbosity (Detail == 0):
--------------------- fail2ban-messages Begin ------------------------
Banned services with Fail2Ban: Bans:Unbans
SSH: [ 6:6 ]
VSFTPD: [ 1:1 ]
---------------------- fail2ban-messages End -------------------------
-- 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.13.4
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages logwatch depends on:
ii gawk 1:3.1.5-1 GNU awk, a pattern scanning and pr
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii perl 5.8.7-10 Larry Wall's Practical Extraction
logwatch recommends no packages.
-- no debconf information
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
fail2ban.logwatch.v5.tgz
Description: application/tar-gz
--- End Message ---
--- Begin Message ---
Source: logwatch
Source-Version: 7.3-1
We believe that the bug you reported is fixed in the latest version of
logwatch, which is due to be installed in the Debian FTP archive:
logwatch_7.3-1.diff.gz
to pool/main/l/logwatch/logwatch_7.3-1.diff.gz
logwatch_7.3-1.dsc
to pool/main/l/logwatch/logwatch_7.3-1.dsc
logwatch_7.3-1_all.deb
to pool/main/l/logwatch/logwatch_7.3-1_all.deb
logwatch_7.3.orig.tar.gz
to pool/main/l/logwatch/logwatch_7.3.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.
Willi Mann <[EMAIL PROTECTED]> (supplier of updated logwatch 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: Sun, 19 Mar 2006 18:29:50 +0100
Source: logwatch
Binary: logwatch
Architecture: source all
Version: 7.3-1
Distribution: unstable
Urgency: low
Maintainer: Willi Mann <[EMAIL PROTECTED]>
Changed-By: Willi Mann <[EMAIL PROTECTED]>
Description:
logwatch - log analyser with nice output written in Perl
Closes: 298275 356815 359177
Changes:
logwatch (7.3-1) unstable; urgency=low
.
* New upstream release
- this should fix the reports about exim "Unmatched Entries".
closes: #298275.
* Add another unmatched entry for imapd - thanks again to Richard Burton
for the report. closes: #356815
* Add some unmatched lines for smartd.
* remove no longer needed debian-specific logfile definitions. merged
upstream.
* add fail2ban scripts from Yaroslav Halchenko. closes: #359177
* policy version 3.7.0.0, no changes
Files:
070470b3b5bd69d38c21837b1257f5d5 560 admin optional logwatch_7.3-1.dsc
4a788202618a5a849b206c71c6b1766f 226362 admin optional logwatch_7.3.orig.tar.gz
0c7538c1aee555906c865ae7c1eaed60 13782 admin optional logwatch_7.3-1.diff.gz
c7c7394cb7c583eebf1b0b7a309fca99 236602 admin optional logwatch_7.3-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEZFIyliSD4VZixzQRAlA/AJ4l//isF7jtAA2Ekd5t7U6shO8f9QCfVLsB
hLF3hWxsmQ5JXAu9BfgzgwA=
=N8RK
-----END PGP SIGNATURE-----
--- End Message ---
