From 77a2f04c41410a0e9780d048134bc57f66990c9f Mon Sep 17 00:00:00 2001
From: Sadie Powell <sadie@witchery.services>
Date: Fri, 21 Feb 2020 20:26:23 +0000
Subject: Improve the documentation of <sasl:server>.

---
 docs/conf/modules.conf.example | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

(limited to 'docs')

diff --git a/docs/conf/modules.conf.example b/docs/conf/modules.conf.example
index ad2b9ca8a..9f8c46d05 100644
--- a/docs/conf/modules.conf.example
+++ b/docs/conf/modules.conf.example
@@ -1947,11 +1947,10 @@
 # Layer via AUTHENTICATE. Note: You also need to have cap loaded
 # for SASL to work.
 #<module name="sasl">
-# Define the following to your services server name to improve security
-# by ensuring the SASL messages are only sent to the services server
-# and not to all connected servers. This prevents a rogue server from
-# capturing SASL messages and disables the SASL cap when services is
-# down.
+
+# You must define <sasl:target> to the name of your services server so
+# that InspIRCd knows where to send SASL authentication messages and
+# when it should enable the SASL capability.
 #<sasl target="services.mynetwork.com">
 
 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
-- 
cgit v1.2.3