X-Git-Url: https://jfr.im/git/irc/freenode/web-7.0.git/blobdiff_plain/c95cac82f0b84f94a665c555787926c5c3492b75..19b15d59d04fe782a769535e7cfdb1e3a842aa4b:/content/kb/using/sasl.md diff --git a/content/kb/using/sasl.md b/content/kb/using/sasl.md index 302188d88..a13979336 100644 --- a/content/kb/using/sasl.md +++ b/content/kb/using/sasl.md @@ -6,19 +6,37 @@ SASL is a method that allows identification to services (NickServ) during the co SASL Client Configuration ============== -We have instructions on how to configure SASL for some client, below. If asked to choose an authentication mechanism, be aware that freenode does not support `DH-BLOWFISH` +We have instructions on how to configure SASL for some clients, below. If asked to choose an authentication mechanism, be aware that freenode does not support `DH-BLOWFISH` +* [AdiIRC ](https://dev.adiirc.com/projects/adiirc/wiki/SASL) * [AndChat ](http://www.andchat.net/page/misc_doc) * [AndroIRC ](http://wiki.androirc.com/nickserv_sasl) * [Chatzilla](kb/sasl/chatzilla) * [EPIC5](kb/sasl/epic5) +* [glirc ](https://github.com/glguy/irc-core/wiki/Automatically-authenticating-to-NickServ) * [HexChat](kb/sasl/hexchat) * [irssi](kb/sasl/irssi) * [Konversation ](http://userbase.kde.org/Konversation/Configuring_SASL_authentication) * [KVIrc](kb/sasl/kvirc) -* [mirc](kb/sasl/mirc) +* [LimeChat](kb/sasl/limechat) +* [mIRC](kb/sasl/mirc) +* [Quassel](kb/sasl/quassel) +* [Revolution](kb/sasl/revolution) * [Textual](kb/sasl/textual) -* [Weechat ](https://www.weechat.org/files/doc/stable/weechat_user.en.html#irc_sasl_authentication) -* [ZNC ](http://wiki.znc.in/Sasl#example) +* [WeeChat](kb/sasl/weechat) +* [ZNC ](http://wiki.znc.in/Sasl#Example) +* [IRCCloud](kb/sasl/irccloud) If you know of any additions or corrections to the lists above, or would like to contribute a script or (better) documentation, contact us on IRC. + +Documentation on how to create certificates and add their fingerprints to NickServ for SASL EXTERNAL +can be found in [the article on NickServ and certificates](kb/using/certfp). + +SASL access only IP ranges +========================== + +Some IP address ranges are configured to require SASL authentication to an existing NickServ account with a **verified email address**. Connections from these ranges will be refused with the message `SASL access only`. You can follow the instructions above to configure many commonly used clients. + +To [create a NickServ account](https://freenode.net/kb/answer/registration) from a restricted IP address, you can first connect to the [freenode webchat](https://webchat.freenode.net). Webchat is not affected by the SASL restriction. Once your NickServ account's email address has been verified you can use that account to satisfy the SASL requirement. + +SASL access only restrictions are typically applied to address ranges that are the source of frequent policy violations due to providing easy access to dynamic addresses to a wide range of users. These ranges are typically used by VPN, cloud-computing, and mobile network providers. *These restrictions are not targeted at individual users.*