Skip to content

Commit a28c16e

Browse files
authored
Clarify webchat sasl use & add workaround advice (#168)
1 parent 7eb24e3 commit a28c16e

File tree

1 file changed

+14
-3
lines changed

1 file changed

+14
-3
lines changed

content/_guides/sasl.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,20 @@ existing NickServ account with a **verified email address**. Connections from
5252
these ranges will be refused with the message `SASL access only`. You can
5353
follow the instructions above to configure many commonly used clients.
5454

55-
Our webchat is **no longer exempt** from the SASL access only restriction.
56-
You will need to find an alternative connection to register your account on
57-
before swapping to using the SASL access only connection.
55+
Our webchat clients use SASL authentication when a password is provided, but
56+
they are **no longer exempt** from the SASL access only restriction. You will
57+
need to find an alternative connection to register your account on before
58+
swapping to using the SASL access only connection.
59+
60+
If your home internet providers are restricted, consider using public access
61+
wifi hotspots such as those provided by most libraries and many school or
62+
work campuses. If you are concerned about access point privacy, you can
63+
[change your password](/guides/sendpass) once you are on a network you trust.
64+
65+
Connecting bots which lack SASL support from SASL access only ranges can be
66+
achieved if you connect the bot via a bouncer that does support SASL
67+
authentication. [ZNC](https://wiki.znc.in) is a popular bouncer that supports
68+
SASL.
5869

5970
SASL access only restrictions are typically applied to address ranges that are
6071
the source of frequent policy violations due to providing easy access to

0 commit comments

Comments
 (0)