From 28ffef39c86e9d5a2b9164a3e4c7a434632e0d9a Mon Sep 17 00:00:00 2001 From: Peter Powell Date: Mon, 19 Nov 2018 02:25:05 +0000 Subject: Add support for multiple cloak configurations. The first will be used for cloaking and the rest will be used for checking bans. --- docs/conf/modules.conf.example | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'docs/conf/modules.conf.example') diff --git a/docs/conf/modules.conf.example b/docs/conf/modules.conf.example index 4dab9f55b..f2e1d9e89 100644 --- a/docs/conf/modules.conf.example +++ b/docs/conf/modules.conf.example @@ -516,7 +516,8 @@ # # # To use cloaking, you must define a cloak key, and optionally a # # cloak prefix as shown below. The cloak key must be shared across # -# the network for correct cloaking. # +# the network for consistent cloaking and must be at least thirty # +# characters long. # # # # There are two methods of cloaking: # # # @@ -532,12 +533,21 @@ # # # The methods use a single key that can be any length of text. # # An optional prefix may be specified to mark cloaked hosts. # +# # +# IMPORTANT: Changing these details will break all of your existing # +# bans. If you do not want this to happen you can define multiple # +# cloak tags. The first will be used for cloaking and the rest will # +# be used for checking if a user is banned in a channel. # #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-# # # +# +# #-#-#-#-#-#-#-#-#-#-#-#- CLOSE MODULE #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-# # Close module: Allows an oper to close all unregistered connections. -- cgit v1.2.3