]>
Commit | Line | Data |
---|---|---|
de97d234 | 1 | Title: Connecting to freenode |
c7279396 | 2 | Slug: chat |
3 | --- | |
c7279396 | 4 | |
05b3480d EK |
5 | The freenode network can be accessed via the [freenode |
6 | webchat](//webchat.freenode.net) or using an IRC client such as irssi, WeeChat, | |
7 | ERC, HexChat, Smuxi, Quassel or mIRC. | |
8 | ||
9 | You can connect to freenode by pointing your IRC client at `chat.freenode.net` | |
7d5bfc26 DP |
10 | on ports 6665-6667 and 8000-8002 for plain-text connections, or ports 6697, 7000 |
11 | and 7070 for SSL-encrypted connections. | |
a1b22831 CD |
12 | |
13 | ## Accessing freenode Via SSL | |
a1b22831 | 14 | |
05b3480d EK |
15 | freenode provides SSL client access on all servers, on ports 6697, 7000 and |
16 | 7070. Users connecting over SSL will be given user mode +Z, and _is using a | |
17 | secure connection_ will appear in WHOIS (a 671 numeric). Webchat users will not | |
18 | currently appear with +Z or the 671 numeric, even if they connect to webchat | |
19 | via SSL. | |
20 | ||
21 | In order to verify the server certificates on connection, some additional work | |
22 | may be required. First, ensure that your system has an up-to-date set of root | |
23 | CA certificates. On most linux distributions this will be in a package named | |
24 | something like ca-certificates. Many systems install these by default, but some | |
25 | (such as FreeBSD) do not. For FreeBSD, the package is named ca\_root\_nss, | |
26 | which will install the appropriate root certificates in | |
27 | /usr/local/share/certs/ca-root-nss.crt. | |
a1b22831 | 28 | |
05b3480d EK |
29 | Certificate verification will generally only work when connecting to |
30 | **`freenode.net`**. If your client thinks the server's certificate is invalid, | |
31 | make sure you are connecting to `chat.freenode.net` rather than any other name | |
32 | that leads to freenode. | |
debd708e | 33 | |
3f819807 EK |
34 | For most clients this should be sufficient. If not, you can download the root |
35 | certificate from | |
29ce2dd1 | 36 | [LetsEncrypt](https://letsencrypt.org/certificates/). |
a1b22831 | 37 | |
05b3480d EK |
38 | Client SSL certificates are also supported, and may be used for identification |
39 | to services. See [this kb article](kb/using/certfp). If you have connected with | |
40 | a client certificate, _has client certificate fingerprint | |
41 | f1ecf46714198533cda14cccc76e5d7114be4195_ (showing your certificate's SHA1 | |
42 | fingerprint in place of _f1ecf46..._) will appear in WHOIS (a 276 numeric). | |
6da654fb CFL |
43 | |
44 | ## Accessing freenode Via Tor | |
45 | ||
05b3480d EK |
46 | freenode is also reachable via [Tor<i class="fa fa-external-link" |
47 | aria-hidden="true"></i>](https://www.torproject.org/), bound to some | |
3f819807 EK |
48 | restrictions. You can't directly connect to chat.freenode.net via Tor; use |
49 | the following hidden service as the server address instead: | |
6da654fb | 50 | |
c278d82d D |
51 | ajnvpgl6prmkb7yktvue6im5wiedlz2w32uhcwaamdiecdrfpwwgnlqd.onion |
52 | ||
05b3480d EK |
53 | The hidden service requires SASL authentication. In addition, due to the abuse |
54 | that led Tor access to be disabled in the past, we have unfortunately had to | |
55 | add another couple of restrictions: | |
6da654fb | 56 | |
3f819807 | 57 | - You must log in using SASL `EXTERNAL` or `ECDSA-NIST256P-CHALLENGE` (more |
05b3480d EK |
58 | below) |
59 | - If you log out while connected via Tor, you will not be able to log in | |
60 | without reconnecting. | |
6da654fb CFL |
61 | |
62 | If you haven't set up the requisite SASL authentication, we recommend SASL | |
63 | EXTERNAL. You'll need to generate a client certificate and add that to your | |
c3260969 | 64 | NickServ account. This is documented [in our knowledge base](kb/using/certfp). |
05b3480d | 65 | |
3e7dd983 DP |
66 | Connecting using SASL EXTERNAL requires that you connect using SSL encryption. |
67 | ||
6da654fb CFL |
68 | You'll then want to tell your client to try the `EXTERNAL` mechanism. We lack |
69 | comprehensive documentation for this, but it's a feature in most modern | |
70 | clients, so please check their docs for instructions for now. | |
50e402f7 EM |
71 | |
72 | ### Verifying Tor TLS connections | |
73 | ||
c54c1e2e | 74 | 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. |
50e402f7 | 75 | |
c54c1e2e | 76 | 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. |
50e402f7 EM |
77 | |
78 | # torrc snippet: | |
79 | MapAddress zettel.freenode.net ajnvpgl6prmkb7yktvue6im5wiedlz2w32uhcwaamdiecdrfpwwgnlqd.onion | |
80 | ||
81 | Older clients that don't support SOCKS4a or later will need to use `MapAddress` with an IP address, and the certificate will not validate successfully. In this case validation will need to be disabled. | |
82 | ||
83 | Note that the hidden service's certificate changes periodically as it is updated. This means that the *certificate fingerprint* can not be reliably pinned. A few clients support *public key pinning*, however. For these clients the following *public key fingerprint* can be pinned: | |
84 | ||
85 | # sha256 public key fingerprint | |
86 | E0:1B:31:80:56:D9:78:C4:2B:2D:3F:B2:DB:81:AB:03:15:59:BF:04:7E:31:E8:60:5F:98:07:A1:BB:8F:A3:0D |