Your message dated Fri, 23 Nov 2007 18:02:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#436053: fixed in fail2ban 0.8.1-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)
--- Begin Message ---
Package: fail2ban
Version: 0.8.0-4
The ssh and ssh-ddos sections in /etc/fail2ban/jail.conf have "port =
ssh,sftp". However, secure ftp runs over port 22 like regular ssh.
(Instead of starting an interactive session after authentication, the
sftp client requests the sftp module.) Port 115 is the Simple File
Transfer Protocol[1], which is marked by the IETF as "historic"[2].
Please consider adjusting the default configuration to only specify
"port = ssh" for these sections.
[1] http://www.ietf.org/rfc/rfc913.txt
[2] ftp://ftp.isi.edu/in-notes/rfc-index.txt
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.8.1-3
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.1-3.diff.gz
to pool/main/f/fail2ban/fail2ban_0.8.1-3.diff.gz
fail2ban_0.8.1-3.dsc
to pool/main/f/fail2ban/fail2ban_0.8.1-3.dsc
fail2ban_0.8.1-3_all.deb
to pool/main/f/fail2ban/fail2ban_0.8.1-3_all.deb
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: Fri, 23 Nov 2007 11:42:24 -0500
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.8.1-3
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: 436053 451093
Changes:
fail2ban (0.8.1-3) unstable; urgency=low
.
* Added Vcs- fields, moved Homepage into source header's field
* Propagated patch from 0.9 upstream branch: "Replaced ssocket.py with
asyncore/asynchat implementation. Correct fix for bug #1769616. That is
supposed to resolve spontaneous 100% CPU utilization by fail2ban-server."
* BF: removed sftp from ssh jails (closes: #436053)
* NF: new filter for 'refused connect' (closes: #451093). Thanks Guido
Bozzetto
* Moved iptables into recommends since fail2ban can work without iptables
using some other action (e.g hosts.deny)
Files:
06f1151c70e8c21742c12af682eadcc3 805 net optional fail2ban_0.8.1-3.dsc
05383ef4e31c63c76e29d23aced94e65 27120 net optional fail2ban_0.8.1-3.diff.gz
e308ba7dac8cd59f5fddb2abeb93cda4 78410 net optional fail2ban_0.8.1-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHRxRjjRFFY3XAJMgRApaOAJsFRAkwg1cxNPtdEL8yKlqwPC5vlwCeIPeO
WbI3iporwENf4ZNlQ4PUssM=
=d18G
-----END PGP SIGNATURE-----
--- End Message ---
