From 224caf32c740fb30065602e4661a937e3f496289 Mon Sep 17 00:00:00 2001
From: Sadie Powell <sadie@witchery.services>
Date: Mon, 3 Mar 2025 22:02:48 +0000
Subject: Rename sasl to ns_sasl, move to nickserv.example.conf.

---
 data/modules.example.conf  | 10 ----------
 data/nickserv.example.conf | 13 +++++++++++++
 2 files changed, 13 insertions(+), 10 deletions(-)

(limited to 'data')

diff --git a/data/modules.example.conf b/data/modules.example.conf
index 0ae9a9456..e3cd7ad22 100644
--- a/data/modules.example.conf
+++ b/data/modules.example.conf
@@ -558,16 +558,6 @@ module
 	}
 }
 
-/*
- * sasl
- *
- * Some IRCds allow "SASL" authentication to let users identify to services
- * during the IRCd user registration process. If this module is loaded, Anope will allow
- * authenticating users through this mechanism. Supported mechanisms are:
- * PLAIN, EXTERNAL.
- */
-module { name = "sasl" }
-
 /*
  * ssl_gnutls [EXTRA]
  *
diff --git a/data/nickserv.example.conf b/data/nickserv.example.conf
index ad41ba37f..9e08d5e40 100644
--- a/data/nickserv.example.conf
+++ b/data/nickserv.example.conf
@@ -519,6 +519,19 @@ command { service = "NickServ"; name = "RESEND"; command = "nickserv/resend"; }
 module { name = "ns_resetpass" }
 command { service = "NickServ"; name = "RESETPASS"; command = "nickserv/resetpass"; }
 
+/*
+ * ns_sasl
+ *
+ * Provides support for authentication to services via IRCv3 SASL. This is a standardised
+ * alternative to ns_identify that is supported by several IRCds.
+ *
+ * You will need to configure your IRCd to use SASL. See the following links for details:
+ *
+ * InspIRCd: https://docs.inspircd.org/4/modules/sasl/
+ * UnrealIRCd: https://www.unrealircd.org/docs/SASL#Enabling_SASL_on_the_server
+ */
+module { name = "ns_sasl" }
+
 /*
  * ns_set
  *
-- 
cgit