From b231cf713d4f8ffc520a29ddf54c8aa0517c784e Mon Sep 17 00:00:00 2001
From: Bram Matthys
Version: 3.2
Current Version: 3.2 Beta15
- Last doc update: 2003-03-01
+ Last doc update: 2003-03-02
Head Coders: Stskeeps / Codemastr / Luke / McSkaf / Syzop
Contributors: Zogg / NiQuiL / assyrian / chasm / DrBin / llthangel / Griever / nighthawk
Documentation: CKnight^ / Syzop
@@ -231,13 +231,24 @@
you probably want to read those after installing :).
SSL stands for Secure Socket Layer, with SSL you can make secure (encrypted) connections. - It can be used to encrypt server2server traffic, but clients can also use it if you want. - If set up right it can useful again sniffing attacks, if you don't know what I'm talking - about then SSL is (not yet) for you ;).
-To setup a secure SSL port you need to add the ssl flag to the listen block. - NOTE: you cannot connect with non-ssl clients to a SSL port, so don't set port 6667 to SSL for example ;).
- +SSL stands for Secure Socket Layer, with SSL you can make secure encrypted connections. + It can be used to encrypt server<->server traffic, but client<->server traffic can also be encrypted. + You usually use SSL to protect against sniffing and for authentication.
+You need to have your IRC server compiled with SSL support. To setup a SSL port you need to set listen::options::ssl.
+You cannot connect normally to a SSL port (so don't make port 6667 ssl!), you need a client or a tunnel + that understands the SSL protocol.
+Clients that support SSL: XChat
+For all other clients which don't support SSL (like mIRC) you can use a tunnel like
+ stunnel, here's a stunnel.conf example (for stunnel 4.x):
+
+ [irc] + accept = 127.0.0.1:6667 + connect = irc.myserv.com:6900 ++ If you then connect to 127.0.0.1 port 6667 your traffic will be encrypted and forwarded to irc.myserv.com + port 6900 (a SSL port). +
If you are really concerned about security/sniffing then you also need to validate certificates on the client end. + That's however way too offtopic to explain here. Learn about SSL, don't ask us, it has nothing to do with UnrealIRCd.
UnrealIRCd supports IPv6, since beta15 it seems to work well altough there might be some bugs in it. You need to compile with IPv6 support (answer yes to the ./Config question), ofcourse your @@ -245,10 +256,10 @@
Altough microsoft has an experimental IPv6 implementation for w2k/XP it is not (yet) supported by UnrealIRCd
-Zip links can be turned on for server2server links, it compresses the data by using zlib. +
Zip links can be turned on for server<->server links, it compresses the data by using zlib. It can save 60-80% bandwidth... So it's quite useful for low-bandwidth links or links with many users, it can help a lot when you are linking since then a lot of data is sent about ever user/channel/etc.
-To compile with zip links support, you need to answer Yes to the zlib question in ./Config
+To compile with zip links support, you need to answer Yes to the zlib question in ./Config and set it in link::options::zip
UnrealIRCd has a lot of features so not everything is covered here... You'll find that out by yourself