github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

rm options adjusted, README.Debian to fix 373592

debian-releases/etch
Yaroslav Halchenko 2006-06-14 16:22:43 +00:00
parent 7b93d4ded5
commit 4309a11968
3 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
config/debian-initd
View File

@ -61,7 +61,7 @@ do_start()
# we need to remove pid file or fail2ban would refuse to start # we need to remove pid file or fail2ban would refuse to start
# probably check could be ommited but... better be safe # probably check could be ommited but... better be safe
pidofproc $NAME $PIDFILE > /dev/null pidofproc $NAME $PIDFILE > /dev/null
[ $? -eq 2 ] && rm -rf $PIDFILE [ $? -eq 2 ] && rm -f $PIDFILE
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
$DAEMON_ARGS \ $DAEMON_ARGS \
|| return 2 || return 2

13
debian/README.Debian vendored
View File

@ -23,6 +23,8 @@ next release which would handle split configuration files.
Default behavior: Default behavior:
----------------- -----------------
* Enabled Sections:
Only handling of ssh files is enabled by default. If you want to use Only handling of ssh files is enabled by default. If you want to use
fail2ban with apache, please enable apache section manually in fail2ban with apache, please enable apache section manually in
/etc/fail2ban.conf or enable section using command line parameter -e /etc/fail2ban.conf or enable section using command line parameter -e
@ -33,6 +35,17 @@ N.B. '-e' command line parameter is present solely in Debian release
of fail2ban, thus it will not work if you decided to proceed with of fail2ban, thus it will not work if you decided to proceed with
vanilla upstream. vanilla upstream.
* Multiport banning:
Comment for the wishlist #373592.
Default iptables rules for banning use --dport statement which allows to
ban just a single port. For multiport banning you would need to adjust iptables
rules to use multiport module ( -m multiport --dports %(port)s ). If you would
like to ban all ports for that host, just redefine fwban/fwunban commands to
don't have --dport %(port)s statement at all (can be redefined on per-section
basis as well)
Such option is not enabled by default since multiport module might not be
compiled for some hand compiled kernels.
Troubleshooting: Troubleshooting:
--------------- ---------------

9
debian/changelog vendored
View File

@ -1,3 +1,12 @@
fail2ban (0.6.1-9) unstable; urgency=low
* Adjusted rm commands in init script to don't use -r for removal of
the pidfile (thanks Stephen Gran)
* Added clarification about multiport banning to README.Debian
(closes: #373592)
-- Yaroslav Halchenko <debian@onerussian.com> Wed, 14 Jun 2006 12:05:44 -0400
fail2ban (0.6.1-8) unstable; urgency=low fail2ban (0.6.1-8) unstable; urgency=low
* Removed bashism (arrays) from init.d script to make it POSIX shell * Removed bashism (arrays) from init.d script to make it POSIX shell