projects / irc / freenode / web-7.0.git / blame
| Commit | Line | Data |
|---|---|---|
| 46e25db6 | 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 | ||
| 07b4266f | 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` |
| 46e25db6 | 10 | |
| e712239f | 11 | * [AdiIRC <i class="fa fa-external-link" aria-hidden="true"></i>](https://dev.adiirc.com/projects/adiirc/wiki/SASL) |
| 46e25db6 | 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) | |
| 7f46d3ed | 16 | * [glirc <i class="fa fa-external-link" aria-hidden="true"></i>](https://github.com/glguy/irc-core/wiki/Automatically-authenticating-to-NickServ) |
| 46e25db6 | 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) | |
| 7f46d3ed | 21 | * [LimeChat](kb/sasl/limechat) |
| f22bf3e0 | 22 | * [mIRC](kb/sasl/mirc) |
| cc13900e | 23 | * [Pidgin](kb/sasl/pidgin) |
| 12a6a2b9 | 24 | * [Quassel](kb/sasl/quassel) |
| 19b15d59 | 25 | * [Revolution](kb/sasl/revolution) |
| 46e25db6 | 26 | * [Textual](kb/sasl/textual) |
| dbe63da6 | 27 | * [WeeChat](kb/sasl/weechat) |
| 42b8b264 | 28 | * [ZNC <i class="fa fa-external-link" aria-hidden="true"></i>](http://wiki.znc.in/Sasl#Example) |
| 78d58cb4 | 29 | * [IRCCloud](kb/sasl/irccloud) |
| 46e25db6 | 30 | |
| 31 | 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. | |
| 6da654fb | 32 | |
| 12a6a2b9 | 33 | Documentation on how to create certificates and add their fingerprints to NickServ for SASL EXTERNAL |
| c3260969 | 34 | can be found in [the article on NickServ and certificates](kb/using/certfp). |
| d168ffb4 EM |
35 | |
| 36 | SASL access only IP ranges | |
| 37 | ========================== | |
| 38 | ||
| 39 | 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. | |
| 40 | ||
| 41 | 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. | |
| 42 | ||
| e54e8ef6 | 43 | 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.* |