fail2ban

History

Yaroslav Halchenko b25140b40c fixed changelog		2005-09-09 21:16:14 +00:00
..
README.Debian	see changelog	2005-09-09 18:57:53 +00:00
TODO	corrected for proper format of SYSLOG entries	2005-08-19 10:34:03 +00:00
changelog	fixed changelog	2005-09-09 21:16:14 +00:00
compat	Load fail2ban-0.4.1 into debs/fail2ban/trunk.	2005-07-06 23:10:26 +00:00
control	Adjusted description and added logrotate config	2005-08-13 08:31:19 +00:00
copyright	New upstream release, removed log4py, fresh man file for conf	2005-08-06 19:43:43 +00:00
docs	fixed man pages - cross referenced them, placed fail2ban into section 8	2005-08-18 23:40:49 +00:00
logrotate	Adjusted description and added logrotate config	2005-08-13 08:31:19 +00:00
postinst	fixed security hole with world-open umask	2005-07-08 05:05:49 +00:00
rules	minor bug	2005-08-19 08:41:52 +00:00
watch	merged with upstream. Need to propagate 'Debian' patches into upstream as soon as possible because they lead to conflicts on upgrades	2005-09-09 21:15:41 +00:00

README.Debian

fail2ban for Debian
-------------------

This package is nearly 100% identical to the upstream version. It was
merely packaged to be installed on a Debian system and due to tight
collaboration with upstream author most of the Debian modifications
penetrate into the next upstream.

Currently the main difference with upstream: python libraries are
placed under /usr/share/fail2ban insteadh of /usr/lib/fail2ban to
comply with policy regarding architecture independent resources.

Only handling of ssh files is enabled by default. If you want to use
fail2ban with apache, please enable apache section manually in
/etc/fail2ban.conf.

Currently no checks if an iptables queue generated at the beginning
(fail2ban-http and fail2ban-ssh) exists. So if your firewall resets
the iptable rules -- it is your responsibility to restart fail2ban.

See  TODO.Debian for more details, as well as the Debian Bug
Tracking system.

 -- Yaroslav O. Halchenko <debian@onerussian.com>, Fri Sep  9 14:55:29 2005