From 3a155ed2e0f2f5aea5ebefc1981843984f9764cd Mon Sep 17 00:00:00 2001 From: yungchin Date: Tue, 1 Apr 2014 16:52:21 +0100 Subject: [PATCH] Update comments in shorewall.conf for new settings --- config/action.d/shorewall.conf | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/config/action.d/shorewall.conf b/config/action.d/shorewall.conf index 81ac0518..f5f2c775 100644 --- a/config/action.d/shorewall.conf +++ b/config/action.d/shorewall.conf @@ -9,7 +9,9 @@ # connections. So if the attempter goes on trying using the same connection # he could even log in. In order to get the same behavior of the iptable # action (so that the ban is immediate) the /etc/shorewall/shorewall.conf -# file should me modified with "BLACKLISTNEWONLY=No". +# file should me modified with "BLACKLISTNEWONLY=No". Note that as of +# Shorewall 4.5.13 BLACKLISTNEWONLY is deprecated; however the equivalent +# of BLACKLISTNEWONLY=No can now be achieved by setting BLACKLIST="ALL". # [Definition]