]>
Commit | Line | Data |
---|---|---|
1 | Title: Connecting with SASL | |
2 | --- | |
3 | SASL is a method that allows identification to services (NickServ) during the connection process, before anything else happens - therefore eliminating the need to | |
4 | /msg nickserv identify. To use SASL, you must [register your nickname](kb/using/registration). | |
5 | ||
6 | SASL Client Configuration | |
7 | ============== | |
8 | ||
9 | 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` | |
10 | ||
11 | * [AdiIRC <i class="fa fa-external-link" aria-hidden="true"></i>](https://dev.adiirc.com/projects/adiirc/wiki/SASL) | |
12 | * [AndChat <i class="fa fa-external-link" aria-hidden="true"></i>](http://www.andchat.net/page/misc_doc) | |
13 | * [AndroIRC <i class="fa fa-external-link" aria-hidden="true"></i>](http://wiki.androirc.com/nickserv_sasl) | |
14 | * [Chatzilla](kb/sasl/chatzilla) | |
15 | * [EPIC5](kb/sasl/epic5) | |
16 | * [glirc <i class="fa fa-external-link" aria-hidden="true"></i>](https://github.com/glguy/irc-core/wiki/Automatically-authenticating-to-NickServ) | |
17 | * [HexChat](kb/sasl/hexchat) | |
18 | * [irssi](kb/sasl/irssi) | |
19 | * [Konversation <i class="fa fa-external-link" aria-hidden="true"></i>](http://userbase.kde.org/Konversation/Configuring_SASL_authentication) | |
20 | * [KVIrc](kb/sasl/kvirc) | |
21 | * [LimeChat](kb/sasl/limechat) | |
22 | * [mIRC](kb/sasl/mirc) | |
23 | * [Quassel](kb/sasl/quassel) | |
24 | * [Revolution](kb/sasl/revolution) | |
25 | * [Textual](kb/sasl/textual) | |
26 | * [WeeChat](kb/sasl/weechat) | |
27 | * [ZNC <i class="fa fa-external-link" aria-hidden="true"></i>](http://wiki.znc.in/Sasl#Example) | |
28 | * [IRCCloud](kb/sasl/irccloud) | |
29 | ||
30 | 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. | |
31 | ||
32 | Documentation on how to create certificates and add their fingerprints to NickServ for SASL EXTERNAL | |
33 | can be found in [the article on NickServ and certificates](kb/using/certfp). | |
34 | ||
35 | SASL access only IP ranges | |
36 | ========================== | |
37 | ||
38 | 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. | |
39 | ||
40 | 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. | |
41 | ||
42 | 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.* |