Your message dated Sun, 21 Aug 2005 11:49:40 -0400
with message-id <[EMAIL PROTECTED]>
and subject line bugs are closed in -3
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Aug 2005 19:47:56 +0000
>From [EMAIL PROTECTED] Thu Aug 18 12:47:56 2005
Return-path: <[EMAIL PROTECTED]>
Received: from iron.libaux.ucsf.edu [128.218.15.248]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E5qMm-0002Uc-00; Thu, 18 Aug 2005 12:47:56 -0700
Received: from ross by iron.libaux.ucsf.edu with local (Exim 4.52)
id 1E5qMH-0006HA-3M; Thu, 18 Aug 2005 12:47:25 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ross Boylan <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fail2ban: fuller documentation would be helpful
X-Mailer: reportbug 3.15
Date: Thu, 18 Aug 2005 12:47:25 -0700
Message-Id: <[EMAIL PROTECTED]>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
X-SA-Exim-Scanned: No (on iron.libaux.ucsf.edu); SAEximRunCond expanded to false
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: fail2ban
Version: 0.5.2-2
Severity: wishlist
Thanks for making this available; I've been wanting something like this.
1. It would be good to include the upstream README.
2. The main page for fail2ban should have "See also" section for the
conf file, and vice-versa. Or you could just delete the latter, since
it's just a pointer to the conf file anyway.
3. Perhaps you should note somewhere (README.Debian) that the handling
of apache is off by default. The setting itself is fine by me.
4. I'm unclear about the length of time over which the indicated
number of failures can occur. At the moment it looks as if it's
infinite, i.e., as long as the log file is around. I assume it's not,
but can't tell how it does work.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (600, 'testing'), (500, 'stable'), (50, 'unstable'), (40,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27adnvcd
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages fail2ban depends on:
ii iptables 1.3.1-2 Linux kernel 2.4+ iptables adminis
ii python 2.3.5-3 An interactive high-level object-o
fail2ban recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 323840-done) by bugs.debian.org; 21 Aug 2005 15:50:10 +0000
>From [EMAIL PROTECTED] Sun Aug 21 08:50:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from washoe.rutgers.edu [165.230.95.67]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E6s5K-0007pz-00; Sun, 21 Aug 2005 08:50:10 -0700
Received: from yoh by washoe.rutgers.edu with local (Exim 4.52)
id 1E6s4q-0000Ik-8m; Sun, 21 Aug 2005 11:49:40 -0400
Date: Sun, 21 Aug 2005 11:49:40 -0400
From: Yaroslav Halchenko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: bugs are closed in -3
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua"
Content-Disposition: inline
X-Image-Url: http://www.onerussian.com/img/yoh.png
X-PGP-Key: http://www.onerussian.com/gpg-yoh.asc
X-fingerprint: 3BB6 E124 0643 A615 6F00 6854 8D11 4563 75C0 24C8
User-Agent: mutt-ng devel-20050619 (Debian)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 3
--SUOF0GtieIMvvwua
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Bugs are closed in -3 (which was skipped from upload sequence)
fail2ban (0.5.2-3) unstable; urgency=3Dlow
* Fixed errata in /etc/default/fail2ban (closes: #323451)
* Fixed handling of SYSLOG logging target. Now it can log to any syslog
target and facility as directed by the config (revisions 160:166 patch
from syslog branch) (closes: #323543)
* Included upstream README and TODO
* Mentioned in README.Debian that apache section is disabled by default
* Adjusted man pages to cross-reference each other
* Moved fail2ban man page under section 8 as in upstream
* Introduced findtime configuration variable to control the lifetime
of caught "failed" log entries (closes: #323840)
--=20
.-.
=3D------------------------------ /v\ ----------------------------=3D
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--SUOF0GtieIMvvwua
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFDCKKTjRFFY3XAJMgRAnSmAKCRVOxrmIIbQv5C8lEYVt16CdrLoQCbBhFZ
5PEGm7v6M8Bg7V4FNrQlm/Q=
=HKdk
-----END PGP SIGNATURE-----
--SUOF0GtieIMvvwua--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
