webchat.freenode.net now connects to the ircd via tls (#457)

[irc/freenode/web-7.0.git] / content / kb / connect / chat.md

diff --git a/content/kb/connect/chat.md b/content/kb/connect/chat.md
index 3fd53e6ef0566723ddb0cf3de88a5e3cdbfed635..c75241fce36e9f5800dc345fa55c792b76707bd8 100644 (file)
--- a/content/kb/connect/chat.md
+++ b/content/kb/connect/chat.md
@@ -14,9 +14,7 @@ and 7070 for SSL-encrypted connections.
 
 freenode provides SSL client access on all servers, on ports 6697, 7000 and
 7070. Users connecting over SSL will be given user mode +Z, and _is using a
-secure connection_ will appear in WHOIS (a 671 numeric). Webchat users will not
-currently appear with +Z or the 671 numeric, even if they connect to webchat
-via SSL.
+secure connection_ will appear in WHOIS (a 671 numeric).
 
 In order to verify the server certificates on connection, some additional work
 may be required. First, ensure that your system has an up-to-date set of root
@@ -50,11 +48,6 @@ the following hidden service as the server address instead:
 
     ajnvpgl6prmkb7yktvue6im5wiedlz2w32uhcwaamdiecdrfpwwgnlqd.onion
 
-If you are using an old version of Tor (before 0.3.5) that does not support
-v3 addresses, you should instead use the following address:
-
-    freenodeok2gncmy.onion
-
 The hidden service requires SASL authentication. In addition, due to the abuse
 that led Tor access to be disabled in the past, we have unfortunately had to
 add another couple of restrictions:
@@ -76,9 +69,9 @@ clients, so please check their docs for instructions for now.
 
 ### Verifying Tor TLS connections
 
-**A Tor hidden service name securely identifies the service you are connecting to. Verifying the TLS server certificate is strickly-speaking unnecessary while using the hidden service.** Nonetheless the following methods can be used to verify the hidden service's TLS server certificate.
+A Tor hidden service name securely identifies the service you are connecting to. Verifying the TLS server certificate is strickly-speaking unnecessary while using the hidden service. Nonetheless the following methods can be used to verify the hidden service's TLS server certificate.
 
-The best way to ensure the TLS server-side certificate successfully validates is to add the following fragment to your `torrc` configuration file and configure your client to connect to `zettel.freenode.net`. The TLS server certificate used by the hidden service will validate using this hostname.
+The best way to ensure the TLS server-side certificate successfully validates is to add the following fragment to your `torrc` configuration file and configure your client to connect to `zettel.freenode.net` via Tor. The TLS server certificate used by the hidden service will validate using this hostname.
 
     # torrc snippet:
     MapAddress zettel.freenode.net ajnvpgl6prmkb7yktvue6im5wiedlz2w32uhcwaamdiecdrfpwwgnlqd.onion