diff options
author | Sadie Powell <sadie@witchery.services> | 2020-02-21 20:26:23 +0000 |
---|---|---|
committer | Sadie Powell <sadie@witchery.services> | 2020-02-21 20:26:23 +0000 |
commit | 77a2f04c41410a0e9780d048134bc57f66990c9f (patch) | |
tree | f1c7e3951eaf86a1554be6e6ab4d181bac397297 /docs | |
parent | 82c89d40cc6cd0100b4c68e72f869ff007f4ef36 (diff) |
Improve the documentation of <sasl:server>.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/conf/modules.conf.example | 9 |
1 files changed, 4 insertions, 5 deletions
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"> #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-# |