Changelog
fail2ban (0.6.1-8) unstable; urgency=low
* Removed bashism (arrays) from init.d script to make it POSIX shell
complient (closes: #368218)
* Added new proftpd section
* Added new saslauthd section. Thanks to martin f krafft
<email address hidden> (closes: #369483)
* Mentioned apache2 log file in Other. comment field for FILE in
apache section. Nothing has to be changed besides the logfile path to
work with apache2 (closes: #342144)
fail2ban (0.6.1-5) unstable; urgency=low
* Further fixed debian packaging: to comply with policy empty target
binary-arch was provided
fail2ban (0.6.1-4) unstable; urgency=low
* Adjusted debian packaging:
- Clean up of debian/rules: removed commented out dh_ scripts which
definetly will never be used
- debhelper and dpatch moved to Build-Depends
- added --no-compile for python setup.py install, and removed explicit
cleaning of .pyc's
- fixed separation binary-indep and binary-arch in debian/rules
- restricted depends on python >= 2.3
fail2ban (0.6.1-3) unstable; urgency=low
* Fixed vsftpd failregexp (closes: #366687)
* Started to use dpatch
fail2ban (0.6.1-2) unstable; urgency=low
* Assigned maxreinits to 1000 to be reasonable since otherwise logfile grows
indefinetly if there is a real problem on the system (closes: #359218)
* Adjusted debian/{copyright,watch}
* New version of init.d script (Thanks to Aaron Isotton) (closes: #364278)
fail2ban (0.6.1-1) unstable; urgency=low
* New upstream release
* In config file added fwchain to ease switching to another input chain
(closes: #357164)
fail2ban (0.6.0-8) unstable; urgency=low
* Minor adjustments to reduce the deviation from the upstream code
fail2ban (0.6.0-7) unstable; urgency=low
* Fixed a typo in failregex for SSH section (closes: #356112)
fail2ban (0.6.0-6) unstable; urgency=low
* Updated README.Debian with information about some cases with
not-as-shipped configurations of sshd on the boxes running older versions
of openssh server
* Included regexps for SSH in case iff authentication as root using keys was
attempted whenever PermitRootLogin is set to something else than "yes" and
key authentication fails
* Included postrm script to remove log files during purge to comply with
policy 10.8 (closes: #355443)
fail2ban (0.6.0-5) unstable; urgency=low
* Fixed Apache section: changed filepath to point at error.log, thus I had
to revert timeregex and timepattern to user RFC 2822 format (closes:
#354346)
fail2ban (0.6.0-4) unstable; urgency=low
* Modifications in README.Debian to reflect a "finding" on
not-AllowedUsers banning which requires default Debian configuration
of "ChallengeResponseAuthentication no" and "PasswordAuthentication
yes"
* Fixed Apache timeregex and timepattern to confirm
the fomat of time stamp used in Debian's acccess.log (error.log uses
RFC 2822 format)
* Added section ApacheAttacks to specify some common patterns of attacks on
a webserver (awstats.pl as a try). This section stays split from Apache
since it is of different nature and might be not appropriate for some
users
* Forced owner/permissions of log file to be root:adm/640 in postinst and
logrotate (closes: #352053)
-- Ubuntu Archive Auto-Sync <email address hidden> Thu, 15 Jun 2006 13:48:45 +0100
