From 555d12ece47f4b1994ed0de681989428f364e649 Mon Sep 17 00:00:00 2001
From: Yaroslav Halchenko <debian@onerussian.com>
Date: Tue, 4 Oct 2005 06:36:09 +0000
Subject: [PATCH] added a notification regarding configuration file

---
 debian/changelog |  7 +++++++
 debian/postinst  | 21 +++++++++++++++++++++
 2 files changed, 28 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index f46efde0..bc28ab42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+fail2ban (0.5.4-5post1) unstable; urgency=low
+
+  * Added a notification regarding the importance of 0.5.4-5 change of
+    failregex in the config file
+
+ -- Yaroslav Halchenko <debian@onerussian.com>  Mon,  3 Oct 2005 22:26:28 -1000
+
 fail2ban (0.5.4-5) unstable; urgency=low
 
   * Made failregex'es more specific to don't allow usernames to be used as a
diff --git a/debian/postinst b/debian/postinst
index 4f748078..ca52285b 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -16,12 +16,33 @@ set -e
 # for details, see http://www.debian.org/doc/debian-policy/ or
 # the debian-policy package
 #
+preversion=$2
 
 case "$1" in
     configure)
        # To fix the bug in generated by previous version files permissions
         LOG=/var/log/fail2ban.log
         [ -f $LOG ] && chmod go-w $LOG
+
+       # Note regarding changed configuration file
+		if [ ! -z $preversion ] \
+			&& dpkg --compare-versions $preversion lt 0.5.4-5;
+			then
+			cat <<EOF 
+WARNING!
+ Configuration file /etc/fail2ban.conf, failregex configuration parameter
+ specificly, were changed in 0.5.4-5 to close reported security breach.
+
+ Unless configuration file (or corresponding failregex'es) gets updated,
+ security breach is not closed and corresponding warning will be reported
+ by the fail2ban (in the log files).
+
+ Please review the configuration file and make appropriate changes. 
+ENJOY!
+
+EOF
+		fi
+
     ;;
 
     abort-upgrade|abort-remove|abort-deconfigure)