From 24aa8027de56a4f231d790b781ecb752f8b85aa8 Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Mon, 20 Oct 2014 15:06:53 +0300 Subject: [PATCH] use/identifying_to_services: rewording I don't recommend anything anymore there, network operators do that now (ask at \#freenode and they will suggest SASL as reads at https://freenode.net/faq.shtml#identify ). Also mention that SASL is SASL PLAIN and to use SASL EXTERNAL you simply configure CertFP + explain difference between the two mechanisms. --- use/identifying_to_services.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/use/identifying_to_services.rst b/use/identifying_to_services.rst index 446e97a..a0533eb 100644 --- a/use/identifying_to_services.rst +++ b/use/identifying_to_services.rst @@ -4,14 +4,18 @@ Identifying the bot to services ******************************* -The different methods are listed in order which I (Mikaela) recommend. You -can use all of these methods or only some of them. I (Mikaela) personally -use SASL, CertFP and Server password. +The different methods listed here are in the order how they are usually recommended +by network operators. Please also note that SASL and CertFP are only supported on Limnoria. -SASL ----- +SASL PLAIN +---------- + +*To use SASL EXTERNAL, you must only configure CertFP and it's attempted automatically.* +SASL PLAIN is identifying using username and password, SASL EXTERNAL is identifying by +using CertFP fingerprint which is explained later on this document. It doesn't need +username or password to be configured. Note that SASL isn't supported on all networks. You can easily test if it's supported with ``/msg SaslServ help`` and if you get response, SASL is