new blog: shadowbans

[irc/freenode/web-7.0.git] / content / news / 2016-09-18-resurrecting-tor-2.md

diff --git a/content/news/2016-09-18-resurrecting-tor-2.md b/content/news/2016-09-18-resurrecting-tor-2.md
index 8b0f99bfa43fb7fea942e1410b54398782824ee6..05f3ce472df939dda7e08dc2adfeaabf71316d87 100644 (file)
--- a/content/news/2016-09-18-resurrecting-tor-2.md
+++ b/content/news/2016-09-18-resurrecting-tor-2.md
@@ -5,7 +5,7 @@ Date: 2016-09-18T20:18+01:00
 Slug: tor-online
 ---
 
-Following an embarassingly long period of no Tor support, we [recently
+Following an embarrassingly long period of no Tor support, we [recently
 blogged](news/2016-09-05-tor-sasl) about resurrecting Tor.
 
 As of today, Tor users can once more connect to freenode over Tor; the hidden
@@ -17,7 +17,7 @@ The hidden service requires SASL authentication, as before. In addition, due to
 the abuse that led Tor access to be disabled in the first place, we have
 unfortunately had to add another couple of restrictions:
 
-- You must log in using SASL's `EXTERNAL` or `ECDSA-NIST25P-CHALLENGE` (more
+- You must log in using SASL's `EXTERNAL` or `ECDSA-NIST256P-CHALLENGE` (more
        below)
 - If you log out while connected via Tor, you will not be able to log in without
        reconnecting.
@@ -25,7 +25,7 @@ unfortunately had to add another couple of restrictions:
 If you haven't set up the requisite SASL authentication, we recommend SASL
 EXTERNAL. You'll need to generate a client certificate:
 
-    openssl req -x509 -new -newkey rsa:4096 -nodes -out freenode.pem -keyout freenode.pem
+    openssl req -x509 -sha256 -new -newkey rsa:4096 -days 1000 -nodes -out freenode.pem -keyout freenode.pem
 
 and consult your IRC client's documentation to find out how to use it to
 connect. Connect to freenode over TLS on the plain Internet and `/msg NickServ