prehistoric-systems/fail2ban
1
0
Fork 0
mirror of https://github.com/fail2ban/fail2ban.git synced 2026-03-11 08:55:31 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
fail2ban/debian
History
Yaroslav Halchenko ff32f0ec9a * because upstream includes debian-init file I decided to just copy it during installation into debian 
* adjusted Makefile/rules to handle /etc/default/fail2ban correctly
2005-07-23 19:30:44 +00:00
..
changelog * Merged with upstream 2005-07-23 19:15:22 +00:00
compat Load fail2ban-0.4.1 into debs/fail2ban/trunk. 2005-07-06 23:10:26 +00:00
control * tuned description to satisfy lintian 2005-07-13 10:19:20 +00:00
copyright Absorbed LICENSE.log4py inside a copyright file so to make lintian shut up 2005-07-15 22:37:13 +00:00
postinst fixed security hole with world-open umask 2005-07-08 05:05:49 +00:00
README.Debian * Merged with upstream 2005-07-23 19:15:22 +00:00
rules * because upstream includes debian-init file I decided to just copy it during installation into debian 2005-07-23 19:30:44 +00:00
TODO Merged with 0.5.0 upstream release 2005-07-13 10:01:01 +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.

Module log4py installed along into fail2ban directory because there is
no package for not-developed-in-a-long-time fail2ban

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