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

adjusted README: removed part about missing chain because the issue is 

resolved by now
Also postinst announces about necessity to upgrade the config file
debian-releases/etch
Yaroslav Halchenko 2005-10-12 17:21:45 +00:00
parent a9efdf16ea
commit 501955f36a
3 changed files with 17 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
debian/README.Debian vendored
View File

@ -32,15 +32,6 @@ just a single group (?P<host>...)
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330827 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330827
Broken chain:
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. Also you can
augment fwban and fwunban rules and include as first lines full
definitions of fwstart. That is nasty solution and probably it will get
resolved in the future.
Mailing: Mailing:
As it was reported (bug #329722) you might need to provide a full As it was reported (bug #329722) you might need to provide a full
@ -52,4 +43,4 @@ work nicely now
See TODO.Debian for more details, as well as the Debian Bug Tracking See TODO.Debian for more details, as well as the Debian Bug Tracking
system. system.
-- Yaroslav O. Halchenko <debian@onerussian.com>, Sat Oct 1 02:47:46 2005 -- Yaroslav O. Halchenko <debian@onerussian.com>, Wed Oct 12 13:14:48 2005

2
debian/changelog vendored
View File

@ -1,4 +1,4 @@
fail2ban (0.5.4-5.8) unstable; urgency=low fail2ban (0.5.4-5.9) unstable; urgency=low
* Added a notification regarding the importance of 0.5.4-5 change of * Added a notification regarding the importance of 0.5.4-5 change of
failregex in the config file. failregex in the config file.

16
debian/postinst vendored
View File

@ -26,17 +26,27 @@ case "$1" in
# Note regarding changed configuration file # Note regarding changed configuration file
if [ ! -z $preversion ] \ if [ ! -z $preversion ] \
&& dpkg --compare-versions $preversion lt 0.5.4-5; && dpkg --compare-versions $preversion lt 0.5.4-6;
then then
cat <<EOF cat <<EOF
WARNING! WARNING!
Configuration file /etc/fail2ban.conf, failregex configuration parameter
specificly, were changed in 0.5.4-5 to close reported security breach.
Configuration file /etc/fail2ban.conf, failregex configuration
parameter specificly, were changed in 0.5.4-5 to close reported
security breach, and in 0.5.4-6 to close few other bugs.
updating from <0.5.4-5
Unless configuration file (or corresponding failregex'es) gets updated, Unless configuration file (or corresponding failregex'es) gets updated,
security breach is not closed and corresponding warning will be reported security breach is not closed and corresponding warning will be reported
by the fail2ban (in the log files). by the fail2ban (in the log files).
updating from <0.5.4-6
Bugs #329163, #331695 dealing with changed iptables rules
outside of fail2ban were fixed in 0.5.4-6, and require upgrade of the
configuration file (fwcheck option was introduced) to take full
advantage of the problem solution (otherwise some problems might
persist)
Please review the configuration file and make appropriate changes. Please review the configuration file and make appropriate changes.
ENJOY! ENJOY!