This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
help:connecting:ssl [2009/09/28 10:49] winsauce |
help:connecting:ssl [2020/04/08 12:40] rubin [Certificate Authority] |
||
---|---|---|---|
Line 2: | Line 2: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | This is a guide to help you configure your IRC client software to connect to AfterNET using SSL encryption. Our primary focus is on [[help: | + | This is a guide to help you configure your IRC client software to connect to AfterNET using SSL encryption. |
==== Why encryption ==== | ==== Why encryption ==== | ||
- | Our SSL encryption support is intended to protect you from those on __your local network__ intercepting passwords or reading your conversations. Essentially we want you to be able to login to your account(s) over wifi and speak poorly of your boss without fear of snooping. It is __NOT__ end-to-end security and you should never use IRC to discuss company secrets or anything truly of value. | + | Our SSL encryption support is intended to protect you from those on __your local network__ intercepting passwords or reading your conversations. Essentially we want you to be able to login to your account(s) over wifi and speak poorly of your boss without fear of snooping. It is __NOT__ end-to-end security and you should never use IRC to discuss company secrets or anything truly of value. |
==== Enabling encryption ==== | ==== Enabling encryption ==== | ||
- | Our servers have SSL enabled on port 9998. So to begin with, you simply configure your IRC client to connect to the server named **ssl.afternet.org** on port **9998** and select the 'use encryption' | + | Our servers have SSL enabled on ports 6697 and 9998. **We support only TLS1.2** which means some older clients will not be able to use SSL if they can only do SSLv3 or TLS1. See our [[:help: |
- | ==== Verifying identity ==== | + | |
- | === Why? === | + | |
- | For technical reasons (see [[Wp> | + | |
- | + | ||
- | In your web browser, there is a list of respectable certificate authorities who verify the ownership of companies and issue certificates to them for a fee. IRC software doesn' | + | |
- | + | ||
- | You can choose to not bother with installing our CA on your system, but then you have to configure your IRC software to accept invalid certificates, | + | |
- | + | ||
- | === Installing The AfterNET CA === | + | |
- | == Windows: == | + | |
- | The [[http:// | + | |
- | + | ||
- | NOTE In silverex xchat 2.6.8-1 the ssl cert directory is " | + | |
- | If you install X chat on another drive besides C, you need to put the certificate | + | Configure your software to connect |
- | If you have some more native windows IRC client that uses the built-in windows CA scheme, you could download [[https:// | + | === hexchat === |
+ | In the " | ||
- | == Linux: | + | === ZNC === |
- | Copy the [[https://www.afternet.org/ | + | In the ZNC bouncer, add a ' |
- | NOTE: you **must** rename | + | === mIRC === |
+ | Make sure you have the latest version. Old versions have insecure ssl libraries which have been blocked. | ||
- | == ChatZilla: == | + | To [[http:// |
- | The following will allow ChatZilla to use a self signed certificate which it will frequently find invalid. | + | |
- | Create an Alias using: | + | ==== Certificate Authority ==== |
- | < | + | Our server certificates are signed by [[letsencrypt.org]] |
- | Then run: | ||
- | < | ||
- | This will open Mozilla' |