Your message dated Fri, 08 Dec 2006 02:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396668: fixed in fail2ban 0.7.5-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: fail2ban
Version: 0.6.1-11
Severity: minor
The default configuration uses
# Option: from
# Notes.: e-mail address of the sender.
# Values: MAIL Default: fail2ban
#
from = [EMAIL PROTECTED]
2 issues with this.
First, fail2ban is not a user on the system. As a result, the mail
may be rejected by sender verification. I see several possible approaches:
a) change the sender to a real user, like root
b) create a fail2ban user
c) create some kind of alias so that fail2ban is acceptable
d) document the current behavior and options for dealing with it
e) decide that someone who is verifying senders on their own system
is being perverse, and do nothing. However, note that such checks can
prevent spoofing if users are not trusted, and that fail2ban email
might go to some machine other than the one originating the message.
Second, the use of @localhost seems like asking for trouble. If it's
preserved, but the message is routed to another machine, this will be
disorienting at best. I'm not even sure it's a legitmate domain for
an email address. It may be that all MTA's will clean this up, but
they would probably clean up an unqualified name (just fail2ban
without @anything) as well.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages fail2ban depends on:
ii iptables 1.3.5.0debian1-1 Linux kernel 2.4+ iptables adminis
ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip
ii python 2.4.3-11 An interactive high-level object-o
ii python-central 0.5.6 register and build utility for Pyt
fail2ban recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.7.5-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.7.5-1.diff.gz
to pool/main/f/fail2ban/fail2ban_0.7.5-1.diff.gz
fail2ban_0.7.5-1.dsc
to pool/main/f/fail2ban/fail2ban_0.7.5-1.dsc
fail2ban_0.7.5-1_all.deb
to pool/main/f/fail2ban/fail2ban_0.7.5-1_all.deb
fail2ban_0.7.5.orig.tar.gz
to pool/main/f/fail2ban/fail2ban_0.7.5.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.7
Date: Thu, 7 Dec 2006 20:19:09 -0500
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.7.5-1
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: 377711 396668 398739 400162 400278
Changes:
fail2ban (0.7.5-1) unstable; urgency=low
.
* New upstream release which fixes next issues
+ Socket parameter not work with other path (Closes: #400162)
+ fail2ban does not start with /etc/init.d/fail2ban start but
with fail2ban-client start (Closes: #400278)
* Removed obsolete patches left from 0.6
* Adjusted wsftpd patch to use <HOST> tag to be in line with the other
filter definitions
.
fail2ban (0.7.4-5) unstable; urgency=low
.
* Added Suggests on mailx and relevant comments in README.Debian about
invoking mail actions (closes: #396668)
* Removed obsolete entries in TODO and README
* README.Debian describes the use of interpolations vs parameters passed
from jail.{conf,local} into an action definitions (closes:
#398739)
* Initial version of postfix filter has been present in 0.7 (closes:
#377711)
* Removed Uploaded field from control since I am a DD now. Big thanks to
Barak Pearlmutter for being the sponsor of my packages for few years.
.
fail2ban (0.7.4-4) unstable; urgency=low
.
* Added debian/backports to contain patches necessary for backporting. It
gets used by pbuilder-ssh to create package for backports.org
Files:
830e0a95a998e1f3d79634170f3d7721 694 net optional fail2ban_0.7.5-1.dsc
36e65b8effcfd4f4a437d214613eb916 46075 net optional fail2ban_0.7.5.orig.tar.gz
e3d511f14f636ca4c439066f4b82eace 17985 net optional fail2ban_0.7.5-1.diff.gz
8fb2a0cb89d68a68490a4a68c3a298df 62216 net optional fail2ban_0.7.5-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFeM+CjRFFY3XAJMgRArrRAJ9OEEXgsZUompVroALKWAGdcS78twCfYr95
QjfEXTz4KmyiXsp5H+0tWIk=
=PpJh
-----END PGP SIGNATURE-----
--- End Message ---
