fail2ban

History

Yaroslav Halchenko e46b5f6665 New upstream release, removed log4py, fresh man file for conf		2005-08-06 19:43:43 +00:00
..
README.Debian	New upstream release, removed log4py, fresh man file for conf	2005-08-06 19:43:43 +00:00
TODO	Merged with 0.5.0 upstream release	2005-07-13 10:01:01 +00:00
changelog	New upstream release, removed log4py, fresh man file for conf	2005-08-06 19:43:43 +00:00
compat	Load fail2ban-0.4.1 into debs/fail2ban/trunk.	2005-07-06 23:10:26 +00:00
control	fixed description as ftpmaster required + fixed dependency on python-dev	2005-07-31 01:25:17 +00:00
copyright	New upstream release, removed log4py, fresh man file for conf	2005-08-06 19:43:43 +00:00
postinst	fixed security hole with world-open umask	2005-07-08 05:05:49 +00:00
rules	New upstream release, removed log4py, fresh man file for conf	2005-08-06 19:43:43 +00:00
watch	* Merged with upstream	2005-07-23 19:15:22 +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.

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

 -- Yaroslav O. Halchenko <debian@onerussian.com>, Sat Jul 23 09:09:51 2005