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

* NEWS.Debian confusions - the latest NEWS entry and postinst message 

were rephrased (Closes: #402350)
debian-releases/etch
Yaroslav Halchenko 2006-12-09 23:27:39 +00:00
parent ae58ed091a
commit bbb9e6f094
3 changed files with 38 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
debian/NEWS vendored
View File

@ -1,14 +1,31 @@
fail2ban (0.7.1-1) unstable; urgency=low
0.7.x versions of fail2ban is a complete rewrite of the tool since 0.6, and
is went through restructuring of the configuration files. If you had
adjusted config file /etc/fail2ban.conf or /etc/defaults/fail2ban, you need
to adjust new config files (under /etc/fail2ban/ and /etc/default/fail2ban)
to take advantage of the upgrade. Now fail2ban uses split configs and local
modifications can be introduced in corresponding .local files. Please
remove old configuration file /etc/fail2ban.conf thereafter.
fail2ban 0.7 is a complete rewrite of the 0.6 version, and if you
customized any of provided configuration or startup files
(/etc/default/fail2ban, /etc/fail2ban.conf, /etc/init.d/fail2ban),
please read further. The configuration scheme has changed upstream:
0.7 ignores /etc/fail2ban.conf and instead uses a split configuration
under /etc/fail2ban/. To retain your customizations, for example to
monitor anything other than sshd, you will need to set them under that
new directory; use *.local files for customizations. Please see
/usr/share/doc/fail2ban/README.Debian.gz and
http://fail2ban.sourceforge.net for further description of new
configuration scheme. Detailed documentation is under development (see
#400416). When you are satisfied with the new settings, please delete
/etc/fail2ban.conf to avoid confusion.
-- Yaroslav Halchenko <debian@onerussian.com> Tue, 12 Sep 2006 10:31:15 -0400
Fail2ban 0.7 uses client/server architecture and fail2ban-client is to
substitute fail2ban command to provide an interface between the user and
fail2ban-server. That is why some command line parameters present in
fail2ban 0.6 are invalid in fail2ban-client. Such change affects
/etc/default/fail2ban; you should review that file if you customized it.
Please enable sections as directed in README.Debian.gz mentioned above.
You must use newly shipped init.d/fail2ban, or otherwise fail2ban will
not start.
This note was rewritten in release 0.7.5-2 to clarify its meaning.
-- Yaroslav Halchenko <debian@onerussian.com> Sat, 9 Dec 2006 18:24:36 -0500
fail2ban (0.6.0-4) unstable; urgency=low

7
debian/changelog vendored
View File

@ -1,3 +1,10 @@
fail2ban (0.7.5-2) UNRELEASED; urgency=low
* NEWS.Debian confusions - the latest NEWS entry and postinst message
were rephrased (Closes: #402350)
-- Yaroslav Halchenko <debian@onerussian.com> Sat, 9 Dec 2006 14:12:43 -0500
fail2ban (0.7.5-1) unstable; urgency=low
* New upstream release which fixes next issues

13
debian/postinst vendored
View File

@ -35,16 +35,11 @@ case "$1" in
cat <<EOF
WARNING!
0.7.x versions of fail2ban is a complete rewrite of the tool since 0.6, and
it went through restructuring of the configuration files. If you had
adjusted config file /etc/fail2ban.conf or /etc/defaults/fail2ban, you need
to adjust new config files (under /etc/fail2ban/ and /etc/default/fail2ban)
to take advantage of the upgrade. Now fail2ban uses split configs and local
modifications can be introduced in corresponding .local files. Please
remove old configuration file /etc/fail2ban.conf thereafter.
Fail2ban 0.7 is a complete rewrite of the 0.6 version, and if you
customized any of provided configuration or startup files
(/etc/default/fail2ban, /etc/fail2ban.conf, /etc/init.d/fail2ban), please
read relevant entry in /usr/share/doc/fail2ban/NEWS.Debian.gz.
Please review the configuration file and make appropriate changes.
ENJOY!
EOF
fi
if dpkg --compare-versions $preversion lt 0.5.4-5.14; then