Your message dated Wed, 08 Nov 2006 19:05:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#366307: fixed in fail2ban 0.7.4-2 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-1 Severity: wishlist It would be great if I could invoke fail2ban to (a) print a list of currently banned IPs with their lifetimes (fail2ban -L) (b) get information on a specific ban (fail2ban -L <ip>) (c) ban a certain IP for a certain amount of time (fail2ban -B <ip> <secs>) (d) unban a certain IP (fail2ban -U <ip>) Note how I am using capital option letters to distinguish these manipulation functions from the start-time options. Cheers, -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages fail2ban depends on: ii iptables 1.3.3-2 Linux kernel 2.4+ iptables adminis ii python 2.3.5-5 An interactive high-level object-o fail2ban recommends no packages. -- no debconf information -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
--- Begin Message ---Source: fail2ban Source-Version: 0.7.4-2 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.4-2.diff.gz to pool/main/f/fail2ban/fail2ban_0.7.4-2.diff.gz fail2ban_0.7.4-2.dsc to pool/main/f/fail2ban/fail2ban_0.7.4-2.dsc fail2ban_0.7.4-2_all.deb to pool/main/f/fail2ban/fail2ban_0.7.4-2_all.deb fail2ban_0.7.4.orig.tar.gz to pool/main/f/fail2ban/fail2ban_0.7.4.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: Mon, 6 Nov 2006 09:18:58 -0500 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.7.4-2 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: 366307 370095 Changes: fail2ban (0.7.4-2) unstable; urgency=low . * Added reload/force-reload actions to init script * Adjusted jail.conf a bit * Warning NEWS entry for 0.7.1 was not shown during installation on test boxes, thus postinst was adjusted accordingly to inform the user about the changes in the configuration files since 0.6. . fail2ban (0.7.4-1) experimental; urgency=low . * New upstream release . fail2ban (0.7.4~pre20061023.2-3) experimental; urgency=low . * Corrected init.d script to properly perform restart due to server delay to react to client command to stop. Handling of status was adjusted as well . fail2ban (0.7.4~pre20061023.2-2) experimental; urgency=low . * Added apache-noscript to jail.conf * Default action does not send emails to be inline with previous (0.6.x) behavior . fail2ban (0.7.4~pre20061023.2-1) experimental; urgency=low . * Fresh upstream: fixed a bug with not handling error producing actioncheck call . fail2ban (0.7.4~pre2006102-1) experimental; urgency=low . * Currrent snapshot of trunk * Removed outdated (applied in 0.7.4 or specific for 0.6.?) patches from debian/patches * Adjusted rule to install man pages -- only .1 files since there are also h2m sources * debian/{rules,control} adjusted to conform all points in recent python policy changes * install under /usr/share instead of /usr/lib . fail2ban (0.7.3-2) experimental; urgency=low . * Added wuftpd section . fail2ban (0.7.3-1) experimental; urgency=low . * New upstream release * Debian shipped jail.conf * Refreshen init.d script . fail2ban (0.7.1-0.2) experimental; urgency=low . * New upstream release (closes: #370095,#366307) Files: a6c8bb4415ae9d7f2b4f06654651d24f 740 net optional fail2ban_0.7.4-2.dsc efabdc7a827d5b7022ea58929b2c38ac 42142 net optional fail2ban_0.7.4.orig.tar.gz 6b719675ee89d158d0c7092f9042f17c 17642 net optional fail2ban_0.7.4-2.diff.gz d1928a0de465520519c856a0d544c7e3 56706 net optional fail2ban_0.7.4-2_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFUmt8Lz4Gnv7CP7IRAg3vAJ9vAmYPR7wcyu5IUkl3bYMUvh+q/QCglfkQ puCtak2xmK0Omj6Bk/I2cXY= =RgSJ -----END PGP SIGNATURE-----
--- End Message ---
