Merge pull request #71 from Mikaela/sasl

identifying_to_services: don't assume Atheme
This commit is contained in:
Valentin Lorentz 2015-02-20 16:47:15 +01:00
commit 390d57d265

View File

@ -46,10 +46,12 @@ SASL PLAIN is identifying using username and password, SASL EXTERNAL is identify
using CertFP which is explained later on this document. It doesn't need using CertFP which is explained later on this document. It doesn't need
username or password to be configured. username or password to be configured.
Note that SASL isn't supported on all networks. You can easily test if it's Note that SASL isn't supported on all networks. As the only way to check
supported with ``/msg SaslServ help`` and if you get response, SASL is if SASL is supported is either ``/quote CAP LS`` (which usually gets eaten
probably supported, if you don't get reply or get error about no such nick, by bouncers) or connecting to the network and seeing if it works, we
SASL isn't supported. recommend always configuring SASL and whoising the bot to see if it worked.
If it didn't work, you might want to ask the network operators about their
SASL support and request them to start supporting it.
SASL is widely agreed as the best method to identify to services as it SASL is widely agreed as the best method to identify to services as it
identifies you before anyone (other than IRC operators) can see that you identifies you before anyone (other than IRC operators) can see that you