- Undid that. Version is now 3.3-willneverbereleased.

Added comment to changelog:
*****

THIS WAS THE DEVELOPMENT BRANCH FOR UNREAL3.3*. HOWEVER, 3.3* HAS BEEN
DISCONTINUED. FOCUS IS ON 4.* (NEXT-GEN IRCD) AND 3.2* (CURRENT STABLE
IRCD).
FOR 3.2* USE THE BRANCH 'unreal3_2_fixes'
DO NOT USE THIS 3.3* BRANCH FOR ANYTHING OTHER THAN COPYING FEATURES/FIXES
FROM 3.3* TO 3.2* !!

*****

.CHANGES.NEW

@@ -1,6 +1,20 @@
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
-|             UnrealIRCd 3.0                    |
-|               Configuration                   |
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
-| http://unreal.tspre.org                       |
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
+
+ _   _                      _ ___________  _____     _
+| | | |                    | |_   _| ___ \/  __ \   | |
+| | | |_ __  _ __ ___  __ _| | | | | |_/ /| /  \/ __| |
+| | | | '_ \| '__/ _ \/  _ | | | | |    / | |    /  _ |
+| |_| | | | | | |  __/ (_| | |_| |_| |\ \ | \__/\ (_| |
+ \___/|_| |_|_|  \___|\__,_|_|\___/\_| \_| \____/\__,_|
+
+                               Configuration Program
+                                for Unreal3.2.5
+                                    
+This program will help you to compile your IRC server, and ask you
+questions regarding the compile-time settings of it during the process. 
+regarding the setup of it, during the process.
+
+If you have problems regarding the setup & compile, read Unreal.nfo to get
+more information on where to get help. Please, before running this setup,
+read the documentation in the "doc" folder. Docs are also avail online @
+http://www.unrealircd.com/unreal32docs.html
+

.CONFIG.RANT

@@ -0,0 +1,35 @@
+
+Configuration rant, by Stskeeps
+--------------------------------
+
+Right.. so you think you are done now, you can boot your IRCd and be happy,
+and it just works. No, you still got a lot to do. You need to read all of
+the documentation through. Would you even have made it this far without
+makeconf?. 
+
+Well, today, people think they can be 3 months on IRC, and be ready to run
+an IRC daemon. I hate to say this, but I don't think so. 
+
+If you cannot read an IRC help file, or understand what stuff like "desynch",
+"masskill", "k-line", or what "mode # +l 5" means - or you got no experince
+in the UNIX field at all, like, you MUST know how to invoke a editor in a
+shell, or to unzip a file. If you don't know/can do these things, I suggest
+you stop trying to set this up, and go read on some UNIX tutorials, and IRC
+tutorials. It takes a LOT of work to run a IRC server good. 
+
+I mean. I sit on the #unreal-support support channel each day, and I see
+countless questions about stuff that IS IN the documentation. Numerous
+people don't even bother to look at the config files (CONFIG_FILE_STOP
+problem). 
+
+You need to look at the documentation now. You need to see how to "include"
+other configuration files. You need to know how to work out how to use
+doc/example.settings.  I can only tell you, if you ask for support, and it
+is for errors that you could solve by reading the first lines of a document,
+then you'll be firmly ignored. I'm sorry, we cannot help your laziness.
+
+Anyhow, good luck with setting this up. Hope you understand what I am saying
+here. You will learn a lot more reading, than just ignoring what we are
+saying.
+
+--Stskeeps

.NEW_CONFIG

@@ -1,8 +0,0 @@
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
-| UnrealIRCD Custom Create Network Configuration|
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|
-|                                               |
-| This will not be too hard, just follow the    |
-| instructions, and answer the questions...     |
-|                                               |
-|=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=|

.RELEASE.NOTES

@@ -0,0 +1,3 @@
+This is the Unreal3.3* development tree.
+We are currently in pre-alpha stage, which means this code should not be
+used by anyone but the developers or other people liking a broken ircd ;)

.SICI

@@ -0,0 +1,15 @@
+|-------------------------------------------------------------------------|
+| Congratulations on your new SSL self-signed certificate for your IRCd.  |
+| However, wouldn't it be better that you get your certifcate signed by   |
+| some kind of Certification Authority (CA), so your users can check that |
+| they are really connected to the real server, so they feel secure?      |
+|                                                                         |
+| There is an initiative at CACert.org - They offer SSL Certificates      |
+| for use with your IRCd for free, so your users can be sure that they    |
+| can trust you and your server.                                          |
+|                                                                         |
+| To get a free signed certificate please visit http://www.CACert.org     |
+|                                                _________________________|
+| 	                                       	| Press enter to continue |
+---------------------------------------------------------------------------
+

.UPDATE

@@ -0,0 +1,17 @@
+
+ _   _                      _ ___________  _____     _ 
+| | | |                    | |_   _| ___ \/  __ \   | |
+| | | |_ __  _ __ ___  __ _| | | | | |_/ /| /  \/ __| |
+| | | | '_ \| '__/ _ \/ _` | | | | |    / | |    / _` |
+| |_| | | | | | |  __/ (_| | |_| |_| |\ \ | \__/\ (_| |
+ \___/|_| |_|_|  \___|\__,_|_|\___/\_| \_| \____/\__,_|
+
+                             Update Script v2.0 
+
+What download program do you want to use?
+-----------------------------------------
+
+Type "wget" for wget
+Type "lynx" for lynx
+
+> 

.bugreport.gdb

@@ -0,0 +1,77 @@
+#
+# UnrealIRCd Bug Reporting Script
+# Copyright (c) 2001, The UnrealIRCd Team
+# All rights reserved
+#
+#   Redistribution and use in source and binary forms, with or without modification, are permitted
+#   provided that the following conditions are met:
+#   
+#     * Redistributions of source code must retain the above copyright notice, this list of conditions
+#       and the following disclaimer.
+#     * Redistributions in binary form must reproduce the above copyright notice, this list of conditions
+#       and the following disclaimer in the documentation and/or other materials provided with the
+#       distribution.
+#     * Neither the name of the The UnrealIRCd Team nor the names of its contributors may be used
+#       to endorse or promote products derived from this software without specific prior written permission.
+#     * The source code may not be redistributed for a fee or in closed source
+#       programs, without expressed oral consent by the UnrealIRCd Team, however
+#       for operating systems where binary distribution is required, if URL
+#       is passed with the package to get the full source
+#     * No warranty is given unless stated so by the The UnrealIRCd Team
+#
+#   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `AS IS'' AND ANY EXPRESS OR
+#   IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+#   FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE
+#   LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+#   BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR  
+#   BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+#   LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+#   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+# First we define some nice settings and some nice functions
+set print pretty on
+
+# dumplist <linked list> <structure format>
+define dumplist
+echo Dumping linked list $arg0 in format $arg1\n
+set $p = $arg0
+while $p
+	print *($arg1 *) $p
+	set $p = $p->next
+end
+end
+
+# dumparray <name> <size>
+define dumparray
+echo Dumping array $arg0 size $arg1\n
+set $p = 0
+while $p < $arg1
+	if $arg0[$p]
+		print *$arg0[$p]
+	end
+	set $p = $p + 1
+end
+end
+
+echo Full backtrace:\n
+echo ---------------\n
+echo \n
+bt full
+echo \n
+echo Backup parse() buffer:\n
+echo ----------------------\n
+echo \n
+print backupbuf
+echo \n
+echo me output:\n
+echo ----------------------\n
+print me
+echo \n
+echo IRCstats:\n
+echo ----------------------\n
+print IRCstats
+echo \n
+echo Modules:\n
+echo ----------------------\n
+dumparray Modules 50
+quit

.cvsignore

@@ -0,0 +1,6 @@
+ircdcron/ircd.cron
+ircdcron/ircdchk
+src/modules/Makefile
+src/ssl.rnd
+src/win32/devel/StackTrace.lib
+src/win32/gnu_regex.lib

.indent.pro

@@ -0,0 +1,52 @@
+--leave-preprocessor-space
+--dont-break-procedure-type
+--no-space-after-function-call-names
+--brace-indent0
+--indent-level8
+-ip8
+--dont-line-up-parentheses
+--continuation-indentation4
+--case-indentation2
+--no-space-after-casts
+--blank-lines-after-procedures
+--no-blank-lines-after-declarations
+--braces-on-struct-decl-line
+--paren-indentation0
+--case-brace-indentation0
+--line-length110
+--declaration-indentation5
+-T size_t
+-T aClass
+-T TS
+-T aClient
+-T aServer
+-T anUser
+-T aChannel
+-T Mode
+-T aConfItem
+-T aMessage
+-T aMessageTree
+-T aGline
+-T aListingArgs
+-T snomask_t
+-T n_short
+-T n_long
+-T n_time
+-T u_char
+-T u_short
+-T u_long
+-T u_int
+-T dbuf
+-T dbufbuf
+-T aHashEntry
+-T Link
+-T Dlink
+-T VOIDSIG
+-T aHostent
+-T ResRQ
+-T aCache
+-T CacheTable
+-T cainfo
+-T reinfo
+-T RETSIGTYPE
+-T OPT_TYPE

CREDITS.potential

@@ -1,2 +0,0 @@
-List of helpers in the alpha/beta phase:
-* Headbang, Alpha/beta tester

Donation

@@ -1,20 +1,32 @@
-Send donations to:
+UnrealIRCd is a free program, but we do put a lot of time, effort, and money
+into creating and maintaining Unreal. To make it easier for user's to show their
+appreciation, the Unreal team has decided to accept donations through PayPal. If
+you like Unreal, and you'd like to see it continue to exist, please consider making
+a donation. We're not asking for anything huge, whatever you can afford is fine.
+
+PayPal Donation Link:
+<https://www.paypal.com/xclick/business=donation%40unrealircd.org&
+item_name=UnrealIRCd+Donation&no_shipping=1&cn=Comments&tax=0&currency_code=USD>
+
+Or simply send a payment through PayPal to:
+donation@unrealircd.org
+
+If you don't want to use PayPal, or you want to donate something other than money
+(old computer hardware, etc.), contact Stskeeps (stskeeps@unrealircd.com) and send
+your donation to:
 
 UnrealIRCd Project
+C/O Carsten Munk
 P.O.Box 52
 7400 Herning
 Denmark
 
-(if you want to that is.. I mean .. I do my coding for fun.. -
- send a teddybear or something to my nephews or something for 
- my nieces.. so they can keep quiet while I'm trying to do anything)
- 
- Disks, HD's, free internet time or alike are welcome ;p ;)
-
--- Techie (which HAD got 20 MB free HD space out of 400 MB on his own puter)
-	  (just got a 8.4gb and rh6.0 *_*)
-          (and used 200 MB on his shell to code this :>) .. 
-          - oh and btw i'm male:P (*looks at BlueFlame^*)
+All those who donate at least $10 USD will have their name and/or company listed in /credits.
+Additionally, all donators will be listed on the website (regardless of the amount). To make 
+this possible, please include along with your donation the name (or nickname) you want to 
+appear in the list as well as the company name (or IRC server) to list. 
 
+Thank you for your support,
+The UnrealIRCd Team
 
 [ $Id$ ]

INSTALL

@@ -1,153 +0,0 @@
-$Id$
-
-Installation Procedures for the UnrealIRCD:
-=======================================================================
-Created by Stskeeps <stskeeps@tspre.org>
-=======================================================================
-
-This document describes how to install ircd, the unix daemon that acts as 
-an IRC server.
-
-For more information on UnrealIRCD contact us at
- unreal-dev@lists.sourceforge.net
-
-The UnrealIRCD is available from http://unreal.tspre.org
-along with the latest copy of this document.
-
-
-=======================================================================
-This version of the UnrealIRCD is known to compile on the following
-platforms, and with the following compilers.  If you wish to add to this
-list, send the relevant information to us.
-
-OS and Version      Compiler and Version     Comments
-------------------- ------------------------ -------------------------------
-NetBSD 1.2B         gcc 2.7.2
-
-FreeBSD 2.1.0       gcc 2.6.3                Do NOT use crypt at all...
-
-SunOS 4.1.4         gcc 2.7-96q1 (Cygnus)
-
-Solaris 2.4         gcc 2.7-96q1 (Cygnus)    (SunOS 5.4)
-
-Solaris 2.5         SunWorks Pro C           (SunOS 5.5.1)
-                    cc: SC4.0 18 Oct 1995 C 4.0
-
-Digital Unix 3.2    gcc 2.7-96q3 (Cygnus)
-
-Linux 2.0.24        gcc 2.7.2.1
-
-HPUX 9.01           gcc 2.6.3
-
-HPUX 10.01          gcc 2.7-96q3 (Cygnus)
-
-Linux PPC                                    (iMac)
-
-AmigaOS 3.0         GCC egcs-2.91.66         (compile with -D_AMIGA)
-
-Windows NT/95       MSVC++ 4.0	             
-
-Linux Mandrake                                Read FAQ 
-=======================================================================
-Unpacking the Distribution
-
-If you are reading this, you have most likely already done this, but to 
-recap:
-
-The UnrealIRCD server comes tarred and gziped. To uncompress it and expand
-it, use the following commands at the Unix prompt:
-
-gzip -d Unreal3.0.tar.gz
-tar -xvf Unreal3.0.tar
-
-This will create a new directory called Unreal3.0 and unpack the source
-into it.
-
-=======================================================================
-Editing the Configuration Files
-
-In previous versions of the source code many files had to be edited to
-make things right for any given server.
-
-In this version you DO NOT NEED TO EDIT THE Makefile OR ANY FILES
-IN include!  That is, unless you set some strange options.  If you
-find the need to edit include/config.h, for example,
-mail us and tell us why ; Config can be made smarter, and that will make
-it so you won't have to edit anything for the next version.
-
-=======================================================================
-Compiling Your Server
-
-Windows users: You must compile the Config program first. To do this
-run the following command:  $CC src\Config.c
-where $CC is the name of your compiler.  for MSVC users that is 'cl'
-
-To build the server, simply run
-	% ./Config
-to start the configuraton program.  This program looks at your system
-and generate the include/setup.h, include/settings.h, and Options files.
-You will be asked some questions.  Usually the default answers are the best
-ones and most correct.  To accept the default, just hit RETURN.
-
-Next, type 'make'. This will compile your server. Depending on your system,
-this may be a good time for a caffeine break. (MSVC users run 'nmake')
-
-Hopefully, the server will compile without incident. If it does not, and 
-you are not able to determine the error, please email
-unreal-dev@lists.sourceforge.net and hopefully someone will be able to help you with the problem.  If you
-do need to fix something, mail there with a patch.
-
-BE CERTAIN TO INCLUDE OPERATING SYSTEM INFORMATION (uname -a) AND COMPILER
-VERSION (gcc -v, for instance) IN ALL BUG REPORTS.
-
-
-=======================================================================
-Installing the Files
-
-'make install' does not work in this release -- it doesn't do anything
-except a compile if that is needed.
-
-The only files you need are the binary from src/ircd and and an ircd.conf
-(see below for copying doc/example.conf as your initial ircd.conf). You
-probably will want to create a MOTD file too, as well as place the man
-pages from the doc directory to appropriate place in your system.
-
-
-=======================================================================
-Configuring Your Server
-
-The previous step places a file named 'example.conf' into your irc 
-directory you specified to Config.
-
-To create an IRC configuration file, edit: ircd.conf
-
-Now edit this file to reflect your server. The file is mainly 
-self-explanatory. Note that if you plan to use your server on ROXnet,
-make sure that you have the following line:
-
-U:services.roxnet.org:*:*
-
-If you need help configuring your file, please connect to ROXnet,
-(irc.flirt.org or irc.roxnet.org) - go to channel #UnrealIRCd, and ask.
-
-
-=======================================================================
-Starting Your Server
-
-Simply enter the complete path to the executable into the Unix command 
-line, then hit return. Your server is now operational, assuming that you 
-have completed all the steps described above.
-
-NOTE: If you get something like the following when running ircd:
-
-ircd fd table too big
-Hard Limit: 256 IRC max: 1024
-Fix MAXCONNECTIONS
-
-You need to change config.h and recompile. Find the line that says 
-"#define MAXCONNECTIONS 1024", and change it to the number given after 
-"Hard Limit" (most likely 256), then make the server again, following the 
-above instructions.
-
-Enjoy!
-- The UnrealIRCd Team - unreal-dev@lists.sourceforge.net

INSTALL.REMOTEINC

@@ -0,0 +1,23 @@
+**** Remote Includes ****
+
+Setting up UnrealIRCd to work with remote includes is not very difficult. The first step is to
+download c-ares. C-ares can be downloaded from <http://daniel.haxx.se/projects/c-ares/>
+download the latest version of c-ares and extract the .tar.gz somewhere.
+
+Now, download the latest version of curl, available at <http://curl.haxx.se/download.html>
+again, extract the tar.gz somewhere. 
+
+Next, go to the Unreal3.2 directory and run the curlinstall script. You run the script
+as follows:
+
+./curlinstall ares_path curl_path
+
+Paths should be complete pathnames. If you extracted c-ares to /home/username/c-ares-1.0.0
+and curl to /home/username/curl-7.11.0 then you would run:
+
+./curlinstall /home/username/c-ares-1.0.0 /home/username/curl-7.11.0
+
+Lastly, run ./Config. When asked whether to enable remote includes say "yes" and when asked
+for the path curl was installed to include the path that is printed out after ./curlinstall
+completes. Then simply run make to compile Unreal as usual and remote includes should work
+fine.

Makefile.in

@@ -19,10 +19,12 @@
 #*   $Id$
 #*/
 
-CC=gcc
+CC=@CC@
+CXX=@CXX@
 INCLUDEDIR=../include
 NETWORKSDIR=
 FROMDOS=/home/cmunk/bin/4dos
+
 # [CHANGEME]
 # Default flags:
 # Change XCFLAGS if you don't like what Config puts there.  Same with
@@ -31,9 +33,13 @@ FROMDOS=/home/cmunk/bin/4dos
 # If you are configuring by hand, try "-O -g" for XCFLAGS, and leave
 # IRCDLIBS blank.  If that fails, try recomendations below.
 #
-XCFLAGS=
-IRCDLIBS=
 
+#XCFLAGS=-O -g -export-dynamic
+IRCDLIBS=@IRCDLIBS@ @TRELIBS@ @CARESLIBS@
+CRYPTOLIB=@CRYPTOLIB@
+OPENSSLINCLUDES=
+
+XCFLAGS=-I@TREINCDIR@ -I@CARESINCDIR@ @CARESLIBDIR@ @CFLAGS@
 #
 # use the following on MIPS:
 #CFLAGS= -systype bsd43 -DSYSTYPE_BSD43 -I$(INCLUDEDIR)
@@ -87,53 +93,60 @@ IRCDMODE = 711
 # [CHANGEME]
 # IRCDDIR must be the same as DPATH in include/config.h
 #
-IRCDDIR=/usr/local/lib/ircd
+IRCDDIR=@IRCDDIR@
 
-# [CHANGEME]
-# Some SunOS versions want this.  Try it without first.
-#RES=res_init.o res_comp.o res_mkquery.o
-# BSDI systems want this.
-#RES=res_skipname.o
-# The rest are perfectly content with this.
-RES=
 
-# [CHANGEME]
-# If you get a compile-time error dealing with u_int32_t, comment out
-# this line.
-# NEED_U_INT32_T=	-DNEED_U_INT32_T
-NEED_U_INT32_T=
+URL=@URL@
 
 # [CHANGEME]
 # If you get a link-time error dealing with strtoul, comment out
 # this line.
 # STRTOUL=	strtoul.o
-STRTOUL=
+STRTOUL=@STRTOUL@
 
 # [CHANGEME]
 # If you get crashes around a specific number of clients, and that client
 # load comes close or a little over the system-defined value of FD_SETSIZE,
 # override it here and see what happens.
-FD_SETSIZE=
+FD_SETSIZE=@FD_SETSIZE@
 
-CFLAGS=-I$(INCLUDEDIR) $(XCFLAGS) $(NEED_U_INT32_T) $(FD_SETSIZE)
+# Where is your openssl binary
+OPENSSLPATH=@OPENSSLPATH@
+
+CFLAGS=-I$(INCLUDEDIR) $(XCFLAGS) @LDFLAGS@ $(FD_SETSIZE)
 
 SHELL=/bin/sh
 SUBDIRS=src
-BINDIR=$(IRCDDIR)
-MANDIR=/usr/local/man
-INSTALL=/usr/bin/install
-RM=rm
-CP=cp
-TOUCH=touch
-
+BINDIR=@BINDIR@
+INSTALL=@INSTALL@
+RM=@RM@
+CP=@CP@
+TOUCH=@TOUCH@
+RES=
 all:	build
 
 MAKEARGS =	'CFLAGS=${CFLAGS}' 'CC=${CC}' 'IRCDLIBS=${IRCDLIBS}' \
 		'LDFLAGS=${LDFLAGS}' 'IRCDMODE=${IRCDMODE}' \
-		'BINDIR=${BINDIR}' 'INSTALL=${INSTALL}' \
+		'RES=${RES}' 'BINDIR=${BINDIR}' 'INSTALL=${INSTALL}' \
 		'INCLUDEDIR=${INCLUDEDIR}' 'IRCDDIR=${IRCDDIR}' \
-		'MANDIR=${MANDIR}' 'RM=${RM}' 'CP=${CP}' 'TOUCH=${TOUCH}' \
-		'RES=${RES}' 'SHELL=${SHELL}' 'STRTOUL=${STRTOUL}'
+		'RM=${RM}' 'CP=${CP}' 'TOUCH=${TOUCH}' \
+		'SHELL=${SHELL}' 'STRTOUL=${STRTOUL}' \
+		'CRYPTOLIB=${CRYPTOLIB}' \
+		'CRYPTOINCLUDES=${CRYPTOINCLUDES}' \
+		'URL=${URL}' 'CXX=${CXX}'
+
+INSTALL_CONFS = badwords.channel.conf badwords.message.conf \
+		badwords.quit.conf dccallow.conf help.conf \
+		spamfilters.conf.sample LICENSE Donation
+
+INSTALL_DOCS  = doc/Authors doc/example.conf doc/coding-guidelines \
+		doc/tao.of.irc doc/unreal32docs.html
+
+custommodule:
+	cd src; ${MAKE} ${MAKEARGS} MODULEFILE=${MODULEFILE} 'EXLIBS=${EXLIBS}' custommodule
+
+custommodulecpp:
+	cd src; ${MAKE} ${MAKEARGS} MODULEFILE=${MODULEFILE} 'EXLIBS=${EXLIBS}' custommodulecpp
 
 server:
 build:
@@ -147,15 +160,17 @@ build:
 		( cd $$i; ${MAKE} ${MAKEARGS} build; ) \
 	done
 	@echo ' __________________________________________________ '
-	@echo '| Compile is now complete. Now you have to go do   |'
-	@echo '| The load-time configuration - try go read the    |'
-	@echo '| file "dynconf" using your favourite viewer or    |'
-	@echo '| editor. The file will contain instructions on how|'
-	@echo '| to do the dynamic configuration :)               |'
+	@echo '| Compile is now complete.                         |'
+	@echo '| You should now read the documentation and learn  |'
+	@echo '| how to configure your IRCd.                      |'
+	@echo '|                                                  |'
+	@echo '| If you really like UnrealIRCd, and would like to |'
+	@echo '| make a donation, please read the Donation file in|'
+	@echo '| this archive. :)                                 |'
 	@echo '|                                                  |'
 	@echo '| Thanks for using Unreal IRCd! If you are in need |' 
-	@echo '| for any kind of help regarding the IRCd email us |'
-	@echo '| at unreal-dev@lists.sourceforge.net              |' 
+	@echo '| for any kind of help regarding the IRCd please   |'
+	@echo '| read the Unreal.nfo file.                        |' 
 	@echo '|__________________________________________________|'
 
 clean:
@@ -167,16 +182,13 @@ clean:
 	-@if [ -f include/setup.h ] ; then \
 	  echo "To really restart installation, remove include/setup.h" ; \
 	fi
-	-@if [ -f include/settings.h ] ; then \
-	  echo "and include/settings.h" ; \
-	fi
 
 cleandir: clean
-	rm -rf include/networks.h include/setup.h include/settings.h Makefile Settings
+	rm -rf include/networks.h include/setup.h Makefile Settings
 
-makex: fromdos
-	chmod +x Config newnet bsdinstall ircd ircdcron/ircdchk killircd
-	chmod +x makeconf rehash ircdreg
+makex:
+	chmod +x Config newnet ircd ircdcron/ircdchk killircd
+	chmod +x rehash ircdreg
 
 fromdos: cleandir
 	$(FROMDOS) -dv *
@@ -186,7 +198,7 @@ fromdos: cleandir
 	$(FROMDOS) -dv crypt/*
 	$(FROMDOS) -dv ircdcron/*
 makedist: makex
-	echo "Making UnrealIRCd compatible IRCd Dist."
+	echo "Stamping.."
 
 stamp: makedist
 	echo "/* Auto created release stamping */" > include/stamp.h
@@ -201,5 +213,51 @@ depend:
 	done
 
 install: all
-	@echo "Now install by hand; make install is broken."
+	$(INSTALL) -m 0700 -d $(IRCDDIR)
+	$(INSTALL) -m 0700 -d $(BINDIR)
+	$(INSTALL) -b -m 0700 src/ircd $(BINDIR)
+	$(INSTALL) -m 0700 -d $(IRCDDIR)/doc
+	$(INSTALL) -m 0600 $(INSTALL_DOCS) $(IRCDDIR)/doc
+	$(INSTALL) -m 0700 -d $(IRCDDIR)/aliases
+	$(INSTALL) -m 0600 aliases/*.conf $(IRCDDIR)/aliases
+	$(TOUCH) $(IRCDDIR)/unrealircd.conf
+	chmod 0600 $(IRCDDIR)/unrealircd.conf
+	$(INSTALL) -b -m 0600 $(INSTALL_CONFS) $(IRCDDIR)
+	$(INSTALL) -b -m 0700 unreal $(IRCDDIR)
+	$(INSTALL) -m 0700 -d $(IRCDDIR)/modules
+	$(INSTALL) -b -m 0700 src/modules/*.so $(IRCDDIR)/modules
+	-@if [ ! -f "$(IRCDDIR)/curl-ca-bundle.crt" ] ; then \
+		$(INSTALL) -b -m 0700 curl-ca-bundle.crt $(IRCDDIR) ; \
+	fi
+	-@if [ -f server.key.pem ] ; then \
+		if [ ! -f "$(IRCDDIR)/server.key.pem" ] ; then \
+		$(INSTALL) -b -m 0600 server.*.pem $(IRCDDIR) ; \
+		fi ; \
+	fi
+
+pem:	src/ssl.cnf
+	@echo "Generating certificate request .. "
+	$(OPENSSLPATH) req -new \
+              -config src/ssl.cnf -out server.req.pem \
+              -keyout server.key.pem -nodes
+	@echo "Generating self-signed certificate .. "
+	$(OPENSSLPATH) req -x509 -days 365 -in server.req.pem \
+               -key server.key.pem -out server.cert.pem
+	@echo "Generating fingerprint .."
+	$(OPENSSLPATH) x509 -subject -dates -fingerprint -noout \
+		-in server.cert.pem
+	@echo "Setting o-rwx & g-rwx for files... "
+	chmod o-rwx server.req.pem server.key.pem server.cert.pem
+	chmod g-rwx server.req.pem server.key.pem server.cert.pem
+	@echo "Done!. If you want to encrypt the private key, run"
+	@echo "make encpem"
+
+encpem: server.key.pem
+	@echo "Encrypting server key .."
+	$(OPENSSLPATH) rsa -in server.key.pem -out server.key.c.pem -des3
+	-@if [ -f server.key.c.pem ] ; then \
+		echo "Replacing unencrypted with encrypted .." ; \
+		cp server.key.c.pem server.key.pem ; \
+		rm -f server.key.c.pem ; \
+	fi
 

README

@@ -0,0 +1,24 @@
+==[ COMPILING ]==
+To build the ircd, run:
+./Config
+make
+
+If you specified an alternative location during ./Config you also need
+to run "make install".
+
+==[ MAKING A CONFIG FILE ]==
+If you are new, then you need to create your own configfile:
+
+copy doc/example.conf to your main UnrealIRCd directory and call
+it unrealircd.conf .
+Then open it in an editor and carefully modify it, consult the docs
+(doc/unreal32docs.html, or online: www.unrealircd.com/unreal32docs.html)
+for more information about every block/setting.
+Common problems are explained in the FAQ, which is located at:
+http://www.vulnscan.org/UnrealIrcd/faq/ .
+
+==[ BOOTING YOUR IRCD ]==
+Just type: ./unreal start
+Note that after booting the errors are usually logged to ircd.log,
+so check that file if you have any problems.
+Again, check the FAQ (and docs) if you have any boot problems.

READTHIS.NOW

@@ -1,15 +0,0 @@
-Some notes to remember:
------------------------
-* Don't EVER try to link it to incompatible IRCds (this does not
-  include services). It is *INCOMPATIBLE*. Please HEED this warning!!!
-
-* If you need any help you can email me at stskeeps@tspre.org
-
-* Please read the Changes file about release notes
-
-* Bugs? Read Unreal.nfo
-
-* Unreal IRCd is not meant to be a simple IRCd, rather an advanced
-  IRCd, please read the documentation before asking questions
-  
-[ $Id$ ]

TODO

@@ -1,21 +0,0 @@
-TODO: (Possible 3.1)
-* Limit calls to these functions using parse()
-   0.00      3.91     0.00     6475     0.00     0.00  check_registered
-   0.00      3.91     0.00     6827     0.00     0.00 check_registered_user
-* Optimize:
-   0.00      3.91     0.00     1292     0.00     0.01  is_banned    
-  12.55      9.61     2.57    41320     0.06     0.10  check_lusers
-   4.64     11.54     0.95    41566     0.02     0.02  count_channels
-   3.08     13.96     0.63   850968     0.00     0.00  flush_connections
-    (fdlists?)
-   0.15     19.62     0.03       29     1.03     1.80  send_list
-* Add svsvline for global vlines
-* New /whowas system /who as well
-* Short MOTDs
-* B:Lines
-* Channel mode +d
-* Raising PING bug
-* Make alternative I/O engine using poll()
-* Remove some of the _little_ config.h defines and replace with
-  unrealircd.conf lines, ex ADMINCHAT, REMOTE_REHASH
-* X-Windows GUI (how bad it can be but hey! :P)

TSpre.doc

@@ -1,28 +0,0 @@
-
-       TSpre.org
-
-Many here maybe not heard of the Story
-how IRC started (and how EFnet started)
-EFnet's name means "Eris-Free Network". 
-Eris was a central hub at the fomer world-
-wide IRC network, that anyone could just add
-C:N pairs for and connect to.
-
-I was inspired of the tought of a network
-where anyone could link without application and all
-that shit..
-
-Combined with the IRCd i made (Unreal) and the tspre.org
-domain i got donated by Nutcais (my IRC bro). Ive decided to 
-start the TSpre IRC network, where anyone with TSpre servers
-(dreamforge, IRCu p9, and their alike)
-
-(mostly preffered is Unreal thou).. Its an experimental 
-network where people can test out thier IRCds and
-wIRds without having to fill out apps and so on.
-
-There are no real rules. So just have fun :)
-
-See http://www.tspre.org for more info on this=)
-
---Stskeeps (stskeeps@tspre.org)

Unreal.nfo

@@ -1,49 +1,66 @@
 ===============================================
-=            UnrealIRCd v3.0                  =
+=            UnrealIRCd v3.3*                 =
 ===============================================
+
  Was brought to you by:
-  * Stskeeps  <stskeeps@tspre.org>
-  * codemastr <codemastr@tspre.org>
-  
- Precenses on the Internet:
-  * http://unreal.tspre.org or http://unreal.sourceforge.net
-  * ftp://unreal.sourceforge.net/pub/unreal
-  * ftp://ftp.shadow-realm.org/pub/ircd/UnrealIRCd
- 
- CVS Repository:
-  * Alpha versions (or beta)
-  ==========================  
-cvs -z9 -d :pserver:anonymous@cvs.unreal.sourceforge.net:/cvsroot/unreal login
-    (just press enter when it asks for password)
-cvs -z9 -d :pserver:anonymous@cvs.unreal.sourgeforge.net:/cvsroot/unreal co alpha
 
-  * To get support
+  The head coders
   ================
-    * IRC: /server irc.flirt.org 6667 - /join #unrealircd
-    * Mailing list: unreal-support@lists.sourceforge.net (for support)
-  
-  * Got a bug to report? 
-  ====================== 
-    * If the server crashes and dumps core do this:
-       * Go into the Unreal directory and type this:
-           gdb src/ircd core.filename
-         where core.filename is the filename in the dumping core message
-         if it loads gdb, (not saying "command not found" etc), type "bt" in
-         the program (type "quit" to get out again)
-        
-         The output coming out there please mail it to 
-         unreal-dev@lists.sourceforge.net, along with OS type,
-         what "uname -a" says, any clues what it is, if you did anything etc
-         etc. Please keep the core dump files if we ask you to mail us them 
-         if needed
+  * Stskeeps    <stskeeps@tspre.org>
+  * Syzop       <syzop@unrealircd.com>
+  * codemastr   <codemastr@unrealircd.com>
 
-    * If you experince any wierdnesses (that doesnt crash the server)
-      please mail unreal-dev@lists.sourceforge.net with any clues on what
-      you did, what you experinced etc.
+  The coders
+  ===========
+  * DarkElf     <darkelf@unrealircd.com>
+  * Trocotronic <trocotronic@unrealircd.com>
+  * aquanight   <aquanight@unrealircd.com>
 
-  * Got a suggestion?
+  Additional credits
   ===================
-    * Mail it to unreal-dev@lists.sourceforge.net :) or catch one from
-      the Unreal team online on IRC:)
+  Credit also goes to past UnrealIRCd coders, including: McSkaf, Zogg,
+  NiQuiL, assyrian, nighthawk, DrBin, llthangel and Griever.
+  Credit also goes to everyone else who contributed, and those who coded
+  or contributed to UnrealIRCd's ancestors.
 
- 
+ WEBSITE
+ ========
+ http://www.unrealircd.com/
+
+ CVS
+ ====
+ To get anonymous access: (read only)
+ "cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot login"
+
+ press enter when asked for password
+ Then, choose the appropiate branch you want:
+
+ latest 3.3 release (unstable/development):
+ "cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r devel -d Unreal-stable unreal"
+
+ To get support
+ ================
+ Before asking others for help you MUST:
+ * read the docs (doc/unreal32docs.html or online: www.unrealircd.com/unreal32docs.html)
+ * check the FAQ (www.vulnscan.org/UnrealIRCd/faq/)
+
+ Means of support:
+ * Forum: http://forums.unrealircd.com/
+ * IRC: /server irc.ircsystems.net 6667 - /join #unreal-support
+   [Note: Follow the bots instructions in order to get voice.
+          Please be patient after asking questions, we may do other stuff
+          or we're away. Don't repeat questions, we heard you first time,
+          READ THE TOPIC before you ask anything. We do this on a free
+          base so we are volunteeringly helping you, but we are humans
+          like you, and we got to have peace at times as well.]
+ * Mailing list: unreal-users@lists.sourceforge.net
+   (http://lists.sourceforge.net/lists/listinfo/unreal-users also
+    has links to the archive).
+
+ UnrealIRCd Bugtracker (Where to report bugs or make suggestions)
+ =================================================================
+ http://bugs.unrealircd.org
+
+ Want to discuss, chat, etc?
+ =============================
+ * IRC: /server irc.unrealircd.org 6667 - /join #UnrealIRCd

aliases/aliases.conf

@@ -0,0 +1,43 @@
+/* Standard Aliases */
+
+alias identify {
+	format "^#" {
+		target chanserv;
+		type services;
+		parameters "IDENTIFY %1-";
+	};
+	format "^[^#]" {
+		target nickserv;
+		type services;
+		parameters "IDENTIFY %1-";
+	};
+	type command;
+};
+
+alias services {
+	format "^#" {
+		target chanserv;
+		type services;
+		parameters "%1-";
+	};
+	format "^[^#]" {
+		target nickserv;
+		type services;
+		parameters "%1-";
+	};
+	type command;
+};
+
+alias register {
+	format "^#" {
+		target chanserv;
+		type services;
+		parameters "REGISTER %1-";
+	};
+	format "^[^#]" {
+		target nickserv;
+		type services;
+		parameters "REGISTER %1-";
+	};
+	type command;
+};

aliases/anope.conf

@@ -0,0 +1,18 @@
+/* Anope Aliases */
+
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias operserv { type services; };
+alias os { target operserv; type services; };
+alias helpserv { type services; };
+alias botserv { type services; };
+alias bs { target botserv; type services; };
+alias hostserv { type services; };
+alias hs { target hostserv; type services; };
+
+include "aliases/aliases.conf";
+

aliases/auspice.conf

@@ -0,0 +1,33 @@
+/* Auspice Aliases */
+
+/* Uncomment this, if you have enabled "MassServ, W and X" in auspice */
+# alias massserv { type services; };
+# alias ma { target massserv; type services; };
+# alias W { type services; };
+# alias X { type services; };
+
+/* Uncomment this, if you have enabled "WebServ" in auspice */
+# alias webserv { type services; };
+# alias ws { target webserv; type services; };
+
+alias agent { type services; };
+alias adminserv { type services; };
+alias as { target adminserv; type services; };
+alias botserv { type services; };
+alias bs { target botserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias helpserv { type services; };
+alias hs { target helpserv; type services; };
+alias hostserv { type services; };
+alias ho { target hostserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias operserv { type services; };
+alias os { target operserv; type services; };
+alias rootserv { type services; };
+alias rs { target rootserv; type services; };
+
+include "aliases/aliases.conf";

aliases/cygnus.conf

@@ -0,0 +1,12 @@
+/* Cygnus Aliases */
+
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias rootserv { type services; };
+alias rs { target rootserv; type services; };
+
+include "aliases/aliases.conf";

aliases/epona.conf

@@ -0,0 +1,16 @@
+/* Epona Aliases */
+
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias operserv { type services; };
+alias os { target operserv; type services; };
+alias helpserv { type services; };
+alias hs { target helpserv; type services; };
+alias botserv { type services; };
+alias bs { target botserv; type services; };
+
+include "aliases/aliases.conf";

aliases/generic.conf

@@ -0,0 +1,14 @@
+/* Generic Aliases */
+
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias operserv { type services; };
+alias os { target operserv; type services; };
+alias helpserv { type services; };
+alias hs { target helpserv; type services; };
+
+include "aliases/aliases.conf";

aliases/genericstats.conf

@@ -0,0 +1,4 @@
+/* Generic StatServ Aliases */
+
+alias statserv { type stats; };
+alias ss { target statserv; type stats; };

aliases/ircservices.conf

@@ -0,0 +1,17 @@
+/* IRCServices Aliases */
+
+alias nickserv { type services; };
+alias ns { target nickserv; type services; };
+alias chanserv { type services; };
+alias cs { target chanserv; type services; };
+alias memoserv { type services; spamfilter yes; };
+alias ms { target memoserv; type services; spamfilter yes; };
+alias operserv { type services; };
+alias os { target operserv; type services; };
+alias helpserv { type services; };
+alias hs { target helpserv; type services; };
+alias irciihelp { type services; };
+alias statserv { type services; };
+alias ss { target statserv; type services; };
+
+include "aliases/aliases.conf";

aliases/operstats.conf

@@ -0,0 +1,6 @@
+/* OperStats Aliases */
+
+alias operserv { type stats; };
+alias os { target operserv; type stats; };
+alias statserv { type stats; };
+alias ss { target statserv; type stats; };

autoconf/Makefile

@@ -0,0 +1,3 @@
+all:
+	@autoconf
+	cp configure ..

autoconf/aclocal.m4

@@ -0,0 +1,174 @@
+dnl aclocal.m4 generated automatically by aclocal 1.4-p4
+
+dnl Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
+dnl This file is free software; the Free Software Foundation
+dnl gives unlimited permission to copy and/or distribute it,
+dnl with or without modifications, as long as this notice is preserved.
+
+dnl This program is distributed in the hope that it will be useful,
+dnl but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+dnl even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+dnl PARTICULAR PURPOSE.
+
+dnl Macro: unet_CHECK_TYPE_SIZES
+dnl
+dnl Check the size of several types and define a valid int16_t and int32_t.
+dnl
+AC_DEFUN(unreal_CHECK_TYPE_SIZES,
+[dnl Check type sizes
+AC_CHECK_SIZEOF(short)
+AC_CHECK_SIZEOF(int)
+AC_CHECK_SIZEOF(long)
+if test "$ac_cv_sizeof_int" = 2 ; then
+  AC_CHECK_TYPE(int16_t, int)
+  AC_CHECK_TYPE(u_int16_t, unsigned int)
+elif test "$ac_cv_sizeof_short" = 2 ; then
+  AC_CHECK_TYPE(int16_t, short)
+  AC_CHECK_TYPE(u_int16_t, unsigned short)
+else
+  AC_MSG_ERROR([Cannot find a type with size of 16 bits])
+fi
+if test "$ac_cv_sizeof_int" = 4 ; then
+  AC_CHECK_TYPE(int32_t, int)
+  AC_CHECK_TYPE(u_int32_t, unsigned int)
+elif test "$ac_cv_sizeof_short" = 4 ; then
+  AC_CHECK_TYPE(int32_t, short)
+  AC_CHECK_TYPE(u_int32_t, unsigned short)
+elif test "$ac_cv_sizeof_long" = 4 ; then
+  AC_CHECK_TYPE(int32_t, long)
+  AC_CHECK_TYPE(u_int32_t, unsigned long)
+else
+  AC_MSG_ERROR([Cannot find a type with size of 32 bits])
+fi
+AC_CHECK_SIZEOF(rlim_t)
+if test "$ac_cv_sizeof_rlim_t" = 8 ; then
+AC_DEFINE(LONG_LONG_RLIM_T)
+fi
+])
+
+AC_DEFUN(CHECK_LIBCURL,
+[
+	AC_ARG_ENABLE(libcurl,
+	[AC_HELP_STRING([--enable-libcurl=DIR],[enable libcurl (remote include) support])],
+	[
+		CURLCFLAG=`$enableval/bin/curl-config --cflags`
+		CURLLIBS=`$enableval/bin/curl-config --libs`
+
+		dnl Ok this is ugly, basically we need to strip the version of c-ares that curl uses
+		dnl because we want to use our own version (which is hopefully fully binary
+		dnl compatible with the curl one as well).
+		dnl Therefore we need to strip the cares libs in a weird way...
+		dnl If anyone can come up with something better and still portable (no awk!?)
+		dnl then let us know.
+		if test "x`echo $CURLLIBS |grep ares`" != x ; then
+			dnl Attempt one: Linux sed
+			XCURLLIBS="`echo "$CURLLIBS"|sed -r 's/(@<:@^ @:>@+ @<:@^ @:>@+ )(@<:@^ @:>@+ @<:@^ @:>@+ )(.+)/\1\3/g' 2>/dev/null`"
+			if test x"$XCURLLIBS" = x; then
+				dnl Attempt two: FreeBSD (and others?) sed
+				XCURLLIBS="`echo "$CURLLIBS"|sed -E 's/(@<:@^ @:>@+ @<:@^ @:>@+ )(@<:@^ @:>@+ @<:@^ @:>@+ )(.+)/\1\3/g' 2>/dev/null`"
+				if test x"$XCURLLIBS" = x; then
+					AC_MSG_ERROR([sed appears to be broken. It is needed for a remote includes compile hack.])
+				fi
+			fi
+			CURLLIBS="$XCURLLIBS"
+		fi
+		
+		IRCDLIBS="$IRCDLIBS $CURLLIBS"
+		CFLAGS="$CFLAGS $CURLCFLAG -DUSE_LIBCURL"
+		URL="url.o"
+		AC_SUBST(URL)
+	])
+])
+
+dnl the following 2 macros are based on CHECK_SSL by Mark Ethan Trostler <trostler@juniper.net> 
+
+AC_DEFUN([CHECK_SSL],
+[
+AC_ARG_ENABLE(ssl,
+[AC_HELP_STRING([--enable-ssl=],[enable ssl will check /usr/local/ssl /usr/lib/ssl /usr/ssl /usr/pkg /usr/local /usr])],
+[ 
+AC_MSG_CHECKING(for openssl)
+    for dir in $enableval /usr/local/ssl /usr/lib/ssl /usr/ssl /usr/pkg /usr/local /usr; do
+        ssldir="$dir"
+        if test -f "$dir/include/openssl/ssl.h"; then
+	    AC_MSG_RESULT(found in $ssldir/include/openssl)
+            found_ssl="yes";
+	    if test ! "$ssldir" = "/usr" ; then
+                CFLAGS="$CFLAGS -I$ssldir/include";
+  	    fi
+            break;
+        fi
+        if test -f "$dir/include/ssl.h"; then
+	    AC_MSG_RESULT(found in $ssldir/include)
+            found_ssl="yes";
+	    if test ! "$ssldir" = "/usr" ; then
+	        CFLAGS="$CFLAGS -I$ssldir/include";
+	    fi
+            break
+        fi
+    done
+    if test x_$found_ssl != x_yes; then
+	AC_MSG_RESULT(not found)
+	echo ""
+	echo "Apparently you do not have both the openssl binary and openssl development libraries installed."
+	echo "You have two options:"
+	echo "a) Install the needed binaries and libraries"
+	echo "   and run ./Config"
+	echo "OR"
+	echo "b) If you don't need SSL..."
+	echo "   Run ./Config and say 'no' when asked about SSL"
+	echo ""
+	exit 1
+    else
+        CRYPTOLIB="-lssl -lcrypto";
+	if test ! "$ssldir" = "/usr" ; then
+           LDFLAGS="$LDFLAGS -L$ssldir/lib";
+        fi
+	AC_DEFINE(USE_SSL)
+    fi
+],
+)
+])
+
+AC_DEFUN([CHECK_ZLIB],
+[
+AC_ARG_ENABLE(ziplinks,
+[AC_HELP_STRING([--enable-ziplinks],[enable ziplinks will check /usr/local /usr /usr/pkg])],
+[ 
+AC_MSG_CHECKING(for zlib)
+    for dir in $enableval /usr/local /usr /usr/pkg; do
+        zlibdir="$dir"
+        if test -f "$dir/include/zlib.h"; then
+	    AC_MSG_RESULT(found in $zlibdir)
+            found_zlib="yes";
+	    if test "$zlibdir" = "/usr" ; then
+		CFLAGS="$CFLAGS -DZIP_LINKS";
+	    else
+	        CFLAGS="$CFLAGS -I$zlibdir/include -DZIP_LINKS";
+	    fi
+            break;
+        fi
+    done
+    if test x_$found_zlib != x_yes; then
+	AC_MSG_RESULT(not found)
+	echo ""
+	echo "Apparently you do not have the zlib development library installed."
+	echo "You have two options:"
+	echo "a) Install the zlib development library"
+	echo "   and run ./Config"
+	echo "OR"
+	echo "b) If you don't need compressed links..."
+	echo "   Run ./Config and say 'no' when asked about ziplinks support"
+	echo ""
+	exit 1
+    else
+        IRCDLIBS="$IRCDLIBS -lz";
+	if test "$zlibdir" != "/usr" ; then
+             LDFLAGS="$LDFLAGS -L$zlibdir/lib";
+	fi 
+        HAVE_ZLIB=yes
+    fi
+    AC_SUBST(HAVE_ZLIB)
+],
+)
+])

autoconf/configure.in

@@ -0,0 +1,507 @@
+dnl Process this file with autoconf to produce a configure script.
+AC_INIT(src/ircd.c)
+if test $# = 0; then
+	echo "You might want to run ./Config or provide some parameters to this script."
+	echo "./configure --help for information about this script"
+	exit 0
+fi
+AC_CONFIG_HEADER(include/setup.h)
+AC_PROG_CC
+if test "$ac_cv_prog_gcc" = "yes"; then
+CFLAGS="$CFLAGS -funsigned-char"
+AC_CACHE_CHECK(if gcc has a working -pipe, ac_cv_pipe, [
+	save_cflags="$CFLAGS"
+	CFLAGS="$CFLAGS -pipe"
+	AC_TRY_COMPILE(,, ac_cv_pipe="yes", ac_cv_pipe="no")
+	CFLAGS="$save_cflags"
+])
+if test "$ac_cv_pipe" = "yes"; then
+CFLAGS="-pipe $CFLAGS"
+fi
+fi
+
+dnl (the gcc flag detection trick is taken from xemacs/Vin Shelton)
+
+dnl UnrealIRCd might not be strict-aliasing safe at this time
+case "`$CC -v --help 2>&1`" in
+	*-fstrict-aliasing* ) CFLAGS="$CFLAGS -fno-strict-aliasing" ;;
+esac
+
+dnl Pointer signedness warnings are really a pain and 99.9% of the time
+dnl they are of absolutely no use whatsoever. IMO the person who decided
+dnl to enable this without -Wall should be shot on sight.
+case "`$CC -v --help 2>&1`" in
+	*-Wpointer-sign* ) CFLAGS="$CFLAGS -Wno-pointer-sign" ;;
+esac
+AC_PROG_CXX 
+AC_PATH_PROG(RM,rm)
+AC_PATH_PROG(CP,cp)
+AC_PATH_PROG(TOUCH,touch)
+AC_PATH_PROG(OPENSSLPATH,openssl)
+AC_PATH_PROG(INSTALL,install)
+AC_CHECK_PROG(MAKER, gmake, gmake, make)
+AC_PATH_PROG(GMAKE,gmake)
+AC_PATH_PROG(GUNZIP, gunzip)
+AC_PATH_PROG(PKGCONFIG, pkg-config)
+
+dnl Checks for libraries.
+AC_CHECK_LIB(descrypt, crypt, [AC_DEFINE(HAVE_CRYPT) IRCDLIBS="$IRCDLIBS-ldescrypt " MKPASSWDLIBS="-ldescrypt"],
+AC_CHECK_LIB(crypt, crypt,[ AC_DEFINE(HAVE_CRYPT) IRCDLIBS="$IRCDLIBS-lcrypt " MKPASSWDLIBS="-lcrypt"]))
+AC_CHECK_LIB(socket, socket,IRCDLIBS="$IRCDLIBS-lsocket " SOCKLIB="-lsocket")
+AC_CHECK_LIB(nsl, inet_ntoa,IRCDLIBS="$IRCDLIBS-lnsl " INETLIB="-lnsl")
+
+AC_SUBST(IRCDLIBS)
+AC_SUBST(MKPASSWDLIBS)
+
+dnl module checking based on Hyb7's module checking code
+AC_DEFUN([AC_ENABLE_DYN],
+[
+AC_CHECK_FUNC(dlopen,, [AC_CHECK_LIB(dl, dlopen,IRCDLIBS="$IRCDLIBS -ldl",
+[
+AC_MSG_WARN(Dynamic linking is not enabled because dlopen was not found) 
+AC_DEFINE(STATIC_LINKING)
+])])
+
+hold_cflags=$CFLAGS
+CFLAGS="$CFLAGS -export-dynamic"
+AC_CACHE_CHECK(if we need the -export-dynamic flag, ac_cv_export_dynamic, [
+AC_TRY_LINK(, [int i];, ac_cv_export_dynamic=yes, ac_cv_export_dynamic=no)])
+if test "$ac_cv_export_dynamic" = "no"; then
+CFLAGS=$hold_cflags
+fi
+
+AC_CACHE_CHECK(for compiler option to produce PIC,ac_cv_pic,[
+if test "$ac_cv_prog_gcc" = "yes"; then
+	ac_cv_pic="-fPIC -DPIC -shared"
+	case `uname -s` in
+		Darwin*[)]
+		ac_cv_pic="-bundle -flat_namespace -undefined suppress"
+		;;
+		HP-UX*[)]
+		ac_cv_pic="-fPIC"
+		;;
+	esac
+else
+case `uname -s` in
+	SunOS*[)]
+	ac_cv_pic="-KPIC -DPIC -G"
+	;;
+esac
+fi
+])
+AC_CACHE_CHECK(if your system prepends an underscore on symbols,ac_cv_underscore,[
+cat >uscore.c << __EOF__
+int main() {
+	return 0;
+}
+__EOF__
+$CC -o uscore $CFLAGS uscore.c 1>&5
+if test -z "`strings -a uscore |grep '^_main$'`"; then
+ac_cv_underscore=no
+else
+ac_cv_underscore=yes
+fi
+rm -f uscore uscore.c
+])
+if test "$ac_cv_underscore" = "yes"; then
+AC_DEFINE(UNDERSCORE)
+fi
+
+MODULEFLAGS=$ac_cv_pic
+AC_DEFINE(DYNAMIC_LINKING)
+])
+AC_DEFUN([AC_ENABLE_INET6],[
+AC_CACHE_CHECK(if your system has IPv6 support, ac_cv_ip6, [
+save_libs="$LIBS"
+LIBS="$LIBS $SOCKLIB"
+AC_TRY_RUN([
+#include <sys/types.h>
+#include <sys/socket.h>
+int main() {
+if (socket(AF_INET6, SOCK_STREAM, 0) < 0)
+exit(1);
+exit(0);
+}
+], ac_cv_ip6=yes, ac_cv_ip6=no)
+])
+if test "$ac_cv_ip6" = "no"; then
+AC_MSG_WARN(Your system does not support IPv6 so it will not be enabled)
+else
+AC_DEFINE(INET6)
+	dnl in6addr_any detection code taken from ratbox
+	AC_MSG_CHECKING([for struct in6addr_any])
+	AC_COMPILE_IFELSE(
+		[AC_LANG_PROGRAM(
+			[[#define IN_AUTOCONF
+			#include <sys/types.h>
+			#include <sys/socket.h>
+			#include <netinet/in.h>]],
+			[[struct in6_addr a = in6addr_any;]]
+		)],
+		[AC_MSG_RESULT(yes)],
+		[
+			AC_MSG_RESULT(no)
+			AC_DEFINE(NO_IN6ADDR_ANY)
+		]
+	)
+fi
+LIBS="$save_libs"
+])
+
+AC_CHECK_HEADER(sys/param.h,AC_DEFINE(PARAMH))
+AC_CHECK_HEADER(stdlib.h,AC_DEFINE(STDLIBH))
+AC_CHECK_HEADER(stddef.h,AC_DEFINE(STDDEFH))
+AC_CHECK_HEADER(sys/syslog.h,AC_DEFINE(SYSSYSLOGH))
+AC_CHECK_HEADER(unistd.h,AC_DEFINE(UNISTDH))
+AC_CHECK_HEADER(string.h,AC_DEFINE(STRINGH))
+AC_CHECK_HEADER(strings.h,AC_DEFINE(STRINGSH))
+AC_CHECK_HEADER(malloc.h,AC_DEFINE(MALLOCH,<malloc.h>))
+AC_CHECK_HEADER(sys/rusage.h,AC_DEFINE(RUSAGEH))
+AC_CHECK_HEADER(glob.h,AC_DEFINE(GLOBH))
+dnl Checks for typedefs, structures, and compiler characteristics.
+AC_C_CONST
+AC_C_INLINE
+AC_TYPE_SIZE_T
+AC_HEADER_TIME
+AC_STRUCT_TM
+AC_TYPE_UID_T
+unreal_CHECK_TYPE_SIZES
+
+AC_CACHE_CHECK(what kind of nonblocking sockets you have, ac_cv_nonblocking,[
+save_libs="$LIBS"
+LIBS="$LIBS $SOCKLIB"
+AC_TRY_RUN([
+#include <sys/types.h>
+#include <sys/socket.h>
+#include <fcntl.h>
+#include <sys/ioctl.h>
+#include <sys/file.h>
+#include <signal.h>
+alarmed() {
+exit(1);
+}
+int main() {
+#ifdef O_NONBLOCK
+char b[12], x[32];
+int f, l = sizeof(x);
+f = socket(AF_INET, SOCK_DGRAM, 0);
+if (f >= 0 && !(fcntl(f, F_SETFL, O_NONBLOCK))) {
+signal(SIGALRM, alarmed);
+alarm(3);
+recvfrom(f, b, 12, 0, (struct sockaddr *)x, &l);
+alarm(0);
+exit(0);
+}
+#endif
+exit(1);
+}
+],ac_cv_nonblocking=O_NONBLOCK,[
+AC_TRY_RUN([
+#include <sys/types.h>
+#include <sys/socket.h>
+#include <fcntl.h>
+#include <sys/ioctl.h>
+#include <sys/file.h>
+#include <signal.h>
+alarmed() {
+exit(0);
+}
+int main() {
+#ifdef O_NDELAY
+char b[12], x[32];
+int f, l = sizeof(x);
+f = socket(AF_INET, SOCK_DGRAM, 0);
+if (f >= 0 && !(fcntl(f, F_SETFL, O_NDELAY))) {
+signal(SIGALRM, alarmed);
+alarm(3);
+recvfrom(f, b, 12, 0, (struct sockaddr *)x, &l);
+alarm(0);
+exit(0);
+}
+#endif
+exit(1);
+}],ac_cv_nonblocking=O_NDELAY,[
+AC_TRY_RUN([
+#include <sys/types.h>
+#include <sys/socket.h>
+#include <fcntl.h>
+#include <sys/ioctl.h>
+#include <sys/file.h>
+#include <signal.h>
+alarmed() {
+exit(1);
+}
+int main() {
+#ifdef FIONBIO
+char b[12], x[32];
+int f, l = sizeof(x);
+f = socket(AF_INET, SOCK_DGRAM, 0);
+if (f >= 0 && !(fcntl(f, F_SETFL, FIONBIO))) {
+signal(SIGALRM, alarmed);
+alarm(3);
+recvfrom(f, b, 12, 0, (struct sockaddr *)x, &l);
+alarm(0);
+exit(0);
+}
+#endif
+exit(1);
+], ac_cv_nonblocking=FIONBIO,ac_cv_nonblocking=none)])])])
+if test "$ac_cv_nonblocking" = "O_NONBLOCK"; then
+AC_DEFINE(NBLOCK_POSIX)
+elif test "$ac_cv_nonblocking" = "O_NDELAY"; then
+AC_DEFINE(NBLOCK_BSD)
+elif test "$ac_cv_nonblocking" = "FIONBIO"; then
+AC_DEFINE(NBLOCK_SYSV)
+fi
+LIBS="$save_libs"
+dnl Checks for library functions.
+AC_PROG_GCC_TRADITIONAL
+AC_FUNC_SETPGRP
+AC_FUNC_SETVBUF_REVERSED
+AC_FUNC_ALLOCA
+AC_CHECK_FUNCS(snprintf,AC_DEFINE(HAVE_SNPRINTF))
+AC_CHECK_FUNCS(vsnprintf,AC_DEFINE(HAVE_VSNPRINTF))
+AC_CHECK_FUNCS(strlcpy, AC_DEFINE(HAVE_STRLCPY))
+AC_CHECK_FUNCS(strlcat, AC_DEFINE(HAVE_STRLCAT))
+AC_CHECK_FUNCS(strlncat, AC_DEFINE(HAVE_STRLNCAT))
+AC_CHECK_FUNCS(inet_pton, AC_DEFINE(HAVE_INET_PTON))
+AC_CHECK_FUNCS(inet_ntop, AC_DEFINE(HAVE_INET_NTOP))
+dnl Check if it supports C99 style variable length arrays
+AC_CACHE_CHECK(if C99 variable length arrays are supported, ac_cv_varlen_arrays, [
+AC_TRY_COMPILE(,[
+int main() {
+int i = 5;
+int a[i];
+a[0] = 1;
+return 0;
+}], ac_cv_varlen_arrays=yes, ac_cv_varlen_arrays=no)
+])
+if test "$ac_cv_varlen_arrays" = "yes" ; then
+	AC_DEFINE(HAVE_C99_VARLEN_ARRAY)
+fi
+AC_CACHE_CHECK(if we can set the core size to unlimited, ac_cv_force_core,[
+AC_TRY_RUN([
+#include <sys/time.h>
+#include <sys/resource.h>
+#include <unistd.h>
+int main() {
+struct rlimit corelim;
+corelim.rlim_cur = corelim.rlim_max = RLIM_INFINITY;
+if (setrlimit(RLIMIT_CORE, &corelim))
+exit(1);
+exit(0);
+}
+],ac_cv_force_core=yes,ac_cv_force_core=no)
+])
+if test "$ac_cv_force_core" = "yes"; then
+AC_DEFINE(FORCE_CORE)
+fi
+AC_FUNC_VPRINTF
+AC_CHECK_FUNCS(gettimeofday,AC_DEFINE(GETTIMEOFDAY),[AC_CHECK_FUNCS(lrand48,AC_DEFINE(LRADN48))])
+AC_CHECK_FUNCS(getrusage,AC_DEFINE(GETRUSAGE_2),[AC_CHECK_FUNCS(times,AC_DEFINE(TIMES_2))])
+AC_CHECK_FUNCS(setproctitle,AC_DEFINE(HAVE_SETPROCTITLE),[
+AC_CHECK_LIB(util,setproctitle,AC_DEFINE(HAVE_SETPROCTITLE) IRCDLIBS="$IRCDLIBS-lutil",[
+AC_EGREP_HEADER([#define.*PS_STRINGS.*],sys/exec.h,AC_DEFINE(HAVE_PSSTRINGS),[
+AC_CHECK_FUNCS(pstat,AC_DEFINE(HAVE_PSTAT))
+])
+])
+])
+AC_CACHE_CHECK(what type of signals you have, ac_cv_sigtype, [
+AC_TRY_RUN([
+#include <signal.h>
+int main() {
+sigaction(SIGTERM, (struct sigaction *)0L, (struct sigaction *)0L);
+}
+], ac_cv_sigtype=POSIX, [
+AC_TRY_RUN([
+#include <signal.h>
+int	calls = 0;
+void	handler()
+{
+if (calls)
+return;
+calls++;
+kill(getpid(), SIGTERM);
+sleep(1);
+}
+
+int main() {
+signal(SIGTERM, handler);
+kill(getpid(), SIGTERM);
+exit(0);
+}
+], ac_cv_sigtype=BSD,ac_cv_sigtype=SYSV)])])
+
+if test "$ac_cv_sigtype" = "POSIX"; then
+AC_DEFINE(POSIX_SIGNALS)
+elif test "$ac_cv_sigtype" = "BSD"; then
+AC_DEFINE(BSD_RELIABLE_SIGNALS)
+else
+AC_DEFINE(SYSV_UNRELIABLE_SIGNALS)
+fi 
+AC_CHECK_FUNCS(strtoken,,AC_DEFINE(NEED_STRTOKEN))
+AC_CHECK_FUNCS(strtok,,AC_DEFINE(NEED_STRTOK))
+AC_CHECK_FUNCS(strerror,,AC_DEFINE(NEED_STRERROR))
+AC_CHECK_FUNCS(index,,AC_DEFINE(NOINDEX))
+AC_CHECK_FUNCS(strtoul,,STRTOUL="strtoul.o")
+AC_CHECK_FUNCS(bcopy,,AC_DEFINE(NEED_BCOPY))
+AC_CHECK_FUNCS(bcmp,,AC_DEFINE(NEED_BCMP))
+AC_CHECK_FUNCS(bzero,,AC_DEFINE(NEED_BZERO))
+AC_CHECK_FUNCS(strcasecmp,AC_DEFINE(GOT_STRCASECMP))
+save_libs="$LIBS"
+LIBS="$LIBS $SOCKLIB $INETLIB"
+AC_CHECK_FUNCS(inet_addr,,AC_DEFINE(NEED_INET_ADDR))
+AC_CHECK_FUNCS(inet_ntoa,,AC_DEFINE(NEED_INET_NTOA))
+AC_CHECK_FUNCS(inet_netof,,AC_DEFINE(NEED_INET_NETOF))
+LIBS="$save_libs"
+AC_CHECK_FUNCS(syslog,AC_DEFINE(HAVE_SYSLOG))
+AC_CHECK_FUNCS(vsyslog,AC_DEFINE(HAVE_VSYSLOG))
+AC_SUBST(STRTOUL)
+AC_SUBST(CRYPTOLIB)
+AC_SUBST(MODULEFLAGS)
+AC_ARG_WITH(listen, [AC_HELP_STRING([--with-listen=backlog],[Specify the listen backlog value])],
+AC_DEFINE_UNQUOTED(LISTEN_SIZE,$withval),AC_DEFINE(LISTEN_SIZE,5))
+AC_ARG_WITH(nick-history, [AC_HELP_STRING([--with-nick-history=length],[Specify the length of the nickname history])],
+AC_DEFINE_UNQUOTED(NICKNAMEHISTORYLENGTH,$withval), AC_DEFINE(NICKNAMEHISTORYLENGTH,2000))
+AC_ARG_WITH(sendq, [AC_HELP_STRING([--with-sendq=maxsendq],[Specify the max sendq for the server])],
+AC_DEFINE_UNQUOTED(MAXSENDQLENGTH,$withval),AC_DEFINE(MAXSENDQLENGTH,3000000))
+AC_ARG_WITH(bufferpool, [AC_HELP_STRING([--with-bufferpool=size],[Specify the size of the buffer pool])],
+AC_DEFINE_UNQUOTED(BUFFERPOOL,[($withval * MAXSENDQLENGTH)]),AC_DEFINE(BUFFERPOOL,[(18 * MAXSENDQLENGTH)]))
+AC_ARG_WITH(permissions, [AC_HELP_STRING([--with-permissions=permissions],[Specify the default permissions for
+configuration files])], AC_DEFINE_UNQUOTED(DEFAULT_PERMISSIONS,$withval), AC_DEFINE(DEFAULT_PERMISSIONS, 0600)) 
+AC_ARG_WITH(dpath, [AC_HELP_STRING([--with-dpath=path],[Specify the path where configuration files are stored])],
+AC_DEFINE_UNQUOTED(DPATH, "$withval") IRCDDIR="$withval", AC_DEFINE_UNQUOTED(DPATH,"`pwd`") IRCDDIR="`pwd`")
+AC_ARG_WITH(fd-setsize, [AC_HELP_STRING([--with-fd-setsize=size],[Specify the max file descriptors to use])],
+ac_fd=$withval, ac_fd=1024)
+AC_DEFINE_UNQUOTED(MAXCONNECTIONS, $ac_fd)
+AC_ARG_WITH(spath, [AC_HELP_STRING([--with-spath],[Specify the location of the executable])],
+AC_DEFINE_UNQUOTED(SPATH,"$withval/ircd") BINDIR="$withval",AC_DEFINE_UNQUOTED(SPATH,"`pwd`/src/ircd") BINDIR="`pwd`/src/ircd")
+AC_ARG_ENABLE(nospoof, [AC_HELP_STRING([--enable-nospoof],[Enable spoofing protection])], AC_DEFINE(NOSPOOF))
+AC_ARG_ENABLE(prefixaq, [AC_HELP_STRING([--enable-prefixaq],[Enable chanadmin and chanowner prefixes])], AC_DEFINE(PREFIX_AQ))
+AC_ARG_ENABLE(hub, [AC_HELP_STRING([--enable-hub],[Compile as a hub server])], AC_DEFINE(HUB))
+AC_ARG_WITH(showlistmodes, [AC_HELP_STRING([--with-showlistmodes], [Specify whether modes are shown in /list])],
+	AC_DEFINE(LIST_SHOW_MODES))
+AC_ARG_WITH(topicisnuhost, [AC_HELP_STRING([--with-topicisnuhost], [Display nick!user@host as the topic setter])],
+	AC_DEFINE(TOPIC_NICK_IS_NUHOST))
+AC_ARG_WITH(shunnotices, [AC_HELP_STRING([--with-shunnotices], [Notify a user when he/she is no longer shunned])],
+	AC_DEFINE(SHUN_NOTICES))
+AC_ARG_WITH(no-operoverride, [AC_HELP_STRING([--with-no-operoverride], [Disable OperOverride])],
+	AC_DEFINE(NO_OPEROVERRIDE))
+AC_ARG_WITH(disableusermod, [AC_HELP_STRING([--with-disableusermod], [Disable /set* and /chg*])],
+	AC_DEFINE(DISABLE_USERMOD))
+AC_ARG_WITH(operoverride-verify, [AC_HELP_STRING([--with-operoverride-verify], [Require opers to invite themselves to +s/+p channels])],
+	AC_DEFINE(OPEROVERRIDE_VERIFY))
+AC_ARG_WITH(disable-extendedban-stacking, [AC_HELP_STRING([--with-disable-extendedban-stacking], [Disable extended ban stacking])],
+	AC_DEFINE(DISABLE_STACKED_EXTBANS))
+MODULES_WHICH=commandsandmodules
+AC_MSG_CHECKING(for how much module building work we need to do)
+AC_ARG_WITH(moduleswhich,
+[  --with-moduleswhich=onlycommands|onlymodules|commandsandmodules      What modules to build],
+[ case "$withval" in
+  yes|no)
+  ;;
+  * )
+    MODULES_WHICH="$withval"
+    ;;
+  esac])
+AC_SUBST(MODULES_WHICH)
+AC_MSG_RESULT($MODULES_WHICH)
+CHECK_SSL
+CHECK_ZLIB
+CHECK_LIBCURL
+AC_ARG_ENABLE(dynamic-linking, [AC_HELP_STRING([--enable-dynamic-linking],[Make the IRCd dynamically link shared objects rather than statically])], [AC_ENABLE_DYN], [AC_DEFINE(STATIC_LINKING)])
+AC_ARG_ENABLE(inet6, [AC_HELP_STRING([--enable-inet6],[Make the IRCd support IPv6])], [AC_ENABLE_INET6])
+AC_SUBST(IRCDDIR)
+AC_SUBST(BINDIR)
+AC_MSG_CHECKING(if FD_SETSIZE is large enough to allow $ac_fd file descriptors)
+AC_TRY_RUN([
+#include <sys/types.h>
+#include <sys/time.h>
+int main() {
+if (FD_SETSIZE >= $ac_fd)
+exit(0);
+exit(1);
+}
+], AC_MSG_RESULT(yes), [
+FD_SETSIZE="-DFD_SETSIZE=$ac_fd"
+AC_MSG_RESULT(no)
+])
+AC_SUBST(FD_SETSIZE)
+case `uname -s` in
+*SunOS*)
+CFLAGS="$CFLAGS -D_SOLARIS"
+IRCDLIBS="$IRCDLIBS -lresolv "
+;;
+*solaris*)
+CFLAGS="$CFLAGS -D_SOLARIS"
+IRCDLIBS="$IRCDLIBS -lresolv "
+;;
+esac
+
+dnl REMEMBER TO CHANGE WITH A NEW PCRE RELEASE!
+tre_version="7.2"
+AC_MSG_RESULT(extracting PCRE regex library)
+cur_dir=`pwd`
+cd extras
+dnl remove old tre directory to force a recompile...
+rm -rf pcre-$tre_version
+if test "x$ac_cv_path_GUNZIP" = "x" ; then
+	tar xfz pcre.tar.gz
+else
+	cp pcre.tar.gz pcre.tar.gz.bak
+	gunzip -f pcre.tar.gz
+	cp pcre.tar.gz.bak pcre.tar.gz
+	tar xf pcre.tar
+fi
+AC_MSG_RESULT(configuring PCRE regex library)
+cd pcre-$tre_version
+./configure --disable-shared --disable-system-abi --disable-utf8 --prefix=$cur_dir/extras/regexp || exit 1
+AC_MSG_RESULT(compiling PCRE regex library)
+$ac_cv_prog_MAKER || exit 1
+AC_MSG_RESULT(installing PCRE regex library)
+$ac_cv_prog_MAKER install || exit 1
+TREINCDIR="$cur_dir/extras/regexp/include"
+AC_SUBST(TREINCDIR)
+if test "x$ac_cv_path_PKGCONFIG" = "x" ; then
+	TRELIBS="-L../extras/regexp/lib -lpcreposix -lpcre"
+else
+	TRELIBS="`$ac_cv_path_PKGCONFIG --libs libpcre.pc` -lpcreposix -lpcre" 
+fi
+AC_SUBST(TRELIBS)
+cd $cur_dir
+
+
+dnl REMEMBER TO CHANGE WITH A NEW C-ARES RELEASE!
+cares_version="1.4.0"
+AC_MSG_RESULT(extracting c-ares resolver library)
+cur_dir=`pwd`
+cd extras
+dnl remove old c-ares directory to force a recompile...
+rm -rf c-ares-$cares_version
+if test "x$ac_cv_path_GUNZIP" = "x" ; then
+	tar xfz c-ares.tar.gz
+else
+	cp c-ares.tar.gz c-ares.tar.gz.bak
+	gunzip -f c-ares.tar.gz
+	cp c-ares.tar.gz.bak c-ares.tar.gz
+	tar xf c-ares.tar
+fi
+AC_MSG_RESULT(configuring c-ares library)
+cd c-ares-$cares_version
+./configure --prefix=$cur_dir/extras/c-ares || exit 1
+AC_MSG_RESULT(compiling c-ares resolver library)
+$ac_cv_prog_MAKER || exit 1
+AC_MSG_RESULT(installing c-ares resolver library)
+$ac_cv_prog_MAKER install || exit 1
+CARESINCDIR="$cur_dir/extras/c-ares/include"
+AC_SUBST(CARESINCDIR)
+CARESLIBDIR="-L../extras/c-ares/lib"
+AC_SUBST(CARESLIBDIR)
+CARESLIBS="-lcares"
+AC_SUBST(CARESLIBS)
+cd $cur_dir
+
+
+AC_OUTPUT(Makefile src/modules/Makefile src/modules/chanmodes/Makefile unreal ircdcron/ircdchk)
+chmod 0700 unreal
+chmod 0700 ircdcron/ircdchk

badwords.channel.conf

@@ -0,0 +1,52 @@
+/*  
+ Unreal Internet Relay Chat Daemon
+ Copyright (C) Carsten V. Munk 2000
+
+ NOTE: Those words are not meant to insult you (the user)
+       but is meant to be a list of words so that the +G channel/user mode 
+       will work properly. You can easily modify this file at your will.
+       If you got words to add to this file, please mail badwords@tspre.org
+
+ 
+
+
+
+ 
+                This is some filling space, scroll down to see the words
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+*/
+badword channel { word "pussy"; };
+badword channel { word "fuck"; };
+badword channel { word "whore"; };
+badword channel { word "slut"; };
+badword channel { word "shit"; };
+badword channel { word "asshole"; };
+badword channel { word "bitch"; };
+badword channel { word "cunt"; };
+badword channel { word "vagina"; };
+badword channel { word "penis"; };
+badword channel { word "jackass"; };
+badword channel { word "*fucker*"; };
+badword channel { word "faggot"; };
+badword channel { word "fag"; };
+badword channel { word "horny"; };
+badword channel { word "gay"; };
+badword channel { word "dickhead"; };
+badword channel { word "sonuvabitch"; };
+badword channel { word "*fuck*"; };
+badword channel { word "tits"; };

badwords.message.conf

@@ -0,0 +1,52 @@
+/*  
+ Unreal Internet Relay Chat Daemon
+ Copyright (C) Carsten V. Munk 2000
+
+ NOTE: Those words are not meant to insult you (the user)
+       but is meant to be a list of words so that the +G channel/user mode 
+       will work properly. You can easily modify this file at your will.
+       If you got words to add to this file, please mail badword messages@tspre.org
+
+ 
+
+
+
+ 
+                This is some filling space, scroll down to see the words
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+*/
+badword message { word "pussy"; };
+badword message { word "fuck"; };
+badword message { word "whore"; };
+badword message { word "slut"; };
+badword message { word "shit"; };
+badword message { word "asshole"; };
+badword message { word "bitch"; };
+badword message { word "cunt"; };
+badword message { word "vagina"; };
+badword message { word "penis"; };
+badword message { word "jackass"; };
+badword message { word "*fucker*"; };
+badword message { word "faggot"; };
+badword message { word "fag"; };
+badword message { word "horny"; };
+badword message { word "gay"; };
+badword message { word "dickhead"; };
+badword message { word "sonuvabitch"; };
+badword message { word "*fuck*"; };
+badword message { word "tits"; };

badwords.quit.conf

@@ -0,0 +1,52 @@
+/*  
+ Unreal Internet Relay Chat Daemon
+ Copyright (C) Carsten V. Munk 2000
+
+ NOTE: Those words are not meant to insult you (the user)
+       but is meant to be a list of words so that quit message censoring 
+       will work properly. You can easily modify this file at your will.
+       If you got words to add to this file, please mail badword badwords@tspre.org
+
+ 
+
+
+
+ 
+                This is some filling space, scroll down to see the words
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+*/
+badword quit { word "pussy"; };
+badword quit { word "fuck"; };
+badword quit { word "whore"; };
+badword quit { word "slut"; };
+badword quit { word "shit"; };
+badword quit { word "asshole"; };
+badword quit { word "bitch"; };
+badword quit { word "cunt"; };
+badword quit { word "vagina"; };
+badword quit { word "penis"; };
+badword quit { word "jackass"; };
+badword quit { word "*fucker*"; };
+badword quit { word "faggot"; };
+badword quit { word "fag"; };
+badword quit { word "horny"; };
+badword quit { word "gay"; };
+badword quit { word "dickhead"; };
+badword quit { word "sonuvabitch"; };
+badword quit { word "*fuck*"; };
+badword quit { word "tits"; };

bsdinstall

@@ -1,84 +0,0 @@
-#! /bin/sh
-#
-# $Id$
-# Old: @(#)install.sh	4.5	(Berkeley)	10/12/83
-#
-cmd=/bin/mv
-strip=""
-chmod="/bin/chmod 755"
-chown="chown -f root"
-chgrp="/bin/chgrp -f bin"
-while true ; do
-	case $1 in
-		-s )	strip="strip"
-			shift
-			;;
-		-c )	cmd="/bin/cp"
-			shift
-			;;
-		-m )	chmod="/bin/chmod $2"
-			shift
-			shift
-			;;
-		-o )	chown="/etc/chown -f $2"
-			shift
-			shift
-			;;
-		-g )	chgrp="/bin/chgrp -f $2"
-			shift
-			shift
-			;;
-		-d )	cmd="/bin/mkdir"
-			shift
-			;;
-		* )	break
-			;;
-	esac
-done
-
-if [ ! ${2-""} ]
-then	echo "install: no destination specified"
-	exit 1
-fi
-if [ ${3-""} ]
-then	echo "install: too many files specified -> $*"
-	exit 1
-fi
-if [ $1 = $2 -o $2 = . ]
-then	echo "install: can't move $1 onto itself"
-	exit 1
-fi
-case $cmd in
-/bin/mkdir )
-	file=$2/$1
-	;;
-* )
-	if [ '!' -f $1 ]
-	then	echo "install: can't open $1"
-		exit 1
-	fi
-	if [ -d $2 ]
-	then	file=$2/$1
-	else	file=$2
-	fi
-	/bin/rm -f $file
-	;;
-esac
-
-case $cmd in
-/bin/mkdir )
-	if [ ! -d "$file" ]
-	then	$cmd $file
-	fi
-	;;
-* )
-	$cmd $1 $file
-	if [ $strip ]
-	then	$strip $file
-	fi
-	;;
-esac
-
-$chown $file
-$chgrp $file
-$chmod $file

crypt/Makefile

@@ -1,38 +0,0 @@
-#************************************************************************
-#*   IRC - Internet Relay Chat, ircd/crypt/Makefile
-#*   Copyright (C) 1991 Darren Reed
-#*
-#*   This program is free software; you can redistribute it and/or modify
-#*   it under the terms of the GNU General Public License as published by
-#*   the Free Software Foundation; either version 1, or (at your option)
-#*   any later version.
-#*
-#*   This program is distributed in the hope that it will be useful,
-#*   but WITHOUT ANY WARRANTY; without even the implied warranty of
-#*   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#*   GNU General Public License for more details.
-#*
-#*   You should have received a copy of the GNU General Public License
-#*   along with this program; if not, write to the Free Software
-#*   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-#*
-#*   $Id$
-#*/
-#
-# Change this to the path of your local ircd.conf file
-#
-
-IRCDCONF = ../ircd.conf
-
-all: mkpasswd
-crypt: install
-
-mkpasswd: mkpasswd.c
-	cc -lcrypt -O mkpasswd.c -o mkpasswd
-
-install:
-	crypter ${IRCDCONF}
-	@echo 'done.'
-
-clean:
-	/bin/rm -f mkpasswd

crypt/README

@@ -1,63 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, ircd/crypt/README
- *   Copyright (C) 1991 Nelson Minar
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- * 
- *   $Id$
- */
-
-The change implemented here is that the operator password in irc.conf
-is no longer stored in plaintext form, but is encrypted the same way
-that user passwords are encrypted on normal UNIX systems. Ie, instead
-of having
-
-	O:*:goodboy:Nelson
-
-in your ircd.conf file, you have
-
-	O:*:sCnvYRmbFJ7oI:Nelson
-
-You still type "/oper Nelson goodboy" to become operator. However, if
-someone gets ahold of your irc.conf file, they can no longer figure
-out what the password is from reading it.  There are still other
-security holes, namely server-server passwords, but this closes one
-obvious problem.
-
-So how do you generate these icky looking strings for passwords?
-There's a simple program called mkpasswd to do that for you.  Just run
-mkpasswd, and at the prompt type in your plaintext password.  It will
-spit out the encrypted password, which you should then just copy into
-the irc.conf file. This should be done only when adding new passwords
-to your irc.conf file. To change over your irc.conf file to use
-encrypted passwords, define CRYPT_OPER_PASSWORD in config.h. You will
-need to recompile your server if you already compiled it with this
-feature disabled. Once compiled, edit the Makefile in this directory
-and chang "IRCDCONF" to your irc.conf file. Then "make install" in this
-directory to replace all the operator passwords in your irc.conf file
-with the encrypted format.
-
-Choose your passwords carefully. Do not choose something in a
-dictionary, make sure its at least 5 characters. Anything past 8
-characters is ignored.
-
-One thing to note about crypt() passwords - for every plaintext, there
-are 4096 different passwords. Some valid encryptions of "goodboy"
-include t1Ub2RhRQHd4g sCnvYRmbFJ7oI and Xr4Z.Kg5tcdy6. The first
-two characters (the "salt") determine which of the 4096 passwords
-you will get. mkpasswd chooses the salt randomly, or alternately
-will let you specify one on the command line.
-
-see also - crypt(3)

crypt/crypter

@@ -1,55 +0,0 @@
-#!/usr/local/bin/perl
-#************************************************************************
-#*   IRC - Internet Relay Chat, ircd/crypt/crypter
-#*   Copyright (C) 1991 Sean Batt
-#*
-#*   This program is free software; you can redistribute it and/or modify
-#*   it under the terms of the GNU General Public License as published by
-#*   the Free Software Foundation; either version 1, or (at your option)
-#*   any later version.
-#*
-#*   This program is distributed in the hope that it will be useful,
-#*   but WITHOUT ANY WARRANTY; without even the implied warranty of
-#*   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#*   GNU General Public License for more details.
-#*
-#*   You should have received a copy of the GNU General Public License
-#*   along with this program; if not, write to the Free Software
-#*   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-#*
-#*   $Id$
-#*
-#*/
-
-#From Sean Batt sean@coombs.anu.edu.au
-#
-#Temporary output file
-#
-$tmpfile = "/tmp/ircd.conf.tmp";
-
-#
-#Original ircd.conf file
-#
-$ircdconf = @ARGV[0];
-
-print "crypting ",$ircdconf,"\n";
-@saltset = ('a' .. 'z', 'A' .. 'Z', '0' .. '9', '.', '/');
-
-umask(0077);
-open ($ircdout, ">/tmp/ircd.conf.tmp") || die "open $!";
-
-while ($text = <>) {
-#if its not an "O" line we can ignore it
-    $text =~ /^o/i || print ($ircdout $text) && next;
-    chop($text);
-    @oline = split(':', $text);
-    $salt = $saltset[rand(time)%64].$saltset[(rand(time)>>6)%64];
-    $oline[2] = crypt(@oline[2], $salt);
-    print ($ircdout join(':',@oline)."\n");
-}
-close ($ircdout);
-close ($ircdin);
-print "/bin/cp ",$tmpfile," ",$ircdconf,"\n";
-(fork()==0) ? exec("/bin/cp", $tmpfile, $ircdconf) : wait;
-
-#unlink($tmpfile);

crypt/mkpasswd.c

@@ -1,43 +0,0 @@
-/* simple password generator by Nelson Minar (minar@reed.edu)
- * copyright 1991, all rights reserved.
- * You can use this code as long as my name stays with it.
- *
- * $Id$
- *
- */
-
-#include <stdio.h>
-#include <stdlib.h>
-#include <string.h>
-
-extern char *getpass();
-
-int main(argc, argv)
-int argc;
-char *argv[];
-{
-  static char saltChars[] = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789./";
-  char salt[3];
-  char * plaintext;
-  int i;
-
-  if (argc < 2) {
-    srandom(time(0));		/* may not be the BEST salt, but its close */
-    salt[0] = saltChars[random() % 64];
-    salt[1] = saltChars[random() % 64];
-    salt[2] = 0;
-  }
-  else {
-    salt[0] = argv[1][0];
-    salt[1] = argv[1][1];
-    salt[2] = '\0';
-    if ((strchr(saltChars, salt[0]) == NULL) || (strchr(saltChars, salt[1]) == NULL))
-      fprintf(stderr, "illegal salt %s\n", salt), exit(1);
-  }
-
-  plaintext = getpass("Enter Password: ");
-
-  printf("Encryption: %s\n", crypt(plaintext, salt));
-  return 0;
-}
-

curlinstall

@@ -0,0 +1,66 @@
+#!/bin/sh
+
+if test "x$1" = x -o "x$2" = x ; then
+	echo "Syntax:"
+	echo "curlinstall ares_path libcurl_path"
+	echo ""
+	exit 1
+fi
+
+if [ "`eval echo -n 'a'`" = "-n a" ] ; then
+        c="\c"
+else
+        n="-n"
+fi
+
+save_PWD=`pwd`
+echo "Installing ares"
+cd $1
+./configure --prefix=$HOME/ares && make && make install
+
+SSLFLAG=""
+while [ -z "$SSLFLAG" ] ; do
+	echo ""
+	echo "Should libcurl be built with SSL support?"
+	echo $n "-> " $c
+	read cc
+	case "$cc" in
+		[Yy]*)
+			SSLFLAG="--with-ssl"
+			;;
+		[Nn]*)
+			SSLFLAG="--without-ssl"
+			;;
+		*)
+			echo ""
+		        echo "You must enter either Yes or No"
+			;;
+	esac
+done
+if [ -f $HOME/ares/lib/libcares.a ] ; then
+	if [ -f $HOME/ares/lib/libares.a ] ; then
+		rm -f $HOME/ares/lib/libares.a
+	fi
+	cp $HOME/ares/lib/libcares.a $HOME/ares/lib/libares.a
+fi
+
+echo "Installing libcurl"
+cd $2
+CPPFLAGS="-I$HOME/ares/include" ./configure --prefix=$HOME/curl --disable-shared \
+ --disable-thread --enable-ares=$HOME/ares --disable-ipv6 $SSLFLAG
+cp -R $HOME/ares/lib ares
+make && make install
+
+if [ -f $HOME/curl/lib/libares.a ] ; then
+	rm -f $HOME/curl/lib/libares.a
+fi
+cp $HOME/ares/lib/libares.a $HOME/curl/lib
+
+cd $save_PWD
+
+echo ""
+echo ""
+echo "libcurl has been installed. When running ./Config specify:"
+echo "$HOME/curl"
+echo "for the directory you installed libcurl to."
+

dccallow.conf

@@ -0,0 +1,42 @@
+/* Example of a possible semi-secure /DCCALLOW configuration written by Syzop.
+ * $Id$
+ *
+ * Actually nothing is *100% secure*... there could still be
+ * bugs in the software itself (think: a winamp bug that can
+ * be exploited via an mp3, or: a wmplayer bug that can be
+ * exploited via a specially crafted .wmv, etc..).
+ * If you are really that paranoid you could just remove
+ * all 'allow dcc'-blocks and prompt the user for EVERY file ;).
+ * 
+ * Still, I think this file is a good tradeoff between userfriendlyness
+ * and security. Note that when you try to only DENY specific
+ * file type (exe, com, etc) you are *guaranteed* to miss ones
+ * (like: did you know .r17 gets treated as a rar archive?
+ *  and that an exe can be disguished as .cmd which is executable
+ *  on nt/w2k/xp?)
+ */
+
+/* first.. deny everything, then allow known-good stuff... */
+deny dcc { filename "*"; reason "Possible executable content"; soft yes; };
+/* common image formats */
+allow dcc { filename "*.jpg"; soft yes; };
+allow dcc { filename "*.jpeg"; soft yes; };
+allow dcc { filename "*.gif"; soft yes; };
+allow dcc { filename "*.png"; soft yes; };
+allow dcc { filename "*.bmp"; soft yes; };
+/* audio / video (but not scripted/playlists!) */
+allow dcc { filename "*.mp1"; soft yes; };
+allow dcc { filename "*.mp2"; soft yes; };
+allow dcc { filename "*.mp3"; soft yes; };
+allow dcc { filename "*.mpg"; soft yes; };
+allow dcc { filename "*.mpeg"; soft yes; };
+allow dcc { filename "*.m1v"; soft yes; };
+allow dcc { filename "*.m2v"; soft yes; };
+allow dcc { filename "*.vob"; soft yes; };
+allow dcc { filename "*.wav"; soft yes; };
+/* text / misc */
+allow dcc { filename "*.txt"; soft yes; };
+allow dcc { filename "*.log"; soft yes; };
+allow dcc { filename "*.pdf"; soft yes; };
+allow dcc { filename "*.c"; soft yes; };
+allow dcc { filename "*.cpp"; soft yes; };

doc/ADD-TO-IRCRC

@@ -1,72 +0,0 @@
-# $Id$
-
-on ^367 * if ([$4] != []) {echo *** $1 \($3 - $stime($4)) $2} {echo *** $1-}
-on ^333 * echo *** Topic for $1 set by $2 on $stime($3)
-on ^317 * if (index(012345679 $3) != -1) {echo *** $1 has been idle for $2 seconds.  Signon at $stime($3)} {echo *** $1 has been idle for $2 seconds.}
-On ^329 "*" echo *** $1 : created $stime($2)
-on ^
-alias silence quote silence
-alias sile quote silence
-on ^raw_irc "% SILENCE %" echo *** $*
-
-@ hideit = 0
-on ^server_notice "% % NOTICE -- CLIENT*" if (hideit != 1) {echo *** $2-}
-alias show @ hideit = 0;echo *** You can now see clients connecting/exiting
-alias hide @ hideit = 1;echo *** You will no longer see clients connecting/exiting
-
-
-# ctime and sendq written by bry
-# modified by Mmmm
-
-alias ctime { 
-	^on 211 -
-        if ( [$0] )
-           { ^assign SS $0- }
-           { ^assign SS $S }
-
-^on ^211 * {
-        eval ^assign hrs2 ${ ([$7]/60)/60}
-        eval ^assign min2 ${[$7]/60}
-
-        eval ^assign dys ${[$HRS2]/24}
-        eval ^assign hrs ${[$HRS2]-([$DYS]*24)}
-        eval ^assign min ${[$MIN2] - ( ([$HRS]+([$DYS]*24) )*60)}
-        eval ^assign sec ${[$7]-([$MIN2]*60)}
-        @ a = index(\[ $1) - 1
-        @ b = left($a $1)
-        if (index(. $b) == -1)
-	 {eval echo *** $1 $[2]DYS days, $[2]HRS hrs, $[2]MIN min, $[2]SEC s}
-	 {eval echo *** $1 $[2]DYS days, $[2]HRS hrs, $[2]MIN min, $[2]SEC s}
-        }
-        ^stats l $SS
-}
-
-alias sendq {
-	eval ^on ^211 "$SRV *" {
-               @ a = index(\[ $1) - 1
-               @ b = left($a $1)
-               if (index(. $b) == -1)
-	          {eval echo *** $[11]2 sendq $1}
-	          {eval echo *** $[11]2 sendq $1}
-	}
-        if ( [$0] )
-           { ^assign SRV $0- }
-           { ^assign SRV $S }
-	stats l $SRV
-	wait -cmd eval ^on ^211 -"$SRV *"
-}
-
-# If you use Daveman's toolbox or any auto rejoin line, remove the old
-# on raw_irc for KICK, and use the foll. one instead: (Run)
-#
-#ON ^RAW_IRC "% KICK % % *" {
-#    IF ([$3]==[$N]) 
-#      {
-#        //QUOTE JOIN $2
-#        ECHO $MID(11 5 $STIME($TIME())) * You have been kicked off channel $2 by $LEFT($INDEX(! $0) $0) \($MID(1 256 $4-)\) 
-#       } 
-#     {
-#        ECHO $MID(11 5 $STIME($TIME())) * $3 has been kicked off channel $2 by $LEFT($INDEX(! $0) $0) \($MID(1 256 $4-)\) 
-#      }
-#                           }
-

doc/Authors

@@ -118,8 +118,13 @@ Tom Hopkins <hoppie@buengf.bu.edu> / September, October 1990:
   always works on code, so he has to have done alot more than three
   lines worth. :) 
 
-Carsten Munk <stskeeps@mp3fans.co.uk> / May and futher 1999:
-* Made many features based on Elite.. :/
+UnrealIRCd Coders
+Carsten Munk <stskeeps@unrealircd.com> / May 1999, date
+Dominick Meglio <codemastr@unrealircd.com> / June 1999, date
+David Flynn / March 2000, June 2000
+McSkaf / June 2001, September 2001
+Finny Merrill <griever@unrealircd.com> / November 2001, December 2002
+Bram Matthys <syzop@unrealircd.com> / January 2002, date
 
 Thanks go to those persons not mentioned here who have added their advice,
 opinions, and code to IRC.
@@ -139,4 +144,4 @@ Eric P. Scott <eps@toaster.sfsu.edu>
 Dan Goodwin <fornax@wpi.wpi.edu>
 Noah Friedman <friedman@ai.mit.edu>
 
-[ $Id$ ]
+[ $Id$ ]

doc/Crule.readme

@@ -1,128 +0,0 @@
-SmartRoute
-Rule based connects
-Draft 4 - Aug 19, 1994
-by Tony Vencill
-
-Rule based connects allow an admin to specify under what conditions
-a connect should not be allowed.  If no rules are specified for a
-given C and/or N line it will be allowed under any condition.
-
-A rule may consist of any legal combination of the following functions
-and operators.
-
-Functions
----------
-connected(targetmask)     - true if a server other than that processing
-                            the rule is connected that matches the
-                            target mask
-directcon(targetmask)     - true if a server other than that processing
-                            the rule is directly connected that matches
-                            the target mask
-via(viamask, targetmask)  - true if a server other than that processing
-                            the rule matches the target mask and is
-                            connected via a directly connected server
-                            that matches the via mask
-directop()                - true if an oper is directly connected
-
-Unary operators
----------------
-!    eg: !argument        - true if the argument is false
-
-Binary operartors
------------------
-&&   eg: arg1&&arg2       - true if arg1 and arg2 are both true
-||   eg: arg1||arg2       - true if arg1, arg2, or both are true
-
-Parenthesis () are allowed for grouping arguments, but if no parenthesis
-are included, && will take precedence over ||, ! will take precedence
-over both && and ||, and the function will be evaluated from left to
-right.  White space in a rule is ignored.  Invalid characters in a rule
-will lead to the rule being ignored.
-
-Examples
---------
-
-A simple example of a connect rule might be:
-
-connected(*eu.under*)
-
-This might be used in a US undernet server for a Europe CN pair to
-insure that a second Europe link is not allowed if one US-EU link
-already exists.  Note that on the undernet, US server names are
-city.state.us.undernet.org and Europe server names are
-city.country.eu.undernet.org.
-
-A more interesting example might be:
-
-connected(*eu.under*) && 
-  ( !direct(*eu.under*) || via(manhat*, *eu.under*) )
-
-Imagine the Boston undernet server uses this rule on its Europe CN
-pairs.  This says that if a Europe server is already connected, a
-Boston-Europe connect will not be allowed.  It also says that if a
-Europe server does already exist and Boston is not directly connected
-to one or more Europe servers or Manhattan is, the Boston-Europe
-connect will not be allowed.  This has the effect of allowing multiple
-US-EU links but attempting to limit these links to one server (ie:
-Boston will not initiate its first Europe link if another server is
-already linking Europe).  This rule will also prefer to let Manhattan
-handle the US-EU link by disallowing Boston-Europe links if a Europe
-server is already linked to Manhattan.
-
-A example of the remaining function, directop(), is:
-
-connected(*eu.under*) || directop()
-
-If this line is used on Boston for the Paderborn CN pair, it will allow
-connects to Paderborn only if another Europe server is not already
-connected and there is not an oper on Boston.  If this rule is
-overrideable (ie: is applied only to autoconnects as described below),
-then it will disallow Boston autoconnects to Paderborn while a Boston
-oper is online, but allow oper-initiated connects to Paderborn under any
-circumstance.  This directop() function could be used to invoke less
-prefered routes only when an oper is not present to handle routing, or
-conversly to allow use of less preferable routes only when an oper is
-present to monitor their performance.
-
-ircd.conf entries
------------------
-
-A rule is listed in the ircd.conf file using a D or d line (which can
-be thought of as a "disallow" line).  D lines will apply to all oper
-and server originated connects, while d lines will apply only to
-autoconnects (ie: they are overrideable by opers).  The formats are:
-
-D:targetmask::rule
-d:targetmask::rule
-
-Remember that newlines are not allowed in conf lines.  Two examples
-(from above) are:
-
-D:*eu.under*::connected(*eu.under*)
-d:*eu.under*::connected(*eu.under*) || directop()
-
-Connects originating from other servers will be checked against and
-matching D lines, while matching d lines will be ignored as it will not
-be clear whether or not the connection attempt is oper initiated.
-
-Checking and viewing rules
---------------------------
-
-The chkconf program that comes with the servers has been modified to
-also check your connect rules.  If running in debug mode, parsing errors
-will show up at debug level 8.  To view rules online, "/stats d" can be
-used to see all rules and "/stats D" can be used to view those rules
-which affect oper initiated connects and accepts.
-
-Processing and storage
-----------------------
-
-The rules are parsed when the conf file is read and transformed into a
-more efficiently computed form, then all applicable rules are
-evaluated each time a connect command is given or an autoconnect is
-due.  If more than one applicable rule is given, only one need
-evaluate to true for the connect to be allowed (ie: the rules are ored
-together).  Note that conditions that exist when the connect is
-initiated might differ from conditions when the link is established.
-
-[ $Id$ ]

doc/Elite.Changes

@@ -1,126 +0,0 @@
-[ $Id$ ]
----------------------------
-Version Elite2.0 ==========
-===========================
-- Since +x was rewritten, the ban bug is 100% fixed. :)
-- Rewrote +x hidden host function completely.
-- Fixed FUNNY bug with hiddenhost and /who (Reported by Prod|gy)
-- Added/Removed irc networks
-- Fixed bug in /watch (Reported/Fixed by Despise)
-- Added nick-change flood protection.
-- Added an awesome manual... ./manual to run
-- Removed /who notice for opers.
-- Added protection of /akill *@* :)
-- Removed java stuff completely. (Java clients are like normal IRC clients...right?)
-- Added new +a mode. This mode can only be set by +q channel owners. When you are +a in a
-	channel, you cannot be deopped or kicked. (Syntax: /mode #chan +a <nick>)
-- Added new +q channel mode. ChanServ must set the channel founder +q so they are also
-	known as channel owners via the ircd. Channel owners are protected and may set
-	other users +a which they will also be protected (but not chan owners).
-	(Syntax: /mode #chan +q <nick>)
-- Re-coded /MAP
-- Changed GLINE notices from sendto_ops to send to all opers with +e flag on.
-- Added (addnet) script, you can run this to add your net settings to the next release.
-- Changed <server> to <ircnetwork> in whois "Blah is an oper on <server>"
-- Added new +L channel mode. If a #chat has a limit (+l) of 10 users, and +L set to channel
-	#chat2, when a user trys to join #chat, they won't get "#chat is full", they will be
-	auto-joined to #chat2 - (Linked channels in other words).
-	(Syntax: /mode #chan +L <linked chan>)
-- Changes user@shadow-33.com to user@user-33.one.com (noone will know one.com is the realhost)
-- Changed +x for IP's from (x.x.x.***) to (x.x.x.network-#)
-- In oline flags * will introduce +e on oper up. (before: required +e in oline flag)
-- Removed +t usermode (UMODE_ALL) - wasn't used.
-- Made 'create your own network setting' feature more stable.
-- Added new channel mode (+x) to disable colored text in channel.
-- Added +C (Co Administrator)
-- Added +T (Technical Administrator)
-- Changed /map to numerics...
-- Made startup message when booting more stable.
-
-Version Elite1.3 (02/23/99)
-============================
-- Cleaned up version.c.SH
-- Added new net settings (netdomain & helpchan)
-- Added new net config creator in ./Config
-- Made ./Config more easier...
-- Created new usermode +j (Java user)
-- New hostname (java.shadownet.org) for java users.
-- Removed RUN_SERVICES code from entire ircd.
-
-Version Elite1.2.4 (02/14/99)
-============================
-- Fixed the nick crash bug! (damn m_kill small error)
-- New network(s) added.
-- Changed one thing in m_gline (nothing big)
-
-Version Elite1.2.3 (02/10/99)
-============================
-- Removed SOCKS checking. (possibly cause of crashing)
-- Added new networks
-
-Version Elite1.2.2 (02/02/99)
-============================
-- Fixed the crashing bug. (Changing nicks with linked servers)
-- Modified AceStar net settings.
-- Q-line notices are back (except for ULined clients).
-- Fixed /kill bug with services.
-
-Version Elite1.2.1 (01/29/99)
-============================
-- Fixed multiple notices from +N / -N
-- Added some text to s_err.c
-- Possibly fixed the odd crashing... ?
-
-Version Elite1.2 (01/24/99)
-============================
-- Netadmin can be used via +N in the oline slot now.
-- When +N is executed, net-wide oper msg's are sent about it.
-- Completely removed the freeze function (it's a toy unlike a command)
-- Changed abit of the GLINE adding notice.
-- Added logging to a file for glines (gline.log)
-- Implemented SOCKS checking (thx Rhom).
-- Changed channel lists only when 2 ppl in chan to 1.
-- Changed sendto_ops function in many places in s_user.c/s_serv.c to
-  sendto_locfailops.
-- Changed GNOTICE in s_user.c/s_serv.c to GLOBOPS
-- Fixed hiddenhost bug with /kill (+w could see real host of oper)
-- Fixed hiddenhost bug with /oper (+s could see real host of oper)
-
-[Special thanks goes out to Rhom for reporting/help patch bugs]
-
-Version Elite1.1.1 (12/12/98)
-=============================
-- Fixed /whois bug (had problems with mIRC clients *sigh*)
-- Fixed /topic bug (didn't allow topic changes at all.)
-
-Version Elite1.1 (12/6/98)
-============================
-- Fixed ./Config script (Net select)
-- Fixed /remgline bug.
-- If ULined clients, channels are not shown which they are in.
-- Fixed +e / +t / +b (non-opers could get +et before)
-- Fixed OperMode notice.
-- Fixed Gline sending extra Global on expire.
-- Fixed /whowas wrong hostname bug (by Thiago)
-- Fixed chkconf ZLINE error (by matt)
-- Added PhazeNet configuration
-- Added option for auto +x in ./Config
-- Freeze was disabled in this version (It will be back in 1.2)
-
-Version Elite1.0 (09/20/98)
-============================
-- Changed Shadow3.9 to Elite1.0 (Starting a new IRCD)
-- Changed some numeric's around in src/s_err.c
-- Auto +x on Oper up.
-- Fixed small error in ./ircd script.
-- Made ./Config more Linux-redhat friendly.
-- Added RelicNet to the ircd.
-- include/config.h is much more compatible with all IRC nets.
-- Added /gline (works 100%) [/gline <user@host> <seconds> <reason>].
-- Fixed up /map.
-- Added UMODE's +e & +t 
-  * e: EYES [Can see ppl who /whois, and other notices.]
-  * t: ALL [See's all net notices ie: See's all Client connectings...]
-- Fixed the hiddenhost bug with IP's...
-- Fixed major bug with hiddenhost which caused coredump.
-- Made a new script (makeconf) -- generates the ircd.conf file.

doc/History/19.mu1-New

@@ -1,16 +0,0 @@
-The foll. patches are NEW in  19.mu1 (besides the old patches of stats-w,
-ban, topic, client connect, signon time, trace times in previous .mu
-versions):
-
-* All the modifications contained in U3.2, namely - TSpre8, silence, bquiet
-
-* The K line comments patch.
-
-* The operfail notification patch
-
-* The mixed case userid reject patch
-
-For info on these check the file  README.patches
-
-							- Mmmm
-[ $Id$ ]

doc/History/2.8-New

@@ -1,34 +0,0 @@
-
-For starters, not a lot is new.  What is ?
-
-	* STATS o and STATS h added;
-
-	* most STATS options are no longer oper-only;
-
-	* privacy fixes to all of WHO, WHOIS, TRACE and STATS;
-
-	* more options in the ircd.conf file;
-
-	* non-debilitating DNS/ident use (DNS routines written specifically
-	  for ircd which indludes small local cache);
-
-	* less bugs;
-
-	* easier to compile;
-
-	* heaps and heaps of new numerics;
-
-	* more problems for old clients that do stupid things;
-
-	* more numeric replies which replace old NOTICE's;
-
-	* compulsory ident checks and optional result usage;
-
-	* sendQ can now be class dependant;
-
-	* server handles client flooding better;
-
-	* for more information on changes, bug fixes during development, see
-	  ircd/ChangeLog and common/ChangeLog
-
-[ $Id$ ]

doc/History/Advertisement

@@ -1,41 +0,0 @@
-                 The Internet Relay Chat Program  -  IRC
-
-                      Author: Jeff Trim, April '89
-              Revised: Greg Lindahl, Oct '90 (gl8f@virginia.edu)
-	     Re-Revised: Helen Rose, March '94 (hrose@kei.com)
-
-Have you ever wanted to talk with other computer users in other parts of
-the world?  Well guess what?  You can!  The program is called IRC and it
-is networked much over North America, Europe, and Asia, Oceania, and parts
-of Africa.  This program is a substitution for talk(1), ytalk(1) and many
-other multiple talk programs you might have read about.  When you are
-talking in IRC, everything you type will instantly be transmitted around
-the world to other users that might be watching their terminals at the
-time - they can then type something and RESPOND to your messages - and
-vise versa.  I should warn you that the program can be very addictive once
-you begin to make friends and contacts on IRC ;-) especially when you
-learn how to cuss in 14 languages.
-
-Topics of discussion on IRC are varied, just like the topics of Usenet
-newsgroups are varied. Technical and political discussions are
-popular, especially when world events are in progress. IRC is also a
-way to expand your horizons, as people from many countries and
-cultures are on, 24 hours a day. Most conversations are in English,
-but there are always channels in German, Japanese, and Finnish, and
-occasionally other languages.
-
-                       How To Get IRC (technical)
-
-IRC is a fully-distributed client-server system, much like
-NNTP-Usenet, with several clients availble in C and elisp. You may ftp
-documentation and clients from any of the following sites:
-
-many kinds of clients (C, elisp, X11, VMS, REXX for VM, MSDOS, Macintosh):
-cs.bu.edu:/irc/clients
-ftp.acsu.buffalo.edu:/pub/irc
-ftp.funet.fi:/pub/unix/irc
-coombs.anu.edu.au:/pub/irc
-
-If you have any questions about IRC installation, write to hrose@kei.com.
-
-[ $Id$ ]

doc/History/Etiquette

@@ -1,86 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, doc/etiquette
- *   Copyright (C) 1990, Lea Viljanen and Ari Husa
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- *
- * $Id$
- */
-
-HOW TO BEHAVE ON IRC
-
-Authors:      Lea Viljanen (LadyBug)  viljanen@kreeta.helsinki.fi
-              Ari Husa     (luru)     so-luru@tolsun.oulu.fi 
-
-
-1) Language
-
-   The most widely understood and spoken language on IRC is English. 
-However! As IRC is used in many different countries, English is by
-no means the only language. If you want to speak some other language
-than English (for example with your friends), go to a separate channel
-and set the topic (with /topic) to indicate that. For example
-   /topic Finnish only!
-would mean that this channel would be reserved for Finnish discussion.
-On the other hand, you should check the topic (with /list command) 
-before you move to a channel to see if there are any restrictions about 
-language.
-   On a channel not restricted by /topic, please speak a language
-everybody can understand. If you want to do otherwise, change channels
-and set the topic accordingly.
-
-
-2) Hello/Goodbye
-
-   It's not necessary to greet everybody on a channel personally.
-Usually one "Hello" or equivalent is enough. And don't expect everybody
-to greet you back. On a channel with 20 people that would mean one
-screenful of hellos. It's sensible not to greet, in order not to be rude
-to the rest of the channel. If you must say hello, do it with a private /msg.
-The same applies to goodbyes.
-
-
-3) Discussion
-
-   When you come to a new channel it's advised you to listen
-for a while to get an impression of what's discussed. Please feel free
-to join in, but do not try to force your topic into the discussion
-if that doesn't come naturally.
-
-
-4) {}|[]\
-
-   IRC has quite a lot of people from Scandinavian countries,
-the above characters are letters in their alphabet. This 
-has been explained on IRC about a thousand and one times, so
-read the following, do not ask it on IRC:
-
-   {     is an A with 2 dots over it
-   }     is an A with a small circle above it
-   |     is either an O with 2 dots over it or an O with a dash (/) through it
-   [, ], and \ are the preceding three letters in upper case.
-
-   There are a lot of people from Japan as well, who use Kanji characters
-which may look quite exotic as well. As I don't know Kanji I don't
-even try to explain any of the characters.
-
-5) ATTENTION!
-
-   Remember, people on IRC form their opinions about you only by 
-your actions, writings and comments on IRC. So think before you type.
-Do not "dump" to a channel or user (send large amounts of unwanted
-information). This is likely to get you /kicked off the channel or
-/killed off from irc. Dumping causes network 'burbs', connections going
-down because servers cannot handle the large amount of traffic any more.

doc/INSTALL

@@ -1,963 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, doc/INSTALL
- *   Copyright (C) 1990,1991,1992, Jeff Trim, Mike Bolotski,
- *   Jarkko Oikarinen and Darren Reed.
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- *
- *   $Id$
- */
-
-            Installing IRC - The Internet Relay Chat Program
-
-
-Overview of this document:
-
-  1) The config.h file
-  2) Editing the Makefile
-  3) Compiling IRC
-  4) The ircd.conf file
-
-
-1) Edit the "config.h" file and make changes to the various #DEFINE's:
- 
-   a) Copy the config.h.dist file to config.h before editing.
-  
-   b) Define what type of UNIX your machine uses.
-
-      Pick the machine type which best describes your machine and change
-      the #undef to #define (if needed).  Some flavours of Unix require no
-      #define and in such cases all others should be #undef'd.
-
-   c) DEBUGMODE
-
-	Define DEBUGMODE if you want to see the ircd debugging information
-      as the daemon is running. Normally this function will be undefined
-      as ircd produces a considerable amount of output.  DEBUGMODE must be
-      defined for either of -t or -x command line options to work.
-      
-   d) DPATH, SPATH, CPATH, MPATH, LPATH, PPATH
-
-        DPATH is provided so that the other pathnames (SPATH, CPATH, etc)
-      may be provided in just filename form.  When the server starts, it
-      chdir's to DPATH before chroot or any other file operation, making
-      it the "current directory" for the server.  This is where core files
-      will go if it core dumps.
-
-	Define SPATH to be the directory path to ircd.  This is usually
-      /usr/local/bin/ircd, unless you don't have installation permission
-      there. 
-
-      Define CPATH to be the directory path to the "irc.conf" file.
-      This path is usually /usr/local/lib/irc.conf. The format of this file 
-      will be discussed later.
-
-      The LPATH #define should be set to "/dev/null" unless you plan to 
-      debug the program.  Note that the logfile grows very quickly.
-
-      Define MPATH to be the path to the 'motd' (message of the day) file
-      for the server.  Keep in mind this is displayed whenever anyone
-      signs on to your server.
-
-      The PPATH is optional, but if defined, should point to a file which
-      either doesn't exist (but is creatable) or a previously used PPATH
-      file.  It is used for storing the server's PID so a ps(1) isn't
-      necessary.
-
-   e) CHROOTDIR
-
-	To use the CHROOTDIR feature, make sure it is #define'd and that
-      the server is being run as root.  The server will chroot to the
-      directory name provded by DPATH.
-
-   f) ENABLE_SUMMON, ENABLE_USERS
-
-	For security conscious server admins, they may wish to leave
-      ENABLE_USERS undefined, disabling the USERS command which can be used
-      to glean information the same as finger can.  ENABLE_SUMMON toggles
-      whether the server will attempt to summon local users to irc by
-      writing a message similar to that from talk(1) to a user's tty.
-
-   g) SHOW_INVISIBLE_LUSERS, NO_DEFAULT_INVISIBLE
-
-	On large IRC networks, the number of invisible users is likely to
-      be large and reporting that number cause no pain.  To aid and effect
-      this, SHOW_INVISIBLE_LUSERS is provided to cause the LUSERS command
-      to report the number of invisible users to all people and not just
-      operators.  The NO_DEFAULT_INVISIBLE define is used to toggle whether
-      clients are automatically made invisible when they register.
-
-   h) OPER_KILL, OPER_REHASH, OPER_RESTART, LOCAL_KILL_ONLY
-
-	The three operator only commands, KILL, REHASH and RESTART, may all
-      be disabled to ensure that an operator who does not have the correct
-      privilidges does not have the power to cause untoward things to occur.
-      To further curb the actions of guest operators, LOCAL_KILL_ONLY can
-      be defined to only allow locally connected clients to be KILLed.
-
-   i) The rest of the user changable #define's should be pretty much self
-      explanatory in the config.h file.  It is *NOT* recommended that any
-      of the file undef the line with "STOP STOP" in it be changed.
-
-3) Configure and compile the code.
-
-      Edit the root Makefile for the server, uncomment/comment the correct
-   CFLAGS/IRCDLIBS lines as appropriate for your system.
-      Change DESTDIR to be the same as the path for DPATH in config.h.
-   Type "make". This will compile the server, the client, and the services.
-   At the end of this step, the server directory will contain 'ircd',
-   and the client directory will contain 'irc'.  To get the server installed,
-   type "make install" which will build a default m4 file for preprocessing,
-   copy example.conf and put the server all in DESTDIR.  The irc client and
-   a copy of the server will also be placed in BINDIR and the modes set
-   accordingly.
-
-4) The ircd.conf file.
-
-   After installing the ircd and irc programs, edit the irc.conf file
-   as per the instructions in this section and  install it in the 
-   location you specified in the config.h file.  There is a sample
-   conf file called example.conf in the /doc directory.
-
-   Appendix A describes the differences between IP addresses and host
-   names.  If you are unfamiliar with this, you should probably scan 
-   through it before proceeding.
-
-   The irc.conf file contains various records that specify configuration
-   options.  The record types are as follows:
-   
-   1.  Server connections   	(C,N)
-   2.  Machine information	(M)
-   3.  Client connections	(I)
-   4.  Default local server	(U)
-   5.  Operator priviliges	(O)
-   6.  Administrative info	(A)
-   7.  Excluded accounts	(K)
-   8.  Excluded machines        (Q)
-   9.  Connection Classes       (Y)
-  10.  Leaf connections         (L)
-  11.  Service connections      (S)
-  12.  Port connections		(P)
-  13.  Hub connections		(H)
-
-
-   1. SERVER CONNECTIONS:  How to connect to other servers
-			   How other servers can connect to you
-
-   WARNING:
-     The hostnames used as examples are really only examples and
-     not meant to be used (simply because they don't work) in real life.
-
-   Now you must decide WHICH hosts you want to connect to and WHAT ORDER you
-   want to connect to them in.  For my example let us assume I am on the
-   machine "rieska.oulu.fi" and I want to connect to irc daemons on 3 other
-   machines:
-
-         "garfield.mit.edu"        - Tertiary Connection
-         "irc.nada.kth.se"         - Secondary Connection
-         "nic.funet.fi"            - Primary Connection
-
-   And I prefer to connect to them in that order, meaning I first want to
-   try connecting to "nic.funet.fi", then to "irc.nada.kth.edu", and
-   finally to "garfield.mit.edu".  So if "nic.funet.fi" is down or
-   unreachable, the program will try to connect to "irc.nada.kth.se".
-   If irc.nada.kth.se is down it will try to connect to garfield and so forth.
-   PLEASE limit the number of hosts you will attempt to connect to down to 3.
-   This is because of two main reasons:
-     a) to save your server from causing extra load and delays
-        to users
-     b) to save internet from extra network traffic
-        (remember the old rwho program with traffic problems when
-        the number of machines increased).
-
-   The format for the CONNECT entry in the "irc.conf" is:
-
-       C:<TARGET Host Addr>:<Password>:<TARGET Host NAME>:<TARGET Host PORT>
-Field: 1        2              3                4               5
-
-   for example:
-   
-    C:nic.funet.fi:passwd:nic.funet.fi:6667 
-
-          - or -
-
-    C:128.214.6.100:passwd:nic.funet.fi:6667
-
-          - or -
-
-    C:root@nic.funet.fi:passwd:nic.funet.fi:6667
-
-
-    Explanation:
-
-    Each field is separated with a ":" charcter:
-
-    Field 1: Field 1 tells the IRC program which option is being configured.
-             "C" corresponds to a server Connect option.
-
-    Field 2: Specifies the host name or IP address of the machine to connect
-	     to.  If "user@" prefixes the actual hostname or IP address
-	     the server will require that the remote username returned by
-	     the ident server be the same as the one given before the "@".
-
-    Field 3: The password of the other host.  A password must always be
-	     present for the line to be recognized.
-
-    Field 4: The full hostname of the target machine. This is the name that 
-	     the TARGET server will identify itself with when you connect 
-	     to it.  If you were connecting to nic.funet.fi you would receive
-	     "nic.funet.fi" and that is what you should place in 
-	     this field.
-  
-    Field 5: The INTERNET Port that you want to connect to on the TARGET 
-	     machine. Most of the time this will be set to "6667".  
-             If this field is left blank, then no connections will 
-             be attempted to the TARGET host, and your host will accept
-             connections FROM the TARGET host instead.
-
-   Some examples:
-
-            C:nic.funet.fi::nic.funet.fi:6667
- 
-            This reads: Connect to host "nic.funet.fi", with no password
-            and expect this server to identify itself to you as
-            "nic.funet.fi". Your machine will connect to this host to
-            PORT 6667.
-
-            C:18.72.0.252:Jeff:garfield.mit.edu:6667
-
-            This reads: Connect to a host at address "18.72.0.252", using a
-            password of "Jeff".  The TARGET server should identify
-            itself as "garfield.mit.edu".  You will connect to Internet
-            Port 6667 on this host.
-
-            C:irc.nada.kth.se::irc.nada.kth.se
-
-            This reads: do not attempt to connect to "irc.nada.kth.se",
-			but if "irc.nada.kth.se" requests a connection,
-			allow it to connect.
-
-   Now back to our original problem, we wanted OUR server CONNECT to 3
-   hosts,  "nic.funet.fi", "irc.nada.kth.se" and "garfield.mit.edu" in
-   that order.  So as we enter these entries into the file they must be
-   done in REVERSE order of how we could want to connect to them.
-
-   Here's how it would look if we connected "nic.funet.fi" first:
-
-	C:garfield.mit.edu::garfield.mit.edu:6667
-	C:irc.nada.kth.se::irc.nada.kth.se:6667
-	C:nic.funet.fi::nic.funet.fi:6667
-
-   Ircd will attempt to connect to nic.funet.fi first, then to irc.nada
-   and finally to garfield.
-
-   Reciprocal entries:
-
-   Each "C" entry requires a corresponding 'N' entry that specifies
-   connection priviliges to other hosts.  The 'N' entry contains
-   the password, if any, that you require other hosts to have before
-   they can connect to you.  These entries are of the same format as
-   the "C" entries.
-    
-   Let us assume that "garfield.mit.edu" connects to your server
-   and you want to place password authorization authorization on garfield.
-   The "N" entry would be:
-   
-          N:garfield.mit.edu:golden:garfield.mit.edu
-  
-   This line says: expect a connection from host "garfield.mit.edu",
-   and expect a login password of "golden" 
-   and expect the host to identify itself as "garfield.mit.edu".
-     
-	  N:18.72.0.252::garfield.mit.edu
-
-   This line says: expect a Connection from host "18.72.0.252", and 
-   don't expect login password.  The connecting host should identify itself
-   as "garfield.mit.edu". 
-
-  
-   Wildcards domains: 
-	To reduce the great amount of servers in IRCnet wildcard
-	DOMAINS were introduced in 2.6. To explain the usage of
-	wildcard domains we take an example of such:
-		*.de  - a domain name matching all machines
-                        in Germany.
-        Wildcard domains are useful in that ALL SERVERS in Germany
-        (or any other domain area) can be shown as one to the
-	rest of the world. Imagine 100 servers in Germany, it
-	would be incredible waste of netwotk bandwidth to broadcast
-	all of them to all servers around the world.
-
-	So wildcard domains are a great help, but how to use them ?
-	They can be defined in the N-line for a given connection,
-	in place of port number you write a magic number called
-	wildcard count.
-
-	Wildcard count tells you HOW MANY PARTS of your server's name
-	should be replaced by a wildcard. For example, your server's
-	name is "tolsun.oulu.fi" and you want to represent it as
-	"*.oulu.fi" to "nic.funet.fi". In this case the wildcard count
-	is 1, because only one word (tolsun) is replaced by a wildcard.
-	If the wildcard count would be 2, then the wildcard domain would
-	be "*.fi". Note that with wildcard name "*.fi" you could NOT
-	connect to "nic.funet.fi", because that would result in a server
-	name COLLISION (*.fi matches nic.funet.fi).
-
-	I advice you to not to use wildcard servers before you know
-	for sure how they are used, they are mostly beneficial for
-	backbones of countries and other large areas with common domain.
-
-
-   2. MACHINE INFORMATION
-                            
-   IRC needs to know a few things about your UNIX site, and the "M" command
-   specifies this information for IRC.  The fomat of this command is:
-
-           M:<YOUR Host NAME>:xxx:<Geographic Location>:<Internet Port>
-   Field:  1         2         3           4                 5
-
-   Explanation:
-
-      Field 1: "M" specifies a Machine description line
-
-      Field 2: The name of YOUR host adding any Internet DOMAINNAME that 
-               might also be present.  
-
-      Field 3: -- NOT USED --: Set to Value NULL (No spaces at ALL!).
-    
-      Field 4: Geographic Location is used to say WHERE YOUR SEVRER is,
-               and gives people in other parts of the world a good
-               idea of where you are!  If your server is in the USA, it is
-               usually best to say: <CITY> <STATE>, USA.  Like for Denver
-               I say: "Denver Colorado, USA".  Finnish sites (like
-               tolsun.oulu.fi generally say something like "Oulu, Finland".
- 
-      Field 5: The Internet port your server will use.  Should be set to
-	       the same value as in the config.h file.
-
-
-      Example:
-                M:tolsun.oulu.fi::Oulu, Finland:6667
-
-                This line reads: My Host's name is "tolsun.oulu.fi" and
-                my site is located in "Oulu, Finland".  My ircd will use
-		Internet Port 6667.
-
-
-                M:orion.cair.du.edu::Denver Colorado, USA:6667
-
-                This line reads: My Hosts name is "orion.cair.du.edu"
-                and my site is located in "Denver Colorado, USA".
-	        I have defined Internet Port number "6667" to be used
-                as my IRCD Socket Port.
-
-
-   3. CLIENT CONNECTIONS -   How to let clients connect to your IRCD.
-
-   A client is a program that connects to the ircd daemon (ircd).  Currently
-   there are clients written in C and in GNU Emacs Lisp.  The "irc"
-   program is the C client.  Each person that talks via IRC is running
-   their own client.
-
-   The irc.conf files contains entries that specify which clients are allowed
-   to connect to your irc daemon.  Obviously you want to allow your cwn
-   machine's clients to connect.  You may want to allow clients from 
-   other sites to connect.  These remote clients will use your server
-   as a connection point.  All messages sent by these clients will pass
-   through your machine.
-
-   The format of this entry in the conf file is:
-
-          I:<TARGET Host Addr>:<Password>:<TARGET Hosts NAME>:<Internet Port>
-    Field:1         2               3             4                5
-
-
-      For example, if you were installing IRC on tolsun.oulu.fi and you wanted
-      to allow examples sake let us assume you were making this file for
-      tolsun and you wanted to let your own clients to connect to your
-      server, you would add this entry to the file:
-
-      I:128.214.5.6::tolsun.oulu.fi
-      or
-      I:tolsun.oulu.fi::tolsun.oulu.fi
-
-      If you wanted to let remote clients connect, you could add the
-      following lines:
-
-      I:*.du.edu::*.du.edu
-
-      Allow any clients from machines whose names end in "du.edu" to connect
-      with no password.
-
-      I:128.214.6.100::nic.funet.fi
-
-      Allow clients from a machine with that IP number and the name 
-      nic.funet.fi to connect.
-
-      I:*.tut.fi:secret:*.tut.fi
-
-      Allow clients from machines matching *.tut.fi to connect
-      with the password 'secret'.
-
-      I:*::*
-
-      Allow anyone from anywhere to connect your server.
-      This is the easiest way, but it also allows people to for example
-      dump files to your server, or connect 1000 (or how many open
-      sockets per process your OS allows) clients to your machine
-      and take your network ports. Of course the same things can be
-      done by simply telnetting to your machine's SMTP port (for example).
-
-   NEW!!!
-      As of the 2.7.2d version of the server, the server is able to accept
-      connections on multiple ports. I-lines are required for each P-line
-      to allow connections to be accepted. For unix sockets, this means
-      either adding I:/path/port::/path/port or some variation (wildcards
-      are recognised here). For internet ports, there must be an I-line
-      which allows the host access as normal, but the port field of the
-      I-line must match that of the port of the socket accepting the
-      connectiion. A port number of 0 is a wildcard (matches all ports).
-
-   4. DEFAULT HOSTS (for local clients)
-
-      This defines the default connection for the irc client.  If you are
-      running an ircd server on the same machine, you will want to define
-      this command to connect to your own host.  If your site is not running
-      a server then this command should contain the TARGET host's connection
-      information and password (if any).  The format for this command is:
-
-         U:<TARGET Host addr>:<Password>:<TARGET Host NAME>:<Internet Port>
-  Field: 1         2              3                4            5
-   
-
-      For example:
-
-           U:tolsun.oulu.fi::tolsun.oulu.fi:6667
-           U:128.214.5.6::tolsun.oulu.fi:6667
-           U:tolsun.oulu.fi::tolsun.oulu.fi
-
-      If the port number is omitted, irc will default to using 6667.
-
-  5. OPERATOR Privileges:  How to become the IRC administrator on your site
-
-   To become an IRC Administrator, IRC must know who is authorized to become
-   an operator and what their "Nickname" and "Password" is.  To add this
-   information, EDIT your "irc.conf" file and add the following command
-   line to it:
-
-          O:<TARGET Host NAME>:<password>:<nickname>:<port>:<class>
-  Field:  1          2             3          4        5       6
-
-  Explanation:
- 
-     Field 1: Speficies Operator record. If you use capital letter ('O')
-              in it, it specifies a global operator. Small letter ('o')
-              specifies a local operator. Local operator has basically the
-              same rights except global operator with some restrictions.
- 
-     Field 2: Tells IRC which host you have the privileges FROM.  This
-              means that you should be logged into this host when you
-              ask for the priviliges.  If you specify "tolsun.oulu.fi"
-              then IRC will expect your CLIENT to be connected at 
-              "tolsun.oulu.fi" - when you ask for OPERATOR privileges
-              from "tolsun.oulu.fi".  You cannot be logged in at any
-              other host and be able to use your OPERATOR privileges
-              at tolsun, only when you are connected at TOLSUN will this
-              work - this is a safeguard against unauthorized sites.
-
-
-     Field 3: If your AUTHORIZATION Password - this is the password that 
-              let's IRC know you are who you say you are!  Never tell anyone
-              your password and always keep the "irc.conf" file protected
-              from all of the other users.
- 
-     Field 4: The Nickname you usually go by - but you can make this what
-              you want.  It is better to make this a NICKNAME that no one
-              else knows, but anything will do.  I usually use my own
-              loginname.
-
-     Field 5: Unused.
-
-     Field 6: The class field should refer to an existing class (preferably
-	      having a lower number than that for the relevant I-line) and
-	      determines the maximum number of simultaneous uses of the
-	      O-line allowable through the max. links field in the Y-line.
-
-  Example:
-              O:orion.cair.du.edu:pyunxc:Jeff
-
-              There is an OPERATOR at "orion.cair.du.edu" that can get
-              Operator priviliges if he specifies a password of "pyunxc"
-              and uses a NICKNAME of "Jeff".
-
-
-
-  6. ADMINISTRATIVE INFORMATION
-
-  The "A" command is used for administrative information about a site.
-  The e-mail address of the person running the server should be included
-  here in case problems arise.
-
-  
-            A:<Your Name/Location>:<Your Electronic Mailing Addr>:<other> 
-  Field:    1        2                    3                         4
-
-  Explanation:
-
-       Field 1: "A" specifies an Admin record.
-
-
-       Field 2: Use this field to say tell your FULL NAME and where in the 
-                world your machine is.  Be sure to add your City, 
-		State/Province and Country.
-
-
-       Field 3: Use this field to specify your Electronic Mailing Address
-                preferably your Internet Mailing Address.  If you have
-                a UUCP or ARAPnet address - please add that as well.  Be
-                sure to add any extra DOMAIN information that is needed,
-                for example "mail jtrim@orion" probably won't work as a 
-                mail address to me if you happen to be in Alaska.  But 
-                "mail jtrim@orion.cair.du.edu" would work because you 
-                know that "orion" is part of the DOMAIN "cair.du.edu". 
-                So be sure to add your DOMAINNAMES to your mailing addresses.
-
-       Field 4: Is really an OTHER field - you can add what you want here,
-                
-
-  Examples (the line is just one line in the confuration file, here it
-            is cut into two lines to make it clearer to read):
-
-A:Jeff Trim -  Denver Colorado, USA:INET jtrim@orion.cair.du.edu UUCP {hao,
-isis}!udenva!jtrim:Terve! Heippa!  Have you said hello in Finnish today?;)
-
-  Would look like this when printed out with the /admin command:
-
-      Jeff Trim -  Denver Colorado, USA
-      INET jtrim@orion.cair.du.edu   UUCP {hao,isis}!udenva!jtrim
-      Terve! Hei! Heippa!  Have you said hello in Finnish today? ;)
- 
- 
-  Note that the A record cannot be split across multiple lines; it will 
-  typically be longer than 80 characters and will therefore wrap around
-  the screen.
-
-
-  7. REMOVING A USER FROM IRC  Remove an errant user from IRC on your site.
-
-  Obviously it is hoped that you wouldn't have to use this command.
-  Unfortunately sometimes a user can become unmanageable and this is your
-  only recourse - the KILL USER command.  THIS COMMAND ONLY AFFECTS YOUR
-  SERVER - If this user can connect to another SERVER somewhere else in
-  the IRC-Network then you would have to talk to the administrator on that
-  site to disable his access from that IRCD Server as well.
-
-  The format of this command is:
-
-         K:<Host Name>:<time interval(s)>:<User>
-  Field: 1     2               3            4
-
-  Explanation:
-
-       Field 1:  "K" tells the IRCD that you are making a KILL USER command
-                 entry.
-
-       Field 2:  In this field you specify the Hostname that the user is 
-                 connecting from.  If you wanted to REMOVE connects
-                 to IRC from "orion.cair.du.edu" then you would want to enter
-                 "orion.cair.du.edu".  If you want to REMOVE ALL HOSTS
-                 access you can use '*' (Wild Card notation) and no matter
-                 what host the USERNAME (specified in Field 4) connects from
-                 s/he will be denied access. Removing all hosts isn't
-                 very smart thing to do though, why would you run an ircd
-                 if you allow nobody to connect to it anyways ?
-
-       Field 3:  Either leave this field empty (no spaces), then then lines
-		 is active continuously for the specified user/host machine.
-		 You may also specify intervals during the line should be
-		 active, see examples above.
-    
-       Field 4:  The USERNAME of the user you want removed from IRC.  For
-                 example 'root'.
-
-   
-   Some Examples:
-                   K:orion.cair.du.edu::jtrim
- 
-               If user 'jtrim' connects to IRC from host "orion.cair.du.edu"
-               then IMMEDIATELY REMOVE HIM from my IRCD.
-
-                   K:*.cair.du.edu::root
-
-               If user 'root' connects to IRC from any host that has the 
-               suffix "cair.du.edu" - then IMMEDIATELY REMOVE THEM from
-               my IRCD.
-
-                   K:*::vijay
-
-               This line reads "I don't care WHAT HOST user 'vijay' is on,
-               I will NEVER allow username 'vijay' to login to my IRCD.
-
-	           K:*.oulu.fi:0800-1200,1400-1900:*
-
-	       This disallows all users from hosts with enddomain 'oulu.fi'
-	       access to your server between 8 and 12am, 2 and 7pm.
-	       Users get kicked off if they're already signed on when the
-	       line becomes active (they'll get a warning 5 minutes ago).
-
-  8. Disallowing SERVERS in your irc net.
-
-   In some cases people run into difficulties in net administration.
-   For one reason or another you do not want a certain server to be
-   in your net (for example because of the security holes it opens
-   for every server if it's not secured carefully). In that case
-   you should use Q-lines in your server. When you specify a server
-   name in Q-line, everytime some server link tries to introduce you
-   a server (remember, all server names are broadcast around the net),
-   that name is checked if it matches the Q-lines in your server.
-   If it matches, then your server disconnects the link. Note that
-   just placing Q-lines to your server probably results in your server
-   being left alone, unless other servers have agreed to have the
-   same Q-line in their ircd configuration files as well.
-
-   Example:
-                Q::of the security holes:foo.bar.baz
-
-   This command excludes a server named "foo.bar.baz", the reason
-   is given to be security holes (you should give a reason, it is
-   polite). The first field is unused, so leave it empty.
-
- 9. Connection Classes.
-
-   To enable more efficient use of MAXIMUM_LINKS, connection classes
-   were implemented. To give a connection a class, add another field
-   (a sixth) to the C/N lines for a particular server.
-   Each line for a server should have the same number as the sixth
-   field.  If it is absent, the server deaults it to 0, using the
-   defaults from the config.h file.  To define a connection class,
-   you need to include a Y: line in the irc.conf file.  This enables
-   you to define the ping frequency, connection frequency and maximum
-   number of links that class should have.  Currently, the Y: line MUST
-   appear in the irc.conf file BEFORE it is used in any other way.
-
-   The format for the line is:
-
-       Y:<CLASS>:<PING FREQUENCY>:<CONNECT FREQUENCY>:<MAX LINKS>:<SENDQ>
-Field: 1    2                3                4                5     6
-
-   Field 2:  This is the class number which gains the following attributes
-   and should match that which is on the end of the C/N line.
-
-   Field 3:  This field defines how long the server will let the connection
-   remain "silent" before sending a PING message to make sure it is still
-   alive.  Unless you are sure of what you are doing, use the default value
-   which is in your config.h file.
-
-   Field 4:  By changing this number, you change how often your server
-   checks to see if it can connect to this server.  If you want to check
-   very occasionally, use a large value, but if it is an important
-   connection, you might want a smaller value so that you connect to it
-   as soon as possible.
-
-   Field 5:  This field defines the maximum number of links this class
-   will allow from automatic connections.  Using /CONNECT overrides this
-   feature.
-
-   Field 6:  This field defines the 'sendq' value for this class.  If this
-   field is not present, the default (from config.h) is assigned.
-
-   NOTE: leaving any of the fields out means their value is 0 (ZERO)!!
-
-   example:
-
-   Y:23:120:300:5
-
-   define class 23 to allow 5 auto-connections, which are checked every
-   300 seconds.  The connection is allowed to remain silent for 120
-   seconds before a PING is sent.  NOTE: fields 3 & 4 are in seconds.
-
-   You may also give I lines a class (again the sixth field to define
-   which class).  This is only usefull (currently) for redefining the
-   ping frequency.  It can also be useful as a diagnostic to see how
-   much each I line is used when combined with the TRACE output.
-
-   Another feature of connection class is the ability to do automatic
-   routing by using the class as a 'priority'.  If you are connected
-   to a server which has a class lower than one of the servers that is
-   'behind' it, the server will disconnect the lower class one and
-   schedule a 'new' connection for the higher class server.
-
- 10. Leaf Connections.
-
-   To stop servers which should only act as leaves from hubs becoming
-   hubs accidently, the L line was introduced so that hubs can be aware
-   of which servers should and shouldnt be treated as leaves. A leaf
-   server is supposed to remain a node for the entirity of its life
-   whilst connected to the IRC server network.  It is quite easy, however
-   for a leaf server to be incorrectly setup and create problems by
-   becoming a node of 2 or more servers, ending its life as a leaf. The
-   L line enables the administrator of an IRC 'Hub server' to 'stop' a
-   server which is meant to act as a leaf trying to make itself a hub.
-   If, for example, the leaf server connects to another server which doesnt
-   have an L-line for it, the one which does will drop the connection, once
-   again making the server a leaf.
-
-       L:<SERVER MASK>:*:<SERVER NAME>:<MAX DEPTH>
-Field: 1       2       3       4            5
-
-   Field 2 is a mask of which servers the leaf-like attributes are used on
-   when the server receives SERVER messages.  The wildcards * and ? may be
-   used within this field for matching purposes.  If this field is empty,
-   it acts the same as if it were a single * (ie matches everything).
-
-   Field 4 is the the server connectted to you that for which you want to
-   enforce leaf-like attributes upon.
-
-   Field 5 is the maximum depth allowed on that leaf and if not specified,
-   a value of 1 is assumed.  The depth is checked each time a SERVER message
-   is received by the server, the hops to the server being the field checked
-   against this max depth and if greater, the connection to the server that
-   made its leaf too deep has its connection dropped.
-   For the L-line to come into effect, both fields, 2 and 4, must match up
-   with the new server being introduced and the server which is responsible
-   for introducing this new server.
-
- 11. Service Connections (Not yet implemented)
-
-  Introduction.
-   The Service is a special kind of IRC client. It does not have the full
-   abilities of a normal user but can behave in a more active manner than
-   a normal client. Services as they stand now are not fully implemented.
-   The following line can be added to your ircd.conf file to enable a
-   service:
-  
-          S:<TARGET Host Mask>:<password>:<service_name>
-  Field:  1          2             3          4
-
-  Explanation:
-
-    Field 2:
-	The host mask should be set to match the hosts(s) from which the
-	service will be connecting from. This may be either an IP# or full
-	name (prefered).
-
-   Field 3:
-	This is the password which must be passed in the SERVICE command.
- 
-   Field 4:
-	The 'service name' is only used for the purpose of finding the
-	right S-line from the ircd.conf file for password matching. The
-	actual service name used is that set by NICK commands prior to
-	SERVICE being sent.
-
-   To connect a service to your server, you must first create an S-line
-   entry in your ircd.conf file and get your server to read this in (ie
-   rehash or reboot). Once your server has updated itself, you can then
-   attempt to register your connection as a service.
-   Registering as a service is similar to registering as a normal user
-   except that you must send NICK first and then SERVICE. The service
-   command should look something like this:
-
-	SERVICE secretpassword referencename :Service information
-
-   A successfull registering of a service at the server will result in
-   a RPL_YOURESERVICE (383) being sent back to you. Any other reply as
-   a result of sending service indicates an error has occured.
-
-   A service is not a very useful sort of client, it cannot join channels
-   or issue certain commands although most are available to it. Services,
-   however, are not affected by flood control. It is therefore wise to
-   oversee the use of S-lines with some care.
-
- 12. Port Connections
-
-  Introduction.
-   The port line adds flexibility to the server's ability to accept
-   connections. By use of this line in the ircd.conf file, it is easy
-   to setup both Unix Domain ports for the server to accept connections
-   on as well as extra internet ports.
-
-       P:<Internet IP# Mask>:<*>:<*>:<PORT>
-Field: 1        2             3   4     5
-
-or
-
-       P:<Directory>:<*>:<*>:<PORT>
-Field: 1        2             3   4     5
-
-  Explanation
-   Internet Ports
-    Field 1
-	The internet IP mask defines where connections may come from and
-	be accepted. The IP mask uses either *'s or 0's as wildcards. The
-	following two lines are the same:
-
-		P:128.2.*:::6664
-		P:128.2.0.0:::6664
-
-	The incoming isnt matched against the mask, rather the ip# string
-	is decoded and compared segment by segment. Thus
-		P:128.2*.1.2:::6664
-	will not match 128.20.1.2.
-
-     Field 5
-	The port number field tells the server which port number it should
-	listen on for incoming connections.
-
-    Unix Socket Ports.
-     Field 1
-	The path set in field 1 should be the directory name in which to
-	create the unix socket for later listening to. The server will
-	attempt to create the directory before creating the unix socket.
-
-     Field 5
-	The port field when used in combination with a pathname in a P-line
-	is the filename created in the directory set in Field 1.
-
-     Example:
-		P:/tmp/.ircd:::6667
-
-	Creates a unix socket in the /tmp/.ircd directory called "6667".
-	The unix socket (file) must be a numerical.
-
-13.  Hub Connections
-
-      In direct contrast to L-lines, the server also implements H-lines to
-   determine which servers may act as a hub and what they may 'hub for'.
-   If a server is only going to supply its own name (ie act as a solitary
-   leaf) then no H-line is required for, else a H-line must be added as
-   follows:
-
-       H:<SERVER MASK>:*:<SERVER NAME>
-Field: 1       2       3       4
-
-   Explanation:
-    Field 2
-      All servers that are allowed via this H-line must match the mask
-      given in this field.
-
-    Field 4
-      This field is used to match exactly against a server name, wildcards
-      being treated as literal characters.
-
-   Examples:
-
-		H:*.edu:*:*.bu.edu
-
-	Allows a server named "*.bu.edu" to introduce only servers that
- 	match the "*.edu" name mask.
-
-		H:*:*:eff.org
-
-	Allow "eff.org" to introduce (and act as a hub for) any server.
-
-   Note:  It is possible to have and use multiple H-lines (or L-lines) for
-	  the one server.  eg:
-
-		H:*.edu:*:*.bu.edu
-		H:*.au:*:*.bu.edu
-
-	   is allowed as is
-
-		L:*.edu:*:*.au
-		L:*.com:*:*.au
-
-
-Appendix A: Difference between IP addresses and hostnames
-
-
-   There are 2 different types of INTERNET addresses, NAME addresses and
-   NUMERIC addresses.  NAME addresses look like ENGLISH words (and indeed
-   they are ENGLISH words that refer to a given host).  A NAME address looks
-   like "tolsun.oulu.fi" - and that particular address refers to the machine 
-   named TOLSUN in Finland.  It is a UNIQUE address because no other machine
-   in the world has its NAME address the same as "tolsun.oulu.fi".  Anytime
-   you say "telnet tolsun.oulu.fi" - you would always connect to TOLSUN in
-   Finland.  NUMERIC addresses refer to those addresses that are made up of
-   NUMBERS for example "128.214.5.6" is the NUMERIC address for TOLSUN.  This
-   address is also UNIQUE in that no other machine in the world will be use 
-   those NUMERIC numbers.  The NUMERIC address is usually more reliable than
-   the NAME address because not all sites can recognize and translate the
-   NAME address into it's numeric counterpart.  NUMERIC always seems to work
-   best, but use a NAME address when you can because it is easier to tell
-   what host you are connected to.
-
-
-   Every Unix machine has a file called "/etc/hosts" on it.  This file 
-   contains NAME and NUMERIC addresses.  When you supply IRC with a NAME 
-   address it will at first try to find it in /etc/hosts, and then (if it's 
-   really smart), use the local Domain Name Server (DNS) to find the NUMERIC
-   address for the host you want to connect to.  Thus if you plan to use NAME
-   addresses keep in mind that on SOME sites the entry for the TARGET machine
-   must be found in /etc/hosts or the NAME address will fail.  A typical 
-   entry in /etc/hosts looks like this:
-
-   130.253.1.15    orion.cair.du.edu orion.du.edu orion    # BSD 4.3
-
-   This particular example is the Host ORION at the University of Denver. 
-   Notice that on the far left is the NUMERIC Address for orion.  The
-   next few ENGLISH words are the NAME addresses that can be used for orion,
-   "orion.cair.du.edu", "orion.du.edu", "orion".  ALL of these NAME addresses
-   will return the NUMERIC address "130.253.1.15" which IRC will use to
-   connect to the TARGET UNIX. (when I say TARGET UNIX I am refering to the
-   UNIX you want to connect to for IRC). Any futher questions about
-   /etc/hosts should be directed to "man hosts".
-
-
-Appendix B: Enabling Summon Messages
-
-   +-----------------------------------------------------------------------+
-   |            E N A B L I N G    / S U M M O N    M E S S A G E S        |
-   +-----------------------------------------------------------------------+
-
-   *NOTE* You must have ROOT or special access to the GROUP tty ('/dev')
-   to do this. If you want to allow users around the world to summon
-   users at your site to irc, then you should make sure that summon works.
-
-   The "IRCD" program needs access to the GROUP of '/dev'.   This
-   directory is where user TTY's are stored (as UNIX treats each Terminal
-   as a FILE!)   IRCD needs GROUP ACCESS to /dev so that users can be
-   SUMMONED to the program by others users that are *in* the program.
-   This allows people from other Universities around the world to SUMMON
-   your users to IRC so that they can chat with them.  Berkeley, SUN, HP-UX
-   and most of the newer versions of UNIX check to see if a USER is
-   accepting MESSAGES via the GROUP access rights on their TTY listing
-   in the /dev directory. For example an entry in '/dev' looks like this:
-
-  (Unix Path on BSD 4.3 UNIX is:  /dev/ttyp0)
-
-        crw------- 1 jtrim     20,     0 Apr 29 10:35 ttyp0
-
-   You will note that 'jtrim' OWNS this terminal and can READ/WRITE to this
-   terminal as well (which makes sense because I am ENTERING DATA and
-   RECEIVEING DATA back from the UNIX).  I logged into this particular
-   UNIX on "April 29th" at "10:35am" and my TTY is "ttyp0".  But further
-   of *note* is that I do not have my MESSAGES ON! (mesg n)  -- This is
-   how my terminal would look with MESSAGES ON (mesg y):
-
-        crw--w---- 1 jtrim     20,     0 Apr 29 10:35 ttyp0
-
-   With my MESSAGES ON (mesg y) I can receive TALK(1) requests, use the 
-   UNIX WRITE(1) command and other commands that allow users to talk
-   to one another.  In IRC this would also allow me to get IRC /SUMMON
-   messages.  To set up the "IRCD" program to work with /SUMMON type
-   the following:  (using ROOT or an account that has access to '/dev').
-
-       % chgrp tty ircd
-       % chmod 6111 ircd 
-
-   The above commands read: "Give IRCD access to GROUP tty (which is /dev)
-   and then when ANYONE runs the IRCD allow SETUID and SETGID priviliges
-   so that they can use the /SUMMON command.

doc/Manual

@@ -1,382 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, doc/MANUAL
- *   Copyright (C) 1990, Karl Kleinpaste
- *
- *   $Id$
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- */
-
-                                                Date: 04 Apr 1989
-                                              Author: Karl Kleinpaste
-                                                      karl@cis.ohio-state.edu
-                                                
-                                   Last modification: 15 May 1992
-                                                  by  Mauri Haikola 
-                                                      mjh@stekt.oulu.fi
-
-
-			 INTERNET RELAY CHAT
-		  a real-time conversational system
-
-
-* 1: Irc - replacement for talk(1)
-
-Irc is a functional replacement for and improvement to talk(1).  Talk
-is an old, primitive, atrocious, minimalist sort of keyboard/screen
-conversation tool, using a grotesque, machine-dependent protocol.
-Irc does everything talk does, but with a better protocol, allowing
-more than 2 users to talk at once, with access across the aggregate
-Internet, and providing a whole raft of other useful features.
-
-* 2: Entering Internet Relay Chat
-
-There are two ways to enter Internet Relay Chat. If you are using the
-emacs lisp client, you need to load the client into your Emacs session
-and then M-x irc. If you are using the C client (easier for beginners)
-then type (usually) irc. If you wish to be known by a nickname which
-is not one's login name, type `irc chosen-nickname' instead.
-
-* 3: How much can be seen from here
-
-The universe - seriously.
-
-This is most formally called Internet Relay Chat.  Server hosts are
-connected via a tree structure.  The various servers relay control and
-message data among themselves to advertise the existence of other
-servers, users, and the channels and other resources being occupied by
-those users.
-
-* 4: Structure
-
-There is quite a lot of structure to the operation of irc, as
-compared to crufty old talk(1).  Since so little could be done with
-talk(1), it needed little structure.  But to keep track of people
-spread literally around the world (the system was written by Jarkko
-Oikarinen of Finland, usually seen on the system as `Wiz'), the
-structure is useful so that one can speak to exactly those people with
-whom one wishes to speak.
-
-** 4.1: Nicknames
-
-All users of irc are known to the system by a `nickname.'  By
-default, one's nickname is one's login name.  Nickname clashes are not
-allowed; this is enforced by the servers.  If one's intended nickname
-clashes with someone else as one enters chat, one will not be able to
-complete entry to irc until one changes one's nickname to something
-else.
-
-** 4.2: Presence on a channel
-
-Fundamental to the operation of irc is the concept of a channel.  All
-users are `on a channel' while inside irc.  One enters the `null
-channel' first.  One cannot send any messages while not in any
-chatting channel unless one has set up a private conversation in some
-way.  The number of channels is essentially unlimited - whatever will
-fit in a string of some ungodly length, that must start with a # sign.
-
-** 4.3: Main modes of channels
-
-Public
-
-This is the default mode for a channel. When one is on a public
-channel, one can be seen by all other users (if one's own user mode
-permits this).  Anyone can notice users on a public channel and join
-such a channel's conversation.
-
-Private
-
-This means that, although anyone can see that one is using chat, no
-one can tell what channel one is using unless one is already on that
-channel with oneself.  Since the number of potential channels is in
-the billions, this is quite some security - all one gives away is the
-acknowledgement that one is using chat.
-
-Secret
-
-While one is on a secret channel, no one who is not on one's channel
-with oneself can even see that one is there.  One's name does not show
-up in a list of active users.  The only indication of one's presence
-is that, when entering chat, all new users are told that there are "N
-users on P servers."  If one checks on all users and finds less than N
-of them, one knows that others are hiding on secret channels.  But a
-secret channel user still cannot be found except by brute-force
-checking through all channels, a hopeless proposition in the face of
-the huge number of possible channel names. Security through obscurity
-finally means something.
-
-Changing the mode
-
-The mode of a channel (private, secret, invite-only, moderated,
-topic-limited, person-number-limited, no-messages-to-channel, ban
-someone from channel) is set by the channel operator, who is the
-first person to join a channel, or someone who has had channel
-operatorship bestowed on them by another channel operator. 
-
-
-*** 4.4: Conversations not using channels
-
-It is possible to conduct conversations with others without using the
-formalized channel structure.  Doing so requires that two people set
-themselves up for private conversation using special commands; see
-User Commands below.
-
-* 5: Screen/keyboard structure
-
-Chat is a full-screen utility.  It takes over the screen, with the
-bulk of activity happening in the top N-2 lines, a modeline (vaguely
-emacs-like) on the next to last line, and one's input being entered on
-the last line.  A very good version of client is the IRC-II client,
-avaliable on anonymous ftp from various sites around the world.
-
-** 5.1: Keyboard input
-
-When typing commands at irc, one has a minimalist line-editing
-facility in an emacs style.  That is, ^A moves the cursor to the
-beginning of the line, ^E goes to the end, ^D deletes the character
-under the cursor, ^K kills from the cursor to the end, and so on.  
-
-** 5.2: Screen activity
-
-Almost everything happens in the upper bulk of the screen.  This
-includes both messages from other users, as well as the output of the
-control commands.
-
-Normal messages from other users appear with the originating nickname
-in <angle brackets>.  Private messages arrive with the originating
-nickname in *asterisks*.  Messages which one sends to everyone appear
-with a preceding "> " whereas messages which one sends privately to
-one other user appear with "-> *nickname*."
-
-Other output (e.g., /who commands, invitations from other users to
-join channels, and so forth) appears interspersed with other activity
-on the screen.
-
-* 6: Command structure
-
-Ordinary text typed at irc is sent as one's messages to everyone else
-on the same channel, modulo personal choices for private messages and
-the like.  Commands to irc itself all begin with a command character,
-which is initially `/' but may be changed to any other character
-desired.
-
-Commands may in general be abbreviated to a unique prefix.
-
-** 6.1: Leaving irc
-
-The way to get out of irc is to enter the /signoff command.  "/si" is
-sufficient.  Also equivalent are "/exit," "/bye," and "/quit." A
-signoff command may include a comment which will be seen by everyone
-on the current channel of the person who left.
-
-** 6.2: Getting help
-
-Type "/help."  Follow the instructions.
-
-** 6.3: User commands
-
-The most important commands supported by irc are:
-
-      help   signoff       who     whois
-      list     topic      join   channel
-     links       msg    invite    ignore
-     users     stats      nick      away
-      info     clear     query     cmdch
-      date      mode
-
-*** 6.3.1: help
-
-Information on how to use the rest of the system is available via
-/help.  The modeline says so as well.
-
-*** 6.3.2: signoff {comment}
-
-/signoff exits chat. Optional comment may be included; see above.
-
-*** 6.3.3: who
-
-/who returns information on who is using chat.  /who without arguments
-prints info on all users that can be seen.  Users of public channels
-show up with their channel identified.  Users of private channels
-appear, but they are specified as being on a private, unspecified
-channel.  Users of secret channels and users whose user mode is +i
-(invisible) do not appear at all.
-
-Giving a channel name as an argument to /who returns only those users of the
-specified channel.  This still doesn't show users of secret channel or
-invisible users one is actually on the same channel with them. Users
-of private channels are shown, if an exact channel name is given.
-
-*** 6.3.4: whois
-
-This returns information about individual users.  Say "/whois
-nickname" to get information on the login name and host from which the
-nicknamed user comes.
-
-*** 6.3.5: topic
-
-Channels can be given off-the-cuff "topics."  Saying "/topic some
-string of text" will associate that topic with the current channel.
-
-*** 6.3.6: list
-
-/list will give lists of active channels, the number of users of each,
-and the topics therewith associated.  Again, secret channels do not
-appear and private channels only appear as Prv.
-
-*** 6.3.7: join & channel
-
-/join or /channel are the means to enter a channel.  Give the channel
-name as an argument.  If this is a secret or hidden channel, /who
-commands will show oneself and any other users of one's channel.
-
-One's arrival on a channel is announced to the rest of the users
-already on that channel.  Silent, anonymous "lurking" is not
-supported.
-
-*** 6.3.8: links
-
-/links lists the currently-active set of chat servers.  Beware: this
-list can be quite long, and will undoubtedly get longer as chat gains
-wider use.  As of 15 May, 1992, about 130 servers is typical.
-
-*** 6.3.9: msg
-
-A single message can be sent privately to a certain user with /msg.
-Type /msg nickname and the text to be sent.  It will be sent privately
-to the indicated nickname.
-
-*** 6.3.10: invite
-
-If there is a user online to whom one wishes to speak, one may invite
-that user to join oneself on a certain channel.  One types "/invite
-nickname" with an optional channel number.  The receiving user gets a
-one-line message indicating the sender and the invitation.  The
-receiving user is free to ignore the invitation, of course.
-
-*** 6.3.11: ignore
-
-If one wants to ignore messages sent by some other user or users, it
-may be done with /ignore command. One can ignore someone by their
-nickname, or by their user@host data. Wildcards may be used. 
-
-*** 6.3.12: users
-
-/users will return a list of the users logged into one's system.  With
-an optional hostname identifying a chat server host, the users logged
-into that system will be listed.
-
-*** 6.3.13: stats
-
-This command returns counts of various protocol operations of one's
-chat server.  It is neither particularly useful nor interesting to
-users other than operators.
-
-*** 6.3.14: nick
-
-One can change nicknames by issuing "/nick new-nickname."  All users
-on one's channel will be advised of the change.  NOTE: If one enters
-chat with a nickname clash (e.g., one's login name is the same as
-someone else's, and the other user got there first), the system will
-not let one enter until one issues a /nick command with a unique
-nickname.
-
-*** 6.3.15: away
-
-Sometimes, one wishes to remain connected to the chat system, but one
-must be elsewhere for a while.  One can issue an /away command with
-arbitrary text as argument, which will mark oneself as being away.  If
-someone sends an away'd user a private message (via /msg or in a
-private session set up via /query; see below), the sender will get a
-message back from the server indicating the away-ness and the message
-which was set.
-
-*** 6.3.16: info
-
-/info returns information regarding the author and copyright of the
-chat system.
-
-*** 6.3.17: clear
-
-At times, one wishes that one's screen weren't so cluttered.  /clear
-makes it so.
-
-*** 6.3.18: query
-
-This command is used to set up private communications `outside' the
-normal channel system.
-
-When one enters "/query nickname," the indicated nickname is set up as
-the sole recipient of anything which one types thereafter.  Thus, if
-user A executes "/query B" and user B executes "/query A," they have
-set up a private communication between themselves.  Significantly, it
-remains possible for them to stay on their respective channels, which
-need not be the same, and listen to whatever conversation is going on
-around them as well, though they cannot respond to that ambient
-conversation without leaving the private conversation they have set up.
-
-One leaves this private mode by issuing /query without arguments.
-
-*** 6.3.19: cmdch
-
-The `/' character may not be best for some people to use as their
-command character.  It can be changed with "/cmdch <character>."
-
-*** 6.3.20: mode
-
-This command can be used for altering the various modes of a channel
-(see the explanation of channel modes above). /mode command can only
-be issued by channel operators. 
-
-** 6.4: Operator commands
-
-The chat system administrators on each host have additional
-responsibilities and power over the configuration and operation of the
-servers.  The commands to do so are delineated below.
-
-*** 6.4.1: oper
-
-Users who have the potential for operator privileges initially invoke
-those privileges by "/oper nickname password," where nickname is the
-nickname under which operation is intended, and password is the
-password known to the chat system for that nickname.
-
-*** 6.4.2: kill
-
-Obnoxious users had best beware the operator who's fast on the /kill
-command.  "/kill nickname" blows any given nickname completely out of
-the chat system.
-
-Obnoxiousness is not to be tolerated.  But operators should not use
-/kill lightly.
-
-*** 6.4.3: quote
-
-Raw access to the underlying server protocol is possible through the
-user of the /quote command.  "/quote any text at all" is used to send
-direct, unmodified commands to the servers.  This has a wide variety
-of uses, such as deliberately killing a local or remote chat daemon,
-invoking operator privileges for otherwise-operator-priv-forbidden
-users, and related tasks.  It is, again, a very powerful operation,
-and not to be used lightly.
-
-* 7: Questions, problems, troubles?
-
-If you have problems, please contact Christopher Davis (ckd@eff.org) or
-Helen Rose (hrose@eff.org). Known as "ckd" and "Trillian" on irc,
-respectively. You can also ask for help on some of the operator
-channels on irc, for example #twilight_zone and #eu-opers. They will
-be able to assist you in whatever problems you are having with IRC.
-

doc/Operators

@@ -1,241 +0,0 @@
-Internet Relay Chat Operator Etiquette Guide (May, 1992)
-[ $Id$ ]
-
-Welcome! You've either been selected to be an IRC Operator or you have set
-up your server and thus have taken on the dual task of IRC Server
-Administrator and IRC Operator. Your future days will be filled with hours
-of fun chatting on IRC, and then wondering why everyone you talked to went
-away, because the links had apparently broken. 
-
-Linking:
-========
-
-You will be assigned links from the IRC Routing Coordinators. Please
-use these links and these links ONLY. The links have been designed to
-maximize efficiency and make delays in chatting minimal. You will
-usually be given two links, one to each regional backbone site.
-Connect to the primary site first and then to the secondary site. You
-should not need to connect to any other sites. You will be informed if
-this policy changes.
-
-Kills 
-=====
-
-/kill is a special operator command. You should use it with
-care, and only if absolutely needed. The format is as follows:
-/kill NICKNAME comment. Comment can be a phrase of almost any length
-(within reason) and should be used for specifying the reason of the kill.
-Example: /kill Trillian She's a Ghost
-IRC Ghosts are created after a net split has occured and the net has yet to
-relink. 
-
-/wallops PHRASE This is used to talk to those users who have their
-user mode set to +w. /wallops used to be a way for operators to talk
-about important matters in linking etc., but it has little use
-nowadays. 
-
-/TRACE command /TRACE is useful to know what servers are connected to
-what. Sometimes /trace can be confusing, especially if you are using
-it for the first time.  Here is an example of a trace from
-stekt1.oulu.fi to cdc835.cdc.polimi.it.
-
-/TRACE cdc835.cdc.polimi.it
-
-*** Link stekt1.oulu.fi<2.7.2> ==> cdc835.cdc.polimi.it
-*** Link rieska.oulu.fi<2.7.1>e ==> cdc835.cdc.polimi.it
-*** Link nic.funet.fi<2.7.1>e ==> cdc835.cdc.polimi.it
-*** Link ircserver.et.tudelft.nl<2.7.1>e ==> cdc835.cdc.polimi.it
-*** Link vesuv.unisg.ch<2.7.1>e ==> cdc835.cdc.polimi.it
-*** Link apollo.di.unipi.it<2.7.1>e ==> cdc835.cdc.polimi.it
-*** Oper Class[10] ==> Allanon[cdc835.cdc.polimi.it]  
-*** User Class[11] ==> Lupandy[plus2.usr.dsi.unimi.it]  
-*** Serv Class[3] ==> apollo.di.unipi.it[131.114.4.36] 132S 445C
-*** User Class[11] ==> Punk[pluto.sm.dsi.unimi.it]  
-*** User Class[11] ==> TheEdge[pluto.sm.dsi.unimi.it]  
-*** User Class[10] ==> Mork[cdc835.cdc.polimi.it]  
-*** User Class[11] ==> Lollo[c700-2.sm.dsi.unimi.it]  
-*** User Class[11] ==> Attila[hp2.sm.dsi.unimi.it]  
-*** Class 0  Entries linked 1
-*** Class 11 Entries linked 5
-*** Class 10 Entries linked 2
-*** Class 3  Entries linked 1
-
-From this output you can see that the route goes first to
-rieska.oulu.fi (running version 2.7.1e), then nic.funet.fi,
-ircserver.et.tudelft.nl, vesuv.unisg.ch, and apollo.di.unipi.it, after
-which cdc835 is the next server. Then we see the connections on
-cdc835: One operator (Allanon) and 6 users are on line. The class of
-each connection is given. There is only one server connected to cdc835
-at the moment, and that server is apollo.di.unipi.it (cdc835 is said
-to be a "leaf" server at the moment). The numbers 132S 445C in the end
-of line tell us, that there are 132 servers and 445 clients connected
-to the servers from apollo onwards.  Finally we see a grand total of
-connections in each connection class. 
-
-
-/SQUIT server {comment}
-   /squit isolates a specified server from the next closest server, when
-you look at it along the trace path starting from your server. 
-This is usually used in conjunction with CONNECT (explained later) to
-reroute traffic. This will be described in detail in the section
-"routing", preceding CONNECT.
-
-   Usage (and examples): 
-
-      /squit E
-
-     If the network looks like this initially (and you are on server A)
-
- 
-          A <---> B <---> C <---> D
-                          ^
-                          |
-                          v
-                  G <---> E <---> F <---> ... (rest of the net)
-                          
-
-    Then after issuing the previous /squit the network would look like this:
-
-          A <---> B <---> C <---> D
-                          
-                          
-                  G <---> E <---> F <---> ...
-
-
-    /squit E {comment}
-
-	It usually helps to give a reason why you are sending a
-	SQUIT for a server. This can be accomplished by sending
-	the command "/squit server This link is making the US route
-	through Finland". The SQUIT will then be sent out, and the 
-	server sending the squit will WALLOP sending the comment
-	so all operators can see it. 
-
-/CONNECT server {portnum server2}
-   /connect is used to establish a link between two servers. These
-connections must be authorized by each server's ircd.conf file, but
-any operator can issue a CONNECT between authorized servers. This
-command is most often used in conjunction with SQUIT to reroute
-traffic. 
-   If only one argument is given, this command causes the server you
-are on to attempt to connect to the server specified. For example,
-"/connect B" (in the previous example) would cause your server (A) to
-connect to B. 
-   Suppose you wanted to reconnect server F to server E? You cannot
-contact server F since it is no longer part of your network. However,
-you can tell server E to connect to it. A remote CONNECT can be issued
-to server E. 
-
-   Examples (assume you are on server A):
-
-   /connect B
-
-   If the network initially looks like this:
-
-         A      B <---> ... (rest of network)
-
-   Then afterwards (if the connection succeeds) the network will look
-   like this:
-
-        A <---> B <---> ... 
-
-
-   In the example where you wanted to reconnect server E to F, the
-   following syntax would be appropriate (note: we are assuming that
-   F's irc socket port is 6667, which is the default)
-
-   /connect F 6667 E
-
-   If the network initially looks like this:
-
-         A <---> B <---> C <---> D
-                         ^
-                         |
-                         v
-                 G <---> E      F <---> ... 
-
-   Then after your CONNECT request the network topology will look like this:
-
-         A <---> B <---> C <---> D
-                         ^
-                         |
-                         v
-                 G <---> E <---> F <---> ... 
-
-    Be careful when connecting servers that you know which command to
-    use! If you simply issued "/connect F" from your server, the
-    network would look like this:
-
-
-    ... <---> F <--->  A <---> B <---> C <---> D
-                                       ^
-                                       |
-                                       v
-                               G <---> E 
-
-    which for various reasons (discussed below) might be very
-    undesirable. 
-
-Routing
-=======
-
-   When and how should you do rerouting? This depends on where your
-server is topologically located and whether you route traffic. If you
-are a leaf node (i.e. only connect to one server at a time) then
-chances are you won't need to do any routing at all.  Your ircd.conf
-file should be written to connect to the best possible servers first
-before trying alternates. At the most, you may decide to squit an
-alternate server and connect to your primary if/when it goes back up.
-This only involves local squits, however.
-
-   If you are operating a backbone site, you may find yourself
-rerouting things quite often. If the servers badger.ugcs.caltech.edu
-(Pasadena, CA), irc.mit.edu (Boston, MA), minnie.cc.utexas.edu
-(Austin, TX) and ucsu.colorado.edu (Boulder, CO) were routing traffic
-in the following way:
-
-    ... <---> minnie <---> badger <---> bucsd <---> ucsu <---> ...
-
-It would make sense to either squit ucsu and reconnect it to minnie,
-or disconnect minnie from badger and connect to ucsu, because
-topologically (and geographically) ucsu and minnie are rather close.
-There are occasions when US traffic for some reasons winds up being
-routed through Australia. This is another case where traffic should
-definitely be rerouted. However, there are sometimes occasions when
-routing is going through "backdoor" methods. If you see something
-totally outrageous (like the east coast and the west coast being
-connected by eff.org) please ask for example on channel #twilight_zone
-before you send any squits, because chances are, it's like that for a
-reason.
-
-   Of course, any operator can remotely squit or connect servers, so
-if you see a problem and you're sure you know how to fix it, it's a
-good idea to do so. If the operator of a server which is is being
-routed poorly is online, it's probably best to contact him/her first,
-though.
-
-   Chances are that hub operators will be more familiar with the
-general topology of the network and which servers connect to which
-(which is why most of the manual routing is left to them), so if you
-have any problems, talk to the other operators on operator channels
-(#twilight_zone, #eu-opers etc.) That's what they are there for!
-   Also, be aware that servers will notify all the operators online of
-remote SQUITs and CONNECTs via WALLOPS.
-
-Please let us know if there should be any additions to this guide. Again,
-this is not MANDATORY, this is just a GUIDE. Please conduct yourself as 
-an IRC Operator would...you are looked upon for assistance, both emotional
-and mental. 
-
-Helen Rose		Christopher Davis	Noah Friedman
-<hrose@cs.bu.edu>	<ckd@cs.bu.edu>		<friedman@ai.mit.edu>
-
-January, 1991
-
-
-Updated by
-
-Mauri Haikola
-<mjh@stekt.oulu.fi>
-
-May, 1992

doc/coding-guidelines

@@ -0,0 +1,97 @@
+
+Some minor rules about patches & modifications to UnrealIRCd
+
+1. When making a change, always add a small description in Changes, in the
+   BOTTOM. Be sure to mention the bugid# (or muliple id's) if you are fixing
+   a bug from a bugtracker, and be sure to credit the reporter. Use:
+   'Fixed blahblahblah, reported by Blah (#0001234).'
+   Or, for example, for features:
+   'Added support for blahbalbvdshd, suggested by Blah (#0001235).'
+   Or something similar ;)
+
+2. If new files are made, it must contain proper copyright headers,
+   and a $Id$ somewhere.
+
+3. /*  
+    * These kind of comments
+   */
+ 
+   NOT
+ 
+   // These kind of comments
+
+4. 	if (something == 1) 
+   	{
+		moo; /* comment */
+		/* This does what what what */
+		cow(go(moo));
+	}
+	
+	NOT 
+	
+	if (something == 1) {
+	}
+	
+5. Do not touch version.c.SH or version.h, unless you are a head coder
+   if you need a credit in, contact us
+   
+6. Patches are submitted to coders@lists.unrealircd.org, 
+   using "cvs diff -u > patchname". A submision must contain description of
+   what it does, etc.
+ 
+7. Protocol changes must be discussed before making patches for it.
+
+8. We do NOT rip people off. If we use other people's code, it MUST be
+   properly credited.
+
+9. We generally use tabsize 4 and 8. In any case, use tabs and NOT spaces.
+   Some code is old and horrible and has a mix of tabs and spaces used for
+   spacing, that's something we do not want to have ;)
+
+10. Be careful about overflows. As you know a line from a user can never be longer
+    than 511 (510?) characters, sometimes you can use this knowledge to your
+    advantage. Whenever it's not safe or when you don't know what input size you
+    can expect, use strlcpy instead of strcpy. Do not ever use strncpy, this is
+    older, slower, and does not add proper zero termination.
+    For the same reason, use snprintf if really needed. Note though, that using
+    ircsprintf with a bigger buffer (eg: 1024 bytes) is MUCH faster, so preferably
+    use that instead of snprintf. The same can be true for strcpy vs strlcpy in
+    some circumstances as well.
+
+11. Speed.  When optimizing or writing code, keep in mind that readability and
+    stability comes first, and after that comes speed. So we'd rather prefer some
+    readable code (even if difficult) over some odd highly optimized routine which
+    nobody understands, is difficult to extend, and might have several bugs.
+    As mentioned earlier: use ircsprintf, not sprintf (this is because ircsprintf
+    is optimized for simple strings like the ones we use).
+    Prefer ircsprintf with a bigger buffer over the use of snprintf, since
+    ircsprintf is much faster.
+
+12. Initialize your structs and use the proper memory calls.
+    In UnrealIRCd we use MyMalloc, MyMallocEx and MyFree (so not malloc/free).
+    MyMalloc usually maps to malloc, and MyMallocEx is a malloc plus filling
+    the memory area (eg: the struct) with zero's (a la calloc).
+    Use of MyMallocEx is suggested. In general you should not be using MyMalloc.
+    "But MyMalloc is faster!" you might say. This is true, but using MyMallocEx
+    has very little speed impact and enourmous benefits: people tend to forget
+    to set certain fields in the struct to NULL, or much more common: when
+    someone later on (eg: 1 year later) adds a field to a struct, there could
+    be several places he/she needs to update to make sure x->something is NULL
+    after allocating a new struct. Bad idea.
+    Little speed impact, huge stability benefits, easy decision ;).
+
+13. Comment your code! This should speak for itself...
+    Put comments wherever you think they are needed, to aid any further coders
+    with reading your code.. and, in fact, it will aid yourself as well if you
+    would look back at your code 2 years later.
+    If there's some obscure pitfall, do mention it! Don't just "hope" a next
+    author will see it like you did.
+
+14. Use enums whenever possible, rather than #define constants. Besides making
+    things more clean, it also aids debugging.
+
+15. Whenever you add a new directive or setting, be sure to add documentation
+    for it in unreal32docs, and for new commands in help.conf as well.
+
+16. Whenever you add a new set:: item, be sure to add it to /stats S
+

doc/compiling_win32.txt

@@ -0,0 +1,109 @@
+==[ IMPORTANT MESSAGE ABOUT DISABLING NOSPOOF ]==
+Disabling NOSPOOF at windows (w9x, nt, w2k, xp) is NOT recommended since this
+WILL allow users to use "spoofed hosts" (like the IP of someone you trust).
+
+If you have problems with NOSPOOF, fix your client (bot?) instead (you should PONG
+back to the initial PING at connect).
+
+==[ GENERAL GUIDELINES ]==
+First of all you need Microsoft Visual C++ (see below), compiling with
+cygwin is not supported (nor is there any good reason to do so).
+
+Compatible compilers:
+cygwin     NOT supported. Will not work. Should be no reason to use this anyway.
+msvc 6.x   Microsoft Visual Studio 6 does not work, this compiler is too old.
+msvc 7.x   Microsoft Visual Studio 7.x (.NET) will work just fine
+msvc 8.x   Microsoft Visual Studio 8.x (.NET 2005), including the free kit,
+           should work fine (since Unreal3.2.5).
+
+If you don't have the paid version of Microsoft Visual Studio 7.x, then you can
+use the FREE development kit and PSDK as explained below:
+1. Download the MS Visual Studio Development kit at:
+   http://msdn.microsoft.com/visualc/vctoolkit2003/
+2. Install the Platform Software Development Kit (PSDK) from:
+   http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
+3. NOTE: Whenever you need to compile something we say 'Start the Visual Studio
+   .NET Command Prompt' below, but you - a person using the free version - will
+   actually have to start the Platform SDK Prompt instead (check out the
+   Start Menu).
+
+== Simple compile (no SSL/ZIP/Remote includes) ==
+1. Start the Visual Studio .NET Command Prompt
+2. Go to your UnrealIRCd dir (like: cd \dev\unreal3.2) and then compile with:
+   nmake -f makefile.win32
+   This will generate a wircd.exe and unreal.exe
+3. Copy the src\win32\tre.dll to your UnrealIRCd main dir.
+4. Done!
+
+== Compiling modules ==
+1. Put your module (the .c file) in src\modules (eg: c:\dev\unreal3.2\src\modules).
+2. Start the Visual Studio .NET Command Prompt
+3. Go to your UnrealIRCd dir (like: cd \dev\unreal3.2).
+4. Compile the module with:
+   nmake -f makefile.win32 custommodule MODULEFILE=<name>
+   <name> is the name of the module WITHOUT the .c suffix, so if your
+   module has the filename 'm_crappymod.c', then you use:
+   nmake -f makefile.win32 custommodule MODULEFILE=m_crappymod
+5. Done. A .dll file should have been created.
+
+If you compiled with VC7 and used the official source (not a CVS version,
+but for example 3.2.1 source) then the module should work on all these
+versions (binary compatible) and you could for example put them on
+your website so users can download them.
+Such a module will work on both SSL and non-SSL, there should be no need
+for separate versions... unless, of course, you use SSL-specific code in your
+mod.
+DO NOT download a CVS version & compile your mod and then start
+distributing the .dll for use at another (non-CVS) version!!
+Every time we change a struct (and in some other cases) it makes the
+binary/module binary incompatible which practically means that your module
+might seem to work fine at first (or not..) but will CRASH or cause memory
+corruption and other subtle errors.
+
+== COMPILING WITH ZIP LINKS / SSL / REMOTE INCLUDES SUPPORT ==
+First of all, DO NOT use any precompiled libs from the official
+zlib/openssl/curl sites. We require certain compile parameters.
+Versions downloaded from such sites will often CRASH.
+
+The easiest is to download the UnrealIRCd development package
+which contains zlib, openssl and curl precompiled for you.
+See: www.vulnscan.org/unrealwin32dev/
+
+Just extract it somewhere (eg: to c:\dev).
+Then, use compile flags to enable the features + specify where to look.
+Here are examples if you used c:\dev:
+ZIP: nmake -f makefile.win32 USE_ZIPLINKS=1 ZLIB_INC_DIR="c:\dev\zlib" ZLIB_LIB_DIR="c:\dev\zlib\dll32"
+SSL: nmake -f makefile.win32 USE_SSL=1 OPENSSL_INC_DIR="c:\dev\openssl\include" OPENSSL_LIB_DIR="c:\dev\openssl\lib" 
+CURL: nmake -f makefile.win32 USE_REMOTEINC=1 LIBCURL_INC_DIR="c:\dev\curl\include" LIBCURL_LIB_DIR="c:\dev\curl\lib"
+
+Obviously you can (and probably will) combine all these options, like
+to build a zip+ssl+curl version (all in 1 line):
+nmake -f makefile.win32 USE_ZIPLINKS=1 ZLIB_INC_DIR="c:\dev\zlib" ZLIB_LIB_DIR="c:\dev\zlib\dll32"
+USE_SSL=1 OPENSSL_INC_DIR="c:\dev\openssl\include" OPENSSL_LIB_DIR="c:\dev\openssl\lib" USE_REMOTEINC=1
+LIBCURL_INC_DIR="c:\dev\curl\include" LIBCURL_LIB_DIR="c:\dev\curl\lib"
+
+== SYMBOL FILES ==
+If you get something like this:
+
+  Creating library L_COMMANDS.lib and object L_COMMANDS.exp
+M_OPER.obj : error LNK2019: unresolved external symbol _sendto_snomask_global re
+ferenced in function _m_oper
+
+(note: the exact name of the symbol will vary)
+
+Then you will have to rebuild the wircd.def symbol file. You do this by
+downloading http://www.vulnscan.org/tmp/dlltool.exe and putting the file somewhere
+in your path (eg: c:\winnt\system32).
+Then, to compile you do this:
+nmake -f makefile.win32 [your other options here]
+nmake -f makefile.win32 SYMBOLFILE
+nmake -f makefile.win32 [your other options here]
+
+So basically you just run 'nmake -f makefile.win32 SYMBOLFILE' and then restart
+compiling again.
+
+== COMPILING ZLIB/SSL/CURL YOURSELF ==
+This is off-topic and not explained here.
+Again, use the stuff from the win32 development pack unless you have a good
+reason to do otherwise (in which case we might not support your self-compiled version
+because we work with specific versions / compile options).

doc/faq

@@ -1,193 +0,0 @@
-[ $Id$ ]
-
-UnrealIRCd FAQ
-Made by Stskeeps
-
-This file will contain frequently asked questions about 
-Unreal IRCd. If you need more help email stskeeps@tspre.org
-
-1) * I compile and everything seems fine during the compiling, but when it
-   comes time for the program to link, I get errors complaining about dns and
-   res things. What causes this?
-
-A: You need to make sure -lresolv is included in the "extra libraries"
-   option of ./Config (or IRCDLIBS in top-level makefile)
-
-2) * When I start up the IRCd it complains about something with chdir()?
-
-A: You need to make sure the right directory is specified when you was 
-   asked about "What directory are all the server configuration files in?"
-   ./Config question
-
-3) The server says like: 
-   *** Link server1 -> server2 is now synced [secs: 30 recv: 130.4 sent: 120.0]
-   when I link two servers together, what does that mean?
-
-A: That means the link is "synced" (all infodata transfered about the server).
-   The "secs" (30 in this example) means it took 30 seconds to do the sync
-   "recv: 130.4" means there was recieved 130 KiloBytes and 4 bytes.
-   "sent: 120.0" means there was sent 120 kilobytes from my side.
-
-4) What is a negative TS split?
-
-A: Every computer/server has got a time (so they can do TimeStamps) .. 
-   When the clock on the computer is set wrong and the computer it links 
-   upto is wrong it creates a Negative TS split (means time is lower it
-   actually is. How to fix this is contacting the root of the machine
-   and ask him to fix the time (when you made sure it's YOUR server that's 
-   wrong)
-
-5) What is an uProtocol ?
-
-A: UnrealIRCd uses numbers to check if a link is compatible with itself
-   F.x Unreal v2.1.3 has got number 2103 while version 2.1 only has got 
-   2100 - This means .. if the number is lower/higher than the uProtocol
-   the server uses, it's an incompatible link (of some reasons)
-
-6) How does T:Lines work and what are they?
-
-A: T:Lines is a new Unreal feature that makes it able to show different 
-  MOTDs and RULES to people who matches a certain hostmask . Lemme show you some examples:
- 
-   T:*.dk:motds/danish.motd:rules/danish.rules
-   T:*.fr:motds/french.motd:rules/french.rules
- 
-  This will get people from Denmark to see the "Danish" MOTD and the "Dandish" RULLES
-  and people from France to see the French ones:) 
-  
-  NOTE: T:Lines are read up side down so if you have a T:*:ircd.motd:ircd.rules in the bottom
-        it should be at the top so the other motd lines can work as well
-
-7) Where can i download updates to Unreal?
-
-A: Mostly you can download the newest version at 
-   http://unreal.tspre.org
-
-   Versions may be spewed out regulary due to new features and bugs.. 
-
-8) Why does it say "unlimit core failed" or something when I boot the IRCd?
-A: It's just a warning, mainly just ignore it.
-
-9) I use Linux Mandrake and ./Config always hangs! What can I do??
-A: Go edit the Config script and remove those lines:
--SNIP START-
-cat > $TMP <<__EOF__
-#$STRINGH STRINGH
-#$STRINGSH STRINGSH
-#ifdef STRINGH
-#include <string.h>
-#endif
-#ifdef STRINGSH
-#include <strings.h>
-#endif
-main()
-{
-	char  *t = "a", *s = strtok(t, ",");
-	if (!strcmp(t, s))
-		exit(0);
-	exit(1);
-}
-__EOF__
-$COMP >/dev/null 2>&1
-if [ $? -ne 0 ] ; then
-	echo $n " strtok$c"
-	NSTRTOK=define
-else
-	$EXEC
-	if [ $? -ne 0 ] ; then
-		echo $n " strtok$c"
-		NSTRTOK=define
-	fi
-fi
-$RM -f $EXEC $TMP
---- SNIP END---
-And replace it by
-NSTRTOK=undef
-
-This should get it to work=) (thanks to Joe Whipple for reporting this bug)
----END----
-
-10) Hosts show up as (null).network.net !!
-A:  This is because you have forgotten to include the network file.
-    The correct form is (in unrealircd.conf)
-    Include ..........: <network file>
-
-    If this doesn't work .. seek me at irc.global-irc.net #unrealircd
-
-11) The IRCd uses like 66.7% CPU !!!?
-A:  Try run it with nice :
-    /usr/bin/nice -n 19 src/ircd
-
-    if services go this way too just place ./<name> instead of src/ircd
-    Any more support seek me at the default place:P
-
-12) My IRCd which runs on a FreeBSD says something about FDs and
-    Max: 0 What shall I do?? 
-A:  Well it's somekinda bug but you can workaround it by removing those
-    lines in src/s_bsd.c: (init_sys())
-
-<- snippet 1 ->
-#ifdef RLIMIT_FD_MAX
-	struct rlimit limit;
-	int     pid;
-
-	if (!getrlimit(RLIMIT_FD_MAX, &limit))
-	    {
-# ifdef	pyr
-		if (limit.rlim_cur < MAXCONNECTIONS)
-#else
-		if (limit.rlim_max < MAXCONNECTIONS)
-# endif
-		    {
-			(void)fprintf(stderr,"ircd fd table too big\n");
-			(void)fprintf(stderr,"Hard Limit: %d IRC max: %d\n",
-				limit.rlim_max, MAXCONNECTIONS);
-			(void)fprintf(stderr,"Fix MAXCONNECTIONS\n");
-			exit(-1);
-		    }
-# ifndef	pyr
-		limit.rlim_cur = limit.rlim_max; /* make soft limit the max */
-		if (setrlimit(RLIMIT_FD_MAX, &limit) == -1)
-		    {
-			(void)fprintf(stderr,"error setting max fd's to %d\n",
-					limit.rlim_cur);
-			exit(-1);
-		    }
-# endif
-	    }
-#endif
-
-<-snippet 2->
-#ifdef sequent
-# ifndef	DYNIXPTX
-	int	fd_limit;
-
-	fd_limit = setdtablesize(MAXCONNECTIONS + 1);
-	if (fd_limit < MAXCONNECTIONS)
-	    {
-		(void)fprintf(stderr,"ircd fd table too big\n");
-		(void)fprintf(stderr,"Hard Limit: %d IRC max: %d\n",
-			fd_limit, MAXCONNECTIONS);
-		(void)fprintf(stderr,"Fix MAXCONNECTIONS\n");
-		exit(-1);
-	    }
-# endif
-#endif
-
-13) I run debian-sparc and i get errors when compiling in match.c
-    What should I do?
-A: If it says like this
-<-snippet->
-match.c: In function 'myncmp':
-match.c:247: argument 'str1' doesn't match prototype
-/usr/include/string.h:255: prototype declaration
-match.c:247: argument 'str2' doesn't match prototype
-/usr/include/string.h:255: prototype declaration
-match.c:247: argument 'n' doesn't match prototype
-/usr/include/string.h:255: prototype declaration
-<-end of snippet>
-
-Then go into include/setup.h and add this line:
-#define GOT_STRCASECMP
-
-(C) Carsten Munk 1999

doc/irc.1

@@ -1,82 +0,0 @@
-.\" $Id$
-.TH IRC 1 "7 October 1990"
-.SH NAME
-irc \- User Interface to Internet Relay Chat Protocol
-.SH SYNOPSIS
-\fBirc\fP [\fB-p\fP \fIportnum\fP] [\fB-c\fP \fIchannel\fP] [ \fInickname\fP [ \fIserver\fP ]]
-.SH DESCRIPTION
-.LP
-\fBIrc\fP is a user interface to the Internet Relay Chat, a CB-like
-interactive discussion environment.  It is structured into \fIchannels\fP,
-which are public discussion forums, and also allows for private intercommunication.
-Each participant has a \fInickname\fP, which is the one specified in the command
-line or else his login name.
-.LP
-Once invoked, \fBirc\fP connects as a client to the specified server,
-\fIserver\fP or to the default one (see below).  The screen splits into a dialogue
-window (the major part
-of the screen) and a command line, from which messages can be sent and
-commands given to control irc.
-.SH COMMAND SYNTAX
-The syntax of irc commands is of the form \fB/COMMAND\fP.  The most notable
-ones are listed below.  For an uptodate list, use the \fBHELP\fP command
-of \fBirc\fP.  Case is ignored.
-.IP "\fB/ADMIN\fR [\fIserver\fP]"
-Prints administrative information about an IRC \fIserver\fP.
-.IP "\fB/AWAY\fP [\fImessage\fP]"
-Mark yourself as being away (with an automatic reply \fImessage\fP
-if specified)
-.IP "\fB/BYE\fR, \fB/EXIT\fR, \fB/QUIT\fR"
-Terminate the session
-.IP "\fB/CHANNEL\fR [\fIchannel\fP]"
-Join another \fIchannel\fP
-.IP "\fB/CLEAR\fR"
-Clear the screen
-.IP "\fB/HELP\fR [\fIcommand\fP]"
-Display a brief description of the \fIcommand\fP (or list all commands, if none
-specified).
-.IP "\fB/SUMMON\fR \fIuser\fP"
-Allows to summon a \fIuser\fP specified as a full Internet address, i.e.,
-\fIlogin@host.domain\fP, to an IRC dialogue session (in much the same
-way as the talk(1) command).  It is usable ONLY if the irc daemon runs on
-the target machine (host.domain).
-.IP "\fB/TOPIC\fR \fItopic\fP"
-Sets the \fItopic\fP for the current channel
-.IP "\fB/WHO\fR [\fIchannel\fP|*]"
-Lists all users of IRC if no argument, of the specified \fIchannel\fP or of the
-current channel (*).
-.SH ARGUMENTS
-.IP "\fB-p\fP \fIportnum\fP"
-TCP/IP "port number.  Default is 6667 and this option should seldom if ever"
-be used.
-.IP "\fB-c\fP \fIchannel\fP"
-\fIChannel\fP number to join upon beginning of the session.  Default is no channel.
-.IP "\fInickname\fP"
-\fINickname\fP used in the session (can be changed with the \fB/NICK\fP command).
-Default is user login name.
-.IP "\fIserver\fP"
-\fIServer\fP to connect to.  Default is specified in the irc system configuration
-file, and can be superseded with the environment variable IRCSERVER.
-.SH EXAMPLE
-.RS
-.nf
-tolmoon% \fBirc -p6667 Wizard tolsun\fP
-.fi
-.RE
-.LP
-connects you to irc server in host tolsun (port 6667) with nickname Wizard
-.SH COPYRIGHT
-Copyright (c) 1988 University of Oulu, Computing Center, Finland.
-.nf
-Copyright (c) 1988,1989,1990 Jarkko Oikarinen
-.nf
-All rights reserved.
-For full COPYRIGHT see LICENSE file with IRC package.
-.SH "SEE ALSO"
-ircd(8)
-.SH BUGS
-What bugs ?
-.SH AUTHOR
-Jarkko Oikarinen <jto@tolsun.oulu.fi>
-.nf
-Manual page updated by Michel Fingerhut <Michel.Fingerhut@ircam.fr>

doc/ircd.8

@@ -1,140 +0,0 @@
-.\" $Id$
-.TH IRCD 8 "29 March 1989"
-.SH NAME
-ircd \- The Internet Relay Chat Program Server 
-.SH SYNOPSIS
-.hy 0
-.IP \fBircd\fP
-[-a] [-c] [-i] [-o] [-q] [-t] [-d directory]
-[-f configfile] [-x debuglevel] [-h hostname] [-p portnum]
-.SH DESCRIPTION
-.LP
-\fIircd\fP is the server (daemon) program for the Internet Relay Chat
-Program.  The \fIircd\fP is a server in that its function is to "serve"
-the client program \fIirc(1)\fP with messages and commands.  All commands
-and user messages are passed directly to the \fIircd\fP for processing
-and relaying to other ircd sites.  The \fIirc(1)\fP program depends upon
-there being an \fIircd\fP server running somewhere (either on your local
-UNIX site or a remote ircd site) so that it will have somewhere to connect
-to and thus allow the user to begin talking to other users. 
-.SH OPTIONS
-.TP
-.B \-d directory
-This option tells the server to change to that directory and use
-that as a reference point when opening \fIircd.conf\fP and other startup
-files.
-.TP
-.B \-o
-Starts up a local ircdaemon. Standard input can be used to send IRC
-commands to the daemon. The user logging in from standard input will
-be given operator privileges on this local ircd. If ircd is a setuid program,
-it will call setuid(getuid()) before going to local mode. This option
-can be used in inetd.conf to allow users to open their own irc clients
-by simply connecting their clients to the correct ports. For example:
-.TP
-.B
-irc stream tcp nowait irc /etc/ircd ircd \\-f/etc/ircd.conf \\-o
-
-allows users connecting to irc port (specified in /etc/services) to start
-up their own ircdaemon. The configuration file should be used to check from
-which hosts these connections are allowed from. This option also turns
-on the autodie option -a.
-.TP
-.B \-a
-Instructs the server to automatically die off if it loses all it's clients.
-.TP
-.B \-t
-Instructs the server to direct debugging output to standard output.
-.TP
-.B \-x#
-Defines the debuglevel for ircd. The higher the debuglevel, the more stuff
-gets directed to debugging file (or standard output if -t option was used
-as well).
-.TP
-.B \-i
-The server was started by inetd and it should start accepting connections
-from standard input. The following inetd.conf-line could be used to start
-up ircd automatically when needed:
-.TP
-.B
-ircd stream tcp wait irc /etc/ircd ircd \-i
-
-allows inetd to start up ircd on request.
-.TP
-.B \-f filename
-Specifies the ircd.conf file to be used for this ircdaemon. The option
-is used to override the default ircd.conf given at compile time.
-.TP
-.B \-c
-This flag must be given if you are running ircd from \fI/dev/console\fP or
-any other situation where fd 0 isnt a tty and you want the server to fork
-off and run in the background. This needs to be given if you are starting
-\fIircd\fP from an \fIrc\fP (such as \fI/etc/rc.local\fP) file.
-.TP
-.B \-q
-Using the -q option stops the server from doing DNS lookups on all the
-servers in your \fIircd.conf\fP file when it boots. This can take a lengthy
-amount of time if you have a large number of servers and they are not all
-close by.
-.TP
-.B \-h hostname
-Allows the user to manually set the server name at startup. The default
-name is hostname.domainname.
-.B \-p portname
-Specifies the port where the daemon should start waiting for connections.
-This overrides the default which is given at compile time.
-.TP
-.SH
-If you plan to connect your \fIircd\fP server to an existing Irc-Network,
-you will need to alter your local IRC CONFIGURATION FILE (typically named
-"ircd.conf") so that it will accept and make connections to other \fIircd\fP
-servers.  This file contains the hostnames, Network Addresses, and sometimes
-passwords for connections to other ircds around the world.  Because 
-description of the actual file format of the "ircs.conf" file is beyond the
-scope of this document, please refer to the file INSTALL in the IRC source
-files documentation directory.
-.LP
-BOOTING THE SERVER:  The \fIircd\fP server can be started as part of the
-UNIX boot procedure or just by placing the server into Unix Background.
-Keep in mind that if it is *not* part of your UNIXES Boot-up procedure 
-then you will have to manually start the \fIircd\fP server each time your
-UNIX is rebooted.  This means if your UNIX is prone to crashing
-or going for for repairs a lot it would make sense to start the \fIircd\fP
-server as part of your UNIX bootup procedure.  In some cases the \fIirc(1)\fP
-will automatically attempt to boot the \fIircd\fP server if the user is
-on the SAME UNIX that the \fIircd\fP is supposed to be running on.  If the
-\fIirc(1)\fP cannot connect to the \fIircd\fP server it will try to start
-the server on it's own and will then try to reconnect to the newly booted
-\fIircd\fP server.
-.SH EXAMPLE
-.RS
-.nf
-tolsun% \fBircd\fP
-.fi
-.RE
-.LP
-Places \fIircd\fP into UNIX Background and starts up the server for use.
-Note:  You do not have to add the "&" to this command, the program will
-automatically detach itself from tty.
-.SH COPYRIGHT
-(c) 1988,1989 University of Oulu, Computing Center, Finland,
-.LP
-(c) 1988,1989 Department of Information Processing Science,
-University of Oulu, Finland
-.LP
-(c) 1988,1989,1990,1991 Jarkko Oikarinen
-.LP
-For full COPYRIGHT see LICENSE file with IRC package.
-.LP
-.RE
-.SH FILES
- /etc/utmp
- "irc.conf"
-.SH "SEE ALSO"
-irc(1)
-.SH BUGS
-None... ;-) if somebody finds one, please inform author
-.SH AUTHOR
-Jarkko Oikarinen, currently jto@tolsun.oulu.fi,
-manual page written by Jeff Trim, jtrim@orion.cair.du.edu,
-later modified by jto@tolsun.oulu.fi.

doc/m4macros

@@ -1,47 +0,0 @@
-[ $Id$ ]
-The following macros are included in "ircd.m4" for use with the m4 text
-preprocessor.  "ircd.m4" is parsed before the IRC server conf file so they
-are all available for use with that.
-
-NOTE:  The "ircd.m4" file is *ONLY* created by a "make install".
-
-VERSION - current version string as in patchlevel.h
-DEBUGMODE - if DEBUGMODE is define in config.h, is also defined for m4.
-HOSTNAME - taken from hostname(1)
-USER - username of person doing the "make install"
-PORT - default port number as in config.h
-PFREQ - default ping frequency as in config.h
-CFREQ - default connect frequency as in config.h
-MAXSENDQ - default max sendq as in config.h
-CL - use this to wrap a class number
-HOST - use this to wrap a hostname
-HOSTM - use this to wrap the hostmask number in N-lines
-ID - when wrapping the host field in an I-line, causes ident string return
-     to be used instead of user supplised username.
-PASS - use this to wrap passwords in C/N/I/O lines
-PING - use this to wrap the ping value in Y-lines
-APORT - use this to wrap the port number in I-lines
-CPORT - use this to wrap the port number in C-lines
-SERV - use this to wrap server names
-
-You might use some of these as
-C:foo.bar.edu:PASS(boo):foo.bar.edu:APORT(6667)
-I:ID(128.250.*)::ID(*.mu.oz.au):CPORT(6667)
-
-In addition to these (rather weak macros), some more complete ones are
-defined which already perform the above.
-
-ADMIN - provide fields to it as you would an A-line
-ALLOW - provide fields to it as you would an N-line
-BAN - provide fields to it as you would an K-line
-CLASS - provide fields to it as you would an Y-line
-CLIENT - provide fields to it as you would an I-line
-CONNECT - provide fields to it as you would an C-line
-ME - provide fields to it as you would an M-line
-HUB - first parameter is server you want to hub, second is optional and is
-      a mask against which other servers introduced must match against.
-LEAF - works like HUB, except that the mask is matched against server names
-       to check if the link should be dropped.
-SERVER - uses 6 fields, the first 4 as are found in an N-line, the last two
-         should be as you would use in a C-line.  It expands out to provide
-         both a C and N line.

doc/server-compile-guide

@@ -1,294 +0,0 @@
-  [ $Id$ ]
-From: Carlo Kid - Runaway <carlo@sg.tn.tudelft.nl>
-Subject: GUIDE for compiling your server
-To: wastelanders@rush.cc.edu (New Wastelanders MailingList)
-Date: Thu, 26 May 94 13:44:10 METDST
-Cc: carlo@sg.tn.tudelft.nl
-Mailer: Elm [revision: 66.33]
-Status: RO
-
-GUIDE for compiling your server,     by Runaway
-===============================================
-
-First of all you must get all the files you need, as an example
-I will explain how to compile irc2.8.19.U3.2.
-The files you'll need in general are:
-
-- irc2.8.19.U3.2.tar.gz
-
-Or, when you already have an older version -say irc2.8.19.U3.1- a patch:
-
-- irc2.8.19.U3.1-2.patch
-
-It is possible you need more then one patch, especially when you already
-upgraded more often. But in that case you already have those old patches.
-Of course, in that case, you also already have the old directory tree:
-
-/home..../yourname/....ircd/irc2.8.19.U3.1/
-
-Scripts, patches and directory trees
-====================================
-
-It is good practise to:
-1) Call the directory tree after the version
-2) Let this directory ONLY contain what comes with the .tar.gz file!
-   Thus: Do NOT put ircd.conf, or any patches etc in it!!!
-   In general, you must be able to delete this whole directory tree
-   when you still have the original .tar.gz file and patches applied to it.
-3) Put it in a directory ending on /ircd, THIS directory will contain
-   your ircd.motd, ircd.pid, ircd.conf and patches...
-
-So, you end up with:
-
-...ircd/irc2.8.19.U3.1-2.patch
-...ircd/irc2.8.19.U3.1.tar.gz
-
-or just:
-
-...ircd/irc2.8.19.U3.2.tar.gz
-
-at once.
-
-Before you can delete the old directory tree, you must be SURE to save
-everything thats in it. This is thus the .tar.gz file, all patches but
-ALSO the following files:
-
-Makefile
-include/config.h
-include/setup.h
-
-You should always keep a copy of those files OUTSIDE the irc2.8.19.U3.2/
-directory tree. For instance:
-
-...ircd/irc.personal/Makefile
-...ircd/irc.personal/include/config.h
-...ircd/irc.personal/include/setup.h
-
-To make these backups easy, you should make a script, called backup.personal
-containing:
-
-cp Makefile ../irc.personal/Makefile
-cp include/config.h ../irc.personal/include/config.h
-cp include/setup.h ../irc.personal/include/setup.h
-
-If you also change anything in the other Makefiles (ircd/Makefile and
-common/Makefile) you can add those too. Be sure to make the directories
-by hand first.
-
-Make the script 'backup.personal' executable with:
-chmod 700 backup.personal
-You must be able to run it from any directory, so put it in your ..bin/
-
-Ok... so now you have a backup of everything. If you wanted to start
-ALL over you could delete the directory tree, unzip and untar the archive
-again, apply all patches to it, change the Makefile and config.h again,
-put setup.h back, recompile and reinstall.
-In some cases it is easy to do this with an other script, I call it 'repatch',
-it provides you with an easy-to-change overview of the patched you have used.
-Here is how my 'repatch' looks now (it is located in .../ircd/repatch).
-
-cd ~/irc/ircd
-rm -rf irc2.8.19 irc2.8.19.U3.2
-zcat irc2.8.19.tar.gz | tar xf -
-mv irc2.8.19 irc2.8.19.U3.2
-cd irc2.8.19.U3.2
-#patch -p1 < ../Makefile.config.h.patch 2> ../patch.out
-#cp ../setup.h include/setup.h
-patch -p1 < ../irc2.8.19-TSpre8.2.patch 2>> ../patch.out
-patch -p1 < ../irc2.8.19.TSpre8-note.patch 2>> ../patch.out
-patch -p1 < ../irc2.8.19.TSpre8-wallops.patch 2>> ../patch.out
-patch -p1 < ../irc2.8.19.TSpre8-bquiet.patch 2>> ../patch.out
-patch -p1 < ../irc2.8.19.TSpre8-silence.2.patch 2>> ../patch.out
-#patch -p1 < ../irc2.8.19.U3-ban.patch 2>> ../patch.out
-make clean
-vi include/patchlevel.h
-grep -e '\.rej' -e '[Ff]ail' -e fuzz ../patch.out
-
-As you can see I commented out the patches Makefile.config.h.patch and
-irc2.8.19.U3-ban.patch, and don't copy setup.h here. This is because
-I wanted to make a virgin .U3.2.tar.gz for distribution via ftp-sites.
-If I change the name of the directory, I have to change it in three
-places :/
-This script forces me to edit the patchlevel.h :) :)
-The last grep warns me if anything went wrong with the patches.
-
-Moreover, as you can see, I have a 'Makefile.config.h.patch'.
-You should make your own as soon as you completely installed
-and tested your server. It is very handy for re-installing a new
-version.
-
-To make this patch, edit the Makefile's and and config.h and type:
-
-backup.personal
-cd ..
-rm -rf irc2.8.19
-zcat irc2.8.19.tar.gz | tar xf -
-diff -rc irc2.8.19 irc.personal > Makefile.config.h.patch
-
-Check it with an editor if it looks ok. In the above, 'irc2.8.19.tar.gz'
-is the virgin 'Avalon' version, I change the Makefiles in the .U3
-however also, so you might wanna use the virgin .U3.2.tar.gz.
-
-Starting ALL over (or begining for the first time)
-==================================================
-
-This is about EDITTING the Makefile(s) and config.h, and creating the
-setup.h for the first time.
-
-2.8.19 is different from 2.8.16 and before. You will have to EDIT the
-Makefile and config.h that comes with the distribution. You can NOT
-use the old Makefile and config.h you had !
-
-First write down the path you want to use where you are going to put
-the ircd.conf etc...
-
-Edit the Makefile. Comments are in it. You should simply define that
-what is needed for your Operating System.
-
-Then edit the config.h
-
-Then run ./Config to create setup.h ... at first simply hit return all the
-time. If you insist on using gcc instead of cc, you must edit that in your
-Makefile BEFORE running setup.h. You can't change that running Config,
-although it asks for it. If you have more then one cc, you can add the
-right path to in the Makefile (if it uses the wrong one).
-
-Since U3.2, I changed the Makefile and config.h a little. The changes are:
-- I added note.o to the dependency
-- I added *.orig files to the 'make clean' (otherwise the *.orig generated
-  by some 'patch' programs will be left).
-If you want this too, and you have .U3.1, you can get the patch from
-sg.tn.tudelft.nl (file: Makefile.conf.U3.patch).
-
-As soon as you are done, run backup.personal. To stay up to date with your
-backup.
-
-Then make the Makefile.conf.patch as described above. (or wait with that
-till you are sure it works... otherwise it might be done more then once
-which is a waste of time).
-
-Special remarks
----------------
-
-Makefile:
-First occurance of
-        CC=cc
-Change this NOT if you want another compiler, add another CC= later, close
-to your OS specific #defines...
-
-# IRCDDIR must be the same as DPATH in include/config.h
-#
-IRCDDIR=/sb/users/carlo/irc/ircd
-Make sure you use the same path in the config.h :)
-
-SUBDIRS=common ircd
-By removing the 'irc' from this line, you stop 'make' from making the client
-as well.
-
-config.h:
-/*
- * NOTE: On some systems, valloc() causes many problems.
- */
-#undef  VALLOC                  /* Define this if you have valloc(3) */
-I never try it, even if I have it.
-
-#define USE_VARARGS
-For defines like this, you best check the online manual if you have them
-(man vprintf in this case)... I didn't have man page for vscanf() but it
-still worked... (I DO have them for vprintf and vsprinf).
-
-#undef  DEBUGMODE               /* define DEBUGMODE to enable debugging mode.*/
-Debug mode uses a lot more memory and is a lot slower. ONLY define
-when your server gives problems like crashing/coredumping, or other
-things like not wanting to startup etc. In other words: when you are really
-*USING* this feature to do DEBUGing !
-
-#define NPATH "/sb/users/carlo/irc/server/Undernet/.ircdnote"
-The '#ifdef notdef' '#endif' around NPATH mean: notdef = NOT DEFINED.
-You should *never* #define notdef... It is used to "comment out" *examples*.
-By defining it, you enable all examples (like making your server SUI :/)
-Simply *remove* the lines '#ifdef notdef' and '#endif' around the NPATH.
-
-#define DPATH   "/sb/users/carlo/irc/ircd"
-Must be the same as in the Makefile!
-#define SPATH   "/sb/users/carlo/bin/ircd" /* path to server executeable */
-This is used when you do a /RESTART. For fast restarting a NEW version (upgrade)you can let this point to a symbolic link, and then change this link to the
-new executable. Do a 'restart' and voila...
-For instance:
-.../bin/ircd.U3.2*
-.../bin/ircd -> ircd.U3.2
-The last made with:
-ln -s ircd.U3.2 ircd
-Then when you upgrade:
-rm ircd
-ln -s ircd.U3.3 ircd
-and a /RESTART
-
-#undef  CRYPT_LINK_PASSWORD
-Make sure your ircd.conf isn't world readable like on pasadena :/
-(and on ircserver.et.tudelft.nl once - we DID have to change all passwords
- then)
-
-Compiling the server
-====================
-
-*** FIRST edit your include/patchlevel.h ***
-
-If you don't want to compile the client, you can change the Makefile
-as mentioned above, or type:
-make server
-
-After a succesfull compilation (ignore warning ;), you can type
-make install
-or just
-cp ircd/ircd ~/bin/ircd.U3.2
-cd ~/bin
-chmod 700 ircd.U3.2
-rm ircd
-ln -s ircd.U3.2 ircd
-
-I changed my Makefile to do the latter thing when I type 'make install'
-
-Then run the server by typing 'ircd'. Don't do this on the
-...ircd/irc2.8.19.U3.2/ircd/ directory, because when in your PATH the
-'.' comes before your '~/bin' you start up THAT exucutable, disallowing
-you to recompile later (text file busy).
-
-Compile errors
-==============
-
-If anything goes wrong with note, it most likely is because you
-1) Didn't define NPATH correctly
-2) Didn't add the note.o to the dependencies.. remove note.o and recompile.
-
-[ For a non-undernet version: irc2.8.19.tar.gz is bugged, get the -note.patch
-  from ftp.undernet.org. ]
-
-If you get problems while linking saying it has undefined _something
-and something is something with 'res', you must add -lresolv to your
-IRCDLIBS in the Makefile.
-
-If you get problems with any function beging defines twice are giving
-errors like not compatible with previous definition (likely atol() in
-note.c), just remove that whole function from the .c file (put #ifdef notdef
-around it). You have it already in your system libraries.
-
-Last remarks
-============
-
-Add those U: lines!!!
-And change your ircd.motd to reflect the new commands/features :)
-( /MOTD uxb*   -- Nice motd RedRum! :)
-
--------------------------------------------------------------------
-
-Run
-
---
--------------------------------------------------------------------------------
-|  carlo@sg.tn.tudelft.nl           |  Run @ IRC                              |
-|                                   |  Admin of Delft.NL.EU.undernet.org      |
-| * Don't expect anything of live,  |  and      Ircserver.et.tudelft.nl       |
-| or you'll miss all the rest of it.|                                         |
--------------------------------------------------------------------------------
-

doc/technical/005.txt

@@ -0,0 +1,167 @@
+Numeric 005 Documentation (c) 2002-2005 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
+
+Numeric 005 allows the server to inform the client of any protocol specific features in the
+IRCd.  The numeric is sent at connection time immediately after numeric 004. Additionally
+the numeric is sent when a /version request is made by a local user, for remote users
+numeric 105 is used but contains the same information.
+
+Due to the limit imposed by RFC1459 on both the buffer size (512) and the amount of
+parameters that can be sent in a single command (15) a total of 13 parameters may be
+specified in each 005. Because of this, a client must be able to accept multiple 005s
+consecutively. The format for the 005 message is as follows:
+
+":" <servername> "005" SPACE <nickname> SPACE <token[=value]> SPACE ... ":are supported
+by this server"
+
+Currently UnrealIRCd supports several tokens that are included in numeric 005. A list of
+all tokens, their respective value and a brief description are listed below.
+
+Unreal attempts to follow the proposed ISupport standard as much as possible. Unreal only
+ignores the standard in one regard, the TARGMAX token. This token is believed to be 
+impractical and technically impossible to correctly implement due to existing limitations
+in the standard. Therefore, this token is not currently supported. 
+
+Unreal does additionally provide a few tokens which are not specified in the standard, these
+include: HCN, AWAYLEN, WATCH, SILENCE, EXTBAN, ELIST, and CMDS. Unreal also maintains a few
+legacy tokens such as MAXCHANNELS and WALLCHOPS to ensure compatibility until the ISupport
+standard is more widely accepted by clients.
+
+Token         Value           Default Value                Description
+------------------------------------------------------------------------------------------------
+MAP           none            none                         Informs the client that the /map 
+                                                           command is present. [Obsolete]
+
+KNOCK         none            none                         Informs the client that the /knock
+                                                           command is present. [Obsolete]
+
+SAFELIST      none            none                         The LIST command is sent in 
+                                                           multiple iterations so that the
+                                                           client's queue does not get filled
+                                                           causing the user to be killed.
+
+HCN           none            none                         The server supports the HCN
+                                                           (Hybrid Connect Notice) protocol.
+
+MAXCHANNELS   number          10                           The maximum number of channels a
+                                                           user may join. [Deprecated]
+
+MAXBANS       number          60                           The maximum number of bans that
+                                                           may be placed for a channel.
+                                                           [Obsolete]
+
+NICKLEN       number          30                           Maximum length of a user's
+                                                           nickname.
+
+TOPICLEN      number          307                          Maximum length of a channel's
+                                                           topic.
+
+KICKLEN       number          307                          Maximum length of a kick reason.
+
+MAXTARGETS    number          20                           Maximum targets for the PRIVMSG
+                                                           command.
+
+AWAYLEN       number          307                          Maximum length of an away message.
+
+WALLCHOPS     none            none                         Indicates that you may use
+                                                           NOTICE/PRIVMSG to send to +ohv by
+                                                           using PRIVMSG/NOTICE [@|%|+]#channel.
+                                                           [Deprecated]
+ 
+WATCH         number          128                          Indicates the presence of the
+                                                           WATCH command and specifies the
+                                                           maximum number of watch entries.
+
+SILENCE       number          15                           Indicates the maximum number of
+                                                           entries on the silence list.
+
+MODES         number          13                           Indicates the number of channel
+                                                           modes with parameters that may be
+                                                           sent at one time.
+
+CHANTYPES     chars           #                            Indicates the prefixes available
+                                                           for channels.
+ 
+PREFIX        (modes)prefixes (qaohv)~&@%+                 Indicates the modes on a channel
+                                                           that corespond to the given
+                                                           nickname prefixes.
+
+CHANMODES     A,B,C,D         be,kfL,lj,                   Specifies how each channel mode is
+                              psmntirRcOAQKVHGCuzNSMT      set/unset. The A section specifies
+                                                           modes that add a nick/mask to a
+                                                           list. The B section specifies
+                                                           modes that require a parameter
+                                                           to be both set and unset. The C
+                                                           section specifies modes that
+                                                           only require a parameter to be
+                                                           set, and the D section
+                                                           specifies modes that require no
+                                                           parameters.
+
+NETWORK       string          no default value             Specifies the name of the
+                                                           network that the server is
+                                                           connected to.
+
+CASEMAPPING   string          ascii                        Specifies what definition the
+                                                           server uses when determining if
+                                                           characters are upper/lowercase
+                                                           of eachother.
+
+EXTBAN        prefix,types    ~,cqnr                       Specifies what extbans are
+                                                           supported by the server. The prefix
+                                                           defines which character indicates
+                                                           an extban and the types defines
+                                                           which extbans the server supports.
+
+ELIST         flags           MNUCT                        Specifies the set of extended LIST
+                                                           options supported. The M flag 
+                                                           indicates mask based searching,
+                                                           the N flag indicates negative
+                                                           mask based searching. The U flag
+                                                           means support for user count
+                                                           searching. The C flag allows channel
+                                                           creation time searching, and the T
+                                                           flag allows topic set time 
+                                                           searching.
+
+CMDS          commands        MAP,KNOCK,DCCALLOW,USERIP    Specifies a series of commands that
+                                                           can be useful for the client to know
+                                                           exist as they may provide a more
+                                                           efficient means for the client to
+                                                           accomplish a specific task. This
+                                                           token replaces the MAP and KNOCK
+                                                           tokens.
+
+STATUSMSG     flags           ~&@%+                        Specifies the mode flags that may
+                                                           prefix a channel name in a PRIVMSG
+                                                           or NOTICE to limit who receives the
+                                                           message to only those with a certain
+                                                           level of access. This token will
+                                                           replace the WALLCHOPS token.
+
+EXCEPTS       none            none                         Indicates that channel ban exceptions
+                                                           (+e) are supported by the server.
+
+INVEX         none            none                         Indicates that channel invite
+                                                           exceptions (+I) are supported by
+                                                           the server.
+
+MAXLIST       mode:num,...    b:60,e:60,I:60               Specifies the maximum number of 
+                                                           entries that may be added to a 
+                                                           particular mode list (type A modes).
+                                                           This token replaces MAXBANS.
+
+CHANLIMIT     pfx:num,...     #:10                         Specifies the maximum number of 
+                                                           channels with the specified prefix
+                                                           that a user may join at one time.
+                                                           This token will replace MAXCHANNELS.
+
+CHANNELLEN    number          32                           Provides the maximum length of a
+                                                           channel name that a user can create.
+
+NAMESX        none            none                         Indicates that extended /NAMES info
+                                                           is available on this server. If the
+                                                           client sends "PROTOCTL NAMESX" then
+                                                           the server will, from then on, send
+                                                           all channel rights in a NAMES reply
+                                                           instead of only the highest right
+                                                           (eg: @+Person instead of @Person).

doc/technical/base64.txt

@@ -0,0 +1,11 @@
+base64 Documentation (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
+(As of Unreal3.2-beta11)
+
+The base64 system used by Unreal is defined as follows:
+
+         0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T
+         U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x
+         y z { }
+
+These numbers are translated to and from their decimal equivilents of 0-64 in order to
+provide a shorter way of expressing a number.

doc/technical/protoctl.txt

@@ -0,0 +1,141 @@
+PROTOCTL Documentation (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
+(As of Unreal3.2-beta11)
+
+The PROTOCTL command allows servers to negotiate protocol specific features when a link
+occurs. The PROTOCTL command is sent during a link before the SERVER and PASS commands. The
+command contains tokens that list what protocols the server supports.
+
+PROTOCTL SPACE <token> SPACE ...
+
+UnrealIRCd supports several tokens that add additional protocol support to the server. A
+list of all supported tokens and their function listed below.
+
+Token         Description
+------------------------------------------------------------------------------------------------
+NOQUIT        Informs the server it need not send out a QUIT for each user on the server
+              when an SQUIT occurs. Instead an SQUIT is sent out for each server that has
+              been disconnected from the network and the server can then assume all users
+              that were on those servers have left as well.
+
+TOKEN         Informs the server that it may send "tokenized commands", that is a shortened
+              name for the commands. This allows the server to save bandwidth by sending
+              less information to other servers. See doc/technical/token.txt for a list of
+              all commands and their respective token.
+
+NICKv2        Notifies the server that it supports the extended NICK command (version 2),
+              this command allows the server to specify more information in the NICK
+              command rather than having to send out a NICK, MODE, and CHGHOST
+              command. This token only affects a NICK command introducing a client, not one
+              in which a client is changing his/her nickname. The format for a NICKv2 NICK
+              command is:
+
+              :<sender> NICK <nickname> <hops> <TS> <username> <host> <server>
+                        <servicestamp> <umodes> <vhost> :<info>
+
+              If the user has no modes set the umodes parameter is a +, if the user has no
+              vhost set the vhost parameter is an *.
+
+SJOIN         SJOIN is an obsolete token that is only supported for backwards
+              compatibility. It should not be used.
+
+SJOIN2        SJOIN2 is an obsolete token that is only supported for backwards
+              compatibility. It should not be used.
+
+UMODE2        Informs the server that support for the UMODE2 command exists. The UMODE2
+              command is a shortened form of the MODE command but only applys to
+              usermodes. In a normal MODE command, when applied to usermodes, the nickname
+              is specified two times. Both as the sender prefix and as the first parameter,
+              UMODE2 solves this problem in order to save bandwidth, the format for UMODE2
+              is as follows:
+
+              :<sender> UMODE2 <modes>
+
+VL            Notifies the server that Vline information is included in the info field of
+              the SERVER command. Vline information consists of the protocol number of the
+              server and compiletime options supported. This allows denial of a server
+              based on version and/or features supported. The VL information is passed only
+              during connection, it is not filtered to other servers on the network, only
+              the uplink. The syntax for a VL supporting SERVER command is:
+
+              SERVER <servername> <hops> :U<protocol>-<versionflags> <info>
+
+              If an * appears for either protocol and/or versionflags no Vline checking is
+              done, this is often used by services programs where support for all versions
+              is desired. See doc/technical/vl.txt for a list of version flags and protocol
+              numbers. 
+
+SJ3           Notifies the server that the SJOIN command with SJ3 syntax is
+              supported. SJOIN is used at link time to inform servers about the channels on
+              the server. It is a combination of the JOIN commands, and MODE commands
+              associated with distribution of channel information. The syntax for the SJOIN
+              command with SJ3 syntax is:
+
+              :<sender> SJOIN <ts> <chname> [<modes>] [<mode para> ...] :<[[*~@%+]member] ...
+                        [&"ban/except] ...>
+
+              The ts parameter is the time at which the channel, chname, was created. The
+              modes parameter is only included if modes are set, if not modes and mode para
+              are excluded. If modes exists and modes requiring parameters (+klLf) are set,
+              one mode para parameter is included for each value. The last parameter
+              specifies a list of channel members and the channel ban and except list. The
+              members are listed with the prefixes they have. * = +q, ~ = +a, @ = +o, % =
+              +h, + = +v. If no prefix is specified for the member then the user is a
+              normal user. The & prefix is used to denote a +b, and the " prefix denotes a
+              +e. It is important that if a & or " is encountered that you do not continue
+              to check that entry for other prefixes as a ban/except may contain *~@
+              characters which will intefere with prefixes.
+
+              When synching, if ts lower than the local value, the information supplied by
+              the remote server replaces the local (ie remove local +ohv that are not
+              recorded on the remote server). The opposite is true when the ts is
+              higher. Bans/excepts do not apply to the previous rule. If the ts is the
+              same, information is merged therefore the modes from both servers are added 
+              together. If +l is set and both servers have different values, the highest is
+              choosen, for +f the highest of each param, N:M is chosen, and if one server
+              has * set, then it is included. For +k and +L the "highest" in a string 
+              comparison is used.
+
+NS            When specified informs the server that numeric server names are
+              supported. Numeric server names are a base64 number that is associated with
+              each server. This number is used as a shorthand name for the server. It is
+              used in the server parameter of the NICK command and can also be used in the
+              prefix for a message. In the event that the prefix is an NS, rather than
+              using :<sender>, the format is @<ns> the ns should be translated into the
+              server name so that the message can be processed. The format for a SERVER
+              message (at sync time) that supports NS is:
+
+              SERVER <servername> <hops> :U<protocol>-<versionflags>-<numeric> <info>
+
+              The VL protocol must also be supported. The numeric is passed to all servers
+              on the network through the SERVER command using the syntax:
+
+              :<sender> SERVER <servername> <hops> <numeric> :<info>
+
+              Note: anywhere a :<sender> is expected an @<ns> may be received if the source
+              is a server. See doc/technical/base64.txt for information on the base64
+              system used.
+
+SJB64         This token allows timestamps to be specified in base64 notation to conserve
+              bandwidth. When SJB64 is supported, anywhere a timestamp can appear may be in
+              base64 notation. A base64 timestamp is preceeded by a ! to identify that it
+              is an sjb64 rather than a regular timestamp, if this is the case the
+              characters following the ! represent the timestamp in base64. See
+              doc/technical/base64.txt for information on the base64 system used. 
+              
+ZIP           If both servers have this set then the link will be (zlib) compressed after
+              the SERVER message. If one of the servers does not have ZIP in his PROTOCTL
+              message then the link stays uncompressed.
+
+TKLEXT        This allows 10 instead of 8 parameters in TKL's for spamfilter, see s_kline.c
+              function m_tkl for more info on this (added in 3.2RC2).
+
+NICKIP        This token indicates that a (standard) base64 encoded IP address is included
+              in the NICK command. The IP is in binary network byte order formated and
+              encoded using the standard base64 algorithm. '*' is used if no IP is available.
+
+NICKCHARS     This specifies a list of language characters that are allowed in nicks.
+              USMARC codes are used, with a suffix if needed. See src/charsys.c for the full
+              list (ctrl+f, static LangList) of possible languages (2nd column).
+              The items in the list sent as NICKCHARS=.. must always be sorted.
+              If a server sends NICKCHARS= and if the remote parameters do not match the
+              charsets in use locally, then the server link is rejected.

doc/technical/serverprotocol.html

@@ -0,0 +1,465 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!-- $Id$ -->
+<html>
+	<head>
+		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+		<title>Unreal 3.2 Protocol Documentation</title>
+	</head>
+	<body>
+		<h1 style="text-align: center;">Unreal 3.2 Protocol Documentation</h1>
+		<h3 style="text-align: center;">Last update: 29 November 2006</h3>
+		<h1>Table of Contents</h1>
+		<p><a href="#S1">1 Introduction</a></p>
+		<p><a href="#S2">2 Server Negotiation</a></p>
+		<blockquote><p><a href="#S2_1">2.1 PASS - Connection Password</a></p></blockquote>
+		<blockquote><p><a href="#S2_2">2.2 PROTOCTL - Server Protocol Negotiation</a></p></blockquote>
+		<blockquote><p><a href="#S2_3">2.3 SERVER - Server Negotiation</a></p></blockquote>
+		<blockquote><p><a href="#S2_4">2.4 EOS - End Of Synch</a></p></blockquote>
+		<blockquote><p><a href="#S2_5">2.5 NETINFO - Network Information</a></p></blockquote>
+		<p><a href="#S3">3 User Operations</a></p>
+		<blockquote><p><a href="#S3_1">3.1 NICK - User Introduction and Nick Change</a></p></blockquote>
+		<blockquote><blockquote><p><a href="#S3_1_1">3.1.1 Nick Collisions</a></p></blockquote></blockquote>
+		<blockquote><p><a href="#S3_2">3.2 MODE, UMODE2 - User Mode Change</a></p></blockquote>
+		<blockquote><p><a href="#S3_3">3.3 QUIT - User Disconnect</a></p></blockquote>
+		<blockquote><p><a href="#S3_4">3.4 KILL - Force Disconnect</a></p></blockquote>
+		<blockquote><p><a href="#S3_5">3.5 SETHOST/CHGHOST - Change virtual host</a></p></blockquote>
+		<blockquote><p><a href="#S3_6">3.6 SETIDENT/CHGIDENT - Change a user's username</a></p></blockquote>
+		<blockquote><p><a href="#S3_7">3.7 SETNAME/CHGNAME - Change a user's realname</a></p></blockquote>
+		<blockquote><p><a href="#S3_8">3.8 WHOIS - User Information</a></p></blockquote>
+		<p><a href="#S1">4 Server Operations</a></p>
+		<blockquote><p><a href="#S4_1">4.1 SERVER - Server Introduction</a></p></blockquote>
+		<blockquote><p><a href="#S4_2">4.2 SQUIT - Server Removal</a></p></blockquote>
+		<blockquote><p><a href="#S4_3">4.3 SDESC - Server Description</a></p></blockquote>
+		<blockquote><p><a href="#S4_4">4.4 PING - Live Connection Query</a></p></blockquote>
+		<blockquote><p><a href="#S4_5">4.5 PONG - Live Connection Reply</a></p></blockquote>
+		<blockquote><p><a href="#S4_6">4.6 STATS - Server Stats</a></p></blockquote>
+		<p><a href="#S5">5 Channel Operations</a></p>
+		<blockquote><p><a href="#S5_1">5.1 SJOIN - Channel Burst</a></p></blockquote>
+		<blockquote><p><a href="#S5_2">5.2 JOIN - Channel Join</a></p></blockquote>
+		<blockquote><p><a href="#S5_3">5.3 PART - Channel Part</a></p></blockquote>
+		<blockquote><p><a href="#S5_4">5.4 KICK - Channel Kick</a></p></blockquote>
+		<blockquote><p><a href="#S5_5">5.5 MODE - Channel Mode</a></p></blockquote>
+		<blockquote><p><a href="#S5_6">5.6 INVITE - Invite a user to a channel</a></p></blockquote>
+		<blockquote><p><a href="#S5_7">5.7 SAJOIN - Channel Force Join</a></p></blockquote>
+		<blockquote><p><a href="#S5_8">5.8 SAPART - Channel Force Part</a></p></blockquote>
+		<blockquote><p><a href="#S5_9">5.9 SAMODE - Channel Force Mode</a></p></blockquote>
+		<blockquote><p><a href="#S5_10">5.10 TOPIC - Chanel Topic</a></p></blockquote>
+		<p><a href="#S6">6 Services Commands</a></p>
+		<blockquote><p><a href="#S6_1">6.1 SVSKILL - Force Disconnect by Service</a></p></blockquote>
+		<blockquote><p><a href="#S6_2">6.2 SVSMODE, SVS2MODE - Force User Mode Change</a></p></blockquote>
+		<blockquote><p><a href="#S6_3">6.3 SVSSNO, SVS2SNO - Forced SNomask Change</a></p></blockquote>
+		<blockquote><p><a href="#S6_4">6.4 SVSNICK - Forced Nick Change</a></p></blockquote>
+		<blockquote><p><a href="#S6_5">6.5 SVSJOIN - Forced Join</a></p></blockquote>
+		<blockquote><p><a href="#S6_6">6.6 SVSPART - Forced Part</a></p></blockquote>
+		<blockquote><p><a href="#S6_7">6.7 SVSO - Oper Permissions</a></p></blockquote>
+		<blockquote><p><a href="#S6_8">6.8 SVSNOOP - Oper Lockdown</a></p></blockquote>
+		<blockquote><p><a href="#S6_9">6.9 SVSNLINE - RealName Ban</a></p></blockquote>
+		<blockquote><p><a href="#S6_10">6.10 SVSFLINE - File Ban</a></p></blockquote>
+		<p><a href="#S7">7 Messaging</a></p>
+		<blockquote><p><a href="#S7_1">7.1 PRIVMSG, NOTICE - Simple Message Transmission</a></p></blockquote>
+		<blockquote><p><a href="#S7_2">7.2 SENDUMODE, SMO - Usermode-based Delivery</a></p></blockquote>
+		<blockquote><p><a href="#S7_3">7.3 SENDSNO - SNomask-based Delivery</a></p></blockquote>
+		<blockquote><p><a href="#S7_4">7.4 CHATOPS - IRCop Chat</a></p></blockquote>
+		<blockquote><p><a href="#S7_5">7.5 WALLOPS - Wallop Chat</a></p></blockquote>
+		<blockquote><p><a href="#S7_6">7.6 GLOBOPS - FailOp Chat</a></p></blockquote>
+		<blockquote><p><a href="#S7_7">7.7 ADCHAT - Admin Chat</a></p></blockquote>
+		<blockquote><p><a href="#S7_8">7.8 NACHAT - NetAdmin Chat</a></p></blockquote>
+		<p><a href="#S8">8 Ban Control</a></p>
+		<blockquote><p><a href="#S8_1">8.1 TKL - Master Ban Control</a></p></blockquote>
+		<blockquote><blockquote><p><a href="#S8_1_1">8.1.1 GLINE - Network-wide user@host ban</a></p></blockquote></blockquote>
+		<blockquote><blockquote><p><a href="#S8_1_2">8.1.2 GZLINE - Network-wide IP ban</a></p></blockquote></blockquote>
+		<blockquote><blockquote><p><a href="#S8_1_3">8.1.3 SQLINE, UNSQLINE - Network-wide Nickname ban</a></p></blockquote></blockquote>
+		<blockquote><blockquote><p><a href="#S8_1_4">8.1.4 SPAMFILTER - Message Spam Filtration System</a></p></blockquote></blockquote>
+		<p><a href="#S9">9 Base64 Tables</a></p>
+		<blockquote><p><a href="#S9_1">9.1 Table for SJB64 (NICK and SJOIN).</a></p></blockquote>
+		<blockquote><p><a href="#S9_2">9.2 Table for NICKIP.</a></p></blockquote>
+		<hr/>
+		<h1><a name="S1"></a>1 Introduction</h1>
+		<p>This document describes the UnrealIRCd server-to-server protocol as of protocol 2307 (Unreal 3.2.4).</p>
+		<h2>A word about clocks.</h2>
+		<p>Unreal is very time-dependant. Users and channels, for example, are timestamped, and if server clocks are not synchronized properly, things can go very wrong very fast. See <a href="http://vulnscan.org/UnrealIrcd/faq/#67">http://vulnscan.org/UnrealIrcd/faq/#67</a> for more information on this. Note that there is a slight difference between server time and what is actually reported by the UNIX date command or by the C time() function. Unreal can apply an offset to the real time to create the server time, allowing servers to be virtually synchronized when synchronizing the real clocks is not possible (such as on shell servers).
+			I should make it quite clear that GMT time is used for everything. To be specific, timestamps in unreal are 32-bit integer values (actually, however many bits the time_t type is, which is 32 on 32-bit systems such as x86). This integer value is the number of seconds that have elapsed since Midnight January 1, 1970 GMT (can be referred to as Epoch time in the UNIX world). This means that timezones are no problem, nor is daylight savings time (or whatever your country of choice calls it).</p>
+		<hr/>
+		<h1><a name="S2"></a>2 Server Negotiation</h1>
+		<p>The first step to establish a server-to-server communication is to negotiate the connection as a server. Negotiation is done using standard IRC commands - no PROTOCTL options are in force until the link is established. The first step is to open a TCP/IP connection to the target server. The target port must be one described by a listen {} block in the remote server's configuration, and that listen block must not have the clientsonly option. After the connection is open, you will be treated as any other connection and be greeted with the "Looking up your hostname..." and "Checking identd..." notices as you would for a client. As these are NOTICE messages and your session as a server isn't established, they should simply be ignored. Use the commands below to introduce a server connection.</p>
+		<h2><a name="S2_1"></a>2.1 PASS - Connection Password</h2>
+		<p><b>Syntax:</b> <tt>PASS :<i>link password</i></tt></p>
+		<p>The PASS command is used to transmit the password required for a server link. It must match the password specified in the remote server's link::password-receive (which can be crypted), otherwise the link will be rejected. This should be the first message sent.</p>
+		<h2><a name="S2_2"></a>2.2 PROTOCTL - Server Protocol Negotiation</h2>
+		<p><b>Syntax:</b> <tt>PROTOCTL <i>protocol options</i></tt></p>
+		<p>The PROTOCTL command sets several protocol options. The tokens supported are listed below.</p>
+		<ul>
+			<li>NOQUIT : When a netsplit occurs, only send a SQUIT message for each server lost. This server will assume that clients on these servers were also lost and will send the appropriate QUIT messages to local clients and to any non-NOQUIT servers.</li>
+			<li>TOKEN : Use tokenized commands. Tokens are case-sensitive, shortened versions of command names. Tokens will be usually one or two characters.</li>
+			<li>NICKv2 : Use extended NICK message for introducing users. See the NICK command for information about this.</li>
+			<li>VHP : When introducing a user, send his cloaked host as if it were a vhost. Usually used for services to avoid having duplicate code.</li>
+			<li>SJOIN : Supports SJOIN version 1 which is no longer in use. Use with SJ3.</li>
+			<li>SJOIN2 : Supports SJOIN version 2 which is no longer in use. Use with SJ3.</li>
+			<li>UMODE2 : Supports the UMODE2 command, which is a shortened version of MODE for usermode changes.</li>
+			<li>VL : Supports V:Line information. Extends the SERVER message to include version information used in deny version{} blocks. Note that this is assumed - unreal will always send its own version information.</li>
+			<li>SJ3 : Supports SJOIN version 3.</li>
+			<li>NS : Supports server numerics which provides a shorthand for server names. In any circumstance where a :server.name is permitted (the server is the message's real source), @servernumeric may be used instead. In addition, the server.name parameter in the NICK message may be simply the server's numeric. Requires VL support.</li>
+			<li>SJB64 : Timestamps in NICK and SJOIN are expressed in base64 rather than base10.</li>
+			<li>TKLEXT : Supports exntended TKL messages for spamfilter support.</li>
+			<li>NICKIP : Adds an IP parameter to the NICK message, which is the base64 encoding of the user's ip address (in network byte order). Requires NICKv2.</li>
+			<li>NICKCHARS : Indicates the set of enabled nickchar options (see the regular documention for info about this).</li>
+			<li>CHANMODES : (Not required to be sent) This is the same as the CHANMODES value in the 005 for client connections. Useful for autodetecting things like what modes are valid for ChanServ MLOCK, for example.</li>
+			<li>CLK : Supports an extra field in NICK for sending the cloaked host (not vhost).</li>
+		</ul>
+		<p>The syntax examples here follow the conventions for TOKEN and also NS in cases of server-only messages.</p>
+		<h2><a name="S2_3"></a>2.3 SERVER - Server Negotiation</h2>
+		<p><b>Note:</b> This message is also used for introducing additional servers, the format of this message in those cases is described later.</p>
+		<p><b>Syntax (normal):</b> <tt>SERVER <i>server.name</i> 1 :<i>server description</i></tt></p>
+		<p><b>Syntax (with VL):</b> <tt>SERVER <i>server.name</i> 1 :U<i>protocolversion</i>-<i>protocolflags</i> <i>server description</i></tt></p>
+		<p><b>Syntax (with VL and NS):</b> <tt>SERVER <i>server.name</i> 1 :U<i>protocolversion</i>-<i>protocolflags</i>-<i>servernumeric</i> <i>server description</i></tt></p>
+		<p>The literal 1 in the parameter list is the hopcount parameter. Since you are a direct link, your own hopcount will be 1.</p>
+		<p>The server.name is the same as that in the remote server's link:: block. When received from unreal servers, this will be the value of that server's me::name. The protocol version is the numeric protocol version (2306 for example), and the protocol flags are the server's compilation flags (described below). These two fields are checked against the deny version {} blocks in the remote server's configuration. A value of 0 for either field prevents deny version{} checking for that field. The server description can be anything. When received from unreal servers, it'll be the value of me::description.</p>
+		<p>The following version numbers have been used previously:</p>
+		<ul>
+			<li>2309 - Unreal 3.2.6</li>
+			<li>2308 - Unreal 3.2.5</li>
+			<li>2307 - Unreal 3.2.4</li>
+			<li>2306 - Unreal 3.2.3</li>
+			<li>2305 - Unreal 3.2.2</li>
+			<li>2304 - Unreal 3.2.1</li>
+			<li>2303 - Unreal 3.2beta* through 3.2 Release</li>
+			<li>2302 - Unreal 3.1.1 through 3.1.4</li>
+			<li>2301 - Unreal 3.1 Release</li>
+			<li>2300 - Unreal 3.0 Release</li>
+		</ul>
+		<p>The compile flags as specified in protocol flags are:</p>
+		<ul>
+			<li>c : Server is chrooted (#define CHROOTDIR).</li>
+			<li>C : Server has command line config (-f option) enabled (#define CMDLINE_CONFIG).</li>
+			<li>D : Server is in debugmode (#define DEBUGMODE).</li>
+			<li>F : Using filedescriptor lists.</li>
+			<li>h : Server is compiled with hub support (#define HUB or answer "Hub" to relevant ./Config prompt).</li>
+			<li>i : Server shows invisible users in /TRACE.</li>
+			<li>n : NOSPOOF (pingcookies) is enabled (#define NOSPOOF or answer "Yes" to relevant ./Config prompt).</li>
+			<li>V : Server is using valloc().</li>
+			<li>W : Windows IRCd.</li>
+			<li>Y : Syslog logging enabled.</li>
+			<li>6 : Server has IPv6 support (#define INET6 or answer "yes" to relevant ./Config prompt).</li>
+			<li>X : Server has badword stripping (user and channel modes +G) (#define STRIPBADWORDS).</li>
+			<li>P : Server is using poll().</li>
+			<li>e : Server has SSL Support (#define USE_SSL or answer "yes" (and have ssl libraries installed) to relevant ./Config prompt).</li>
+			<li>O : Server has OperOverride enabled (#undef NO_OPEROVERRIDE or answer "no" to relevant ./Config prompt).</li>
+			<li>o : Server has disabled Oper verify (#undef OPEROVERRIDE_VERIFY or answer "no" to relevant ./Config prompt).</li>
+			<li>Z : Server has ziplink support (#define ZIP_LINKS or answer "yes" to relevant ./Config prompt AND have the zlib dev libraries).</li>
+			<li>E : Server has extended channel mode support.</li>
+			<li>3 : 3rd party modules are loaded or some system libraries are wonky.</li>
+			<li>m : Private message handling is 'tainted' (one or modules registered a USERMSG hook).</li>
+			<li>M : Channel message handling is 'tainted' (one or modules registered a CHANMSG hook).</li>
+			<li>Additional Version flags can be added by 3rd-party modules.</li>
+		</ul>
+		<h2><a name="S2_4"></a>2.4 EOS - End Of Synch (TOKEN: ES)</h2>
+		<p><b>Syntax:</b> ES</p>
+		<p>Marks the end of the synching process. This is really optional, but it might be a good idea to send it anyway when you really are done synching. Once you send this, unreal will announce &quot;Client connecting&quot; or &quot;Client exiting&quot; notices (to those with snomask +F) for users (unless your server is U:Lined), and joins will be counted toward channel flood controls (chanmode +f).</p>
+		<p>Sending EOS only marks your server as synched, but does not do so for servers behind you. EOS would need to be sent on those servers' behalf as well.</p>
+		<h2><a name="S2_5"></a>2.5 NETINFO - Network Information (TOKEN: AO)</h2>
+		<p><b>Syntax:</b> AO <i>maxglobal</i> <i>currenttime</i> <i>protocolversion</i> <i>cloakhash</i> 0 0 0 :<i>networkname</i></p>
+		<p>This tells the other server your current network configuration. The max global is the highest number of concurrent users network-wide that this server has seen. The current time is a timestamp value. Protocolversion is the same as that in the SERVER command. Cloakhash is a hash representing the configured cloak keys. It may be a * if you are implementing services. The network name is that specified in set::network-name. The cloak-prefix is currently not sent here (and thus unreal won't generate warning for mismatching cloak prefixes, but they should be the same anyway).</p>
+		<p>It is NETINFO, not EOS, that triggers the &quot;Link bla bla bla is now synched&quot; notices, but NETINFO does not imply synching is actually complete (see EOS).</p>
+		<hr/>
+		<h1><a name="S3"></a>3 User Operations</h1>
+		<p>One important function of servers is it must notify all other servers about all of the users behind it. These commands represent the operations that can result in the change of a user's global state.</p>
+		<h2><a name="S3_1"></a>3.1 NICK - User Introduction and Nick Change (TOKEN: &amp;)</h2>
+		<p><b>Syntax (nick change):</b> <tt>:<i>oldnick</i> &amp; <i>newnick</i> :<i>timestamp</i></tt></p>
+		<p>This format of the NICK message indicates an existing user is changing his or her nickname. If a collision occurs, see the section on Nick Collisions below. The timestamp is the new nickname's timestamp.</p>
+		<p><b>Syntax (normal):</b> <tt>&amp; <i>nick</i> <i>hopcount</i> <i>timestamp</i>	<i>username</i> <i>hostname</i> <i>server</i> <i>servicestamp</i> :<i>realname</i></tt></p>
+		<p><b>Syntax (NICKv2):</b> <tt>&amp; <i>nick</i> <i>hopcount</i> <i>timestamp</i>	<i>username</i> <i>hostname</i> <i>server</i> <i>servicestamp</i> <i>+usermodes</i> <i>virtualhost</i> :<i>realname</i></tt></p>
+		<p><b>Syntax (NICKv2+CLK):</b> <tt>&amp; <i>nick</i> <i>hopcount</i> <i>timestamp</i>	<i>username</i> <i>hostname</i> <i>server</i> <i>servicestamp</i> <i>+usermodes</i> <i>virtualhost</i> <i>cloakhost</i> :<i>realname</i></tt>
+		<p><b>Syntax (NICKv2+NICKIP):</b> <tt>&amp; <i>nick</i> <i>hopcount</i> <i>timestamp</i> <i>username</i> <i>hostname</i> <i>server</i> <i>servicestamp</i> <i>+usermodes</i> <i>virtualhost</i> <i>nickipaddr</i> :<i>realname</i></tt></p>
+		<p><b>Syntax (NICKv2+NICKIP+CLK):</b> <tt>&amp; <i>nick</i> <i>hopcount</i> <i>timestamp</i>	<i>username</i> <i>hostname</i> <i>server</i> <i>servicestamp</i> <i>+usermodes</i> <i>virtualhost</i> <i>cloakhost</i> <i>nickipaddr</i> :<i>realname</i></tt>
+		<p><b>Note:</b> Because each server normally does its own cloak generation, Unreal does not expect to receive NICK messages with the CLK info, so do not send it. It will send this info to a server it has received a PROTOCTL CLK from however.</p>
+		<p>This format of the NICK message introduces a new user to the network. If PROTOCTL VHP is enabled, the user's cloaked host is put in the virtualhost field, otherwise it'll be * unless the user is +t. With the addition of CLK, VHP is no longer necessary for determining the cloak host.</p>
+		<h3><a name="S3_1_1"></a>3.1.1 Nick Collisions</h3>
+		<p>A nick collision occurs when a server receives a NICK message (or &amp; token) introducing a user that the server already sees on the network. When a collision occurs, one or both of the colliding clients must be disconnected. The timestamp is examined to determine which client loses. The client with the earlier timestamp remains. If both clients have equal timestamps, both are removed. Currently, Unreal handles NICK collisions both passively and agressively:</p>
+		<ul>
+			<li><b>Aggressive Handling:</b> The server actively sends a KILL message back across the link to terminate that end's client.</li>
+			<li><b>Passive Handling:</b> Upon receipt of a NICK message that should "win", the server simply silently exits it's own client.</li>
+		</ul>
+		<h2><a name="S3_2"></a>3.2 MODE, UMODE2 - User Mode Change (TOKEN: G or |)</h2>
+		<p><b>Syntax (MODE):</b> <tt>:<i>user</i> G <i>user</i> <i>modechange</i></tt></p>
+		<p><b>Syntax (UMODE2):</b> <tt>:<i>user</i> | <i>modechange</i></tt></p>
+		<p>This indicates a usermode change. The modechange can consist of zero or more strings of characters, each prefixed with either a + or -; the only delimiter between them being said + or -. If no + or - is at the beginning of the mode string, a + should be implied.</p>
+		<p>Some user modes are never sent between servers. Specifically, usermode +s and +O are not sent between servers. Modules can define additional usermodes that also might not be sent between servers. The UMODE2 saves bandwidth by not including the redundant target field for usermode changes, so use it when possible.</p>
+		<h2><a name="S3_3"></a>3.3 QUIT - User Disconnect (TOKEN: ,)</h2>
+		<p><b>Syntax:</b> <tt>:<i>user</i> , :<i>reason</i></tt></p>
+		<p>This command indicates that a user has disconnected. The reason field is filled in with the reason the user disconnected, which will be any of: quit message provided by the user in a /quit command, kill message for local operator kills, "Client exited" if the user does a brutal quit (clean (by TCP's definition) disconnect without sending a QUIT message), or a socket error message if present.</p>
+		<p>The QUIT message must NOT be prefixed when passing on to other servers. Only local user quit messages are affected by set::prefix-quit.</p>
+		<h2><a name="S3_4"></a>3.4 KILL - Force Disconnect (TOKEN: .)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> . <i>target</i> :<i>killpath</i>!<i>source</i> (<i>reason</i>)</tt></p>
+		<p>Used to indicate that an operator has used KILL on a user not on the same server. Anything beyond the last ! in the kill path is used as the reason. The source (reason) part is simply a standard used by Unreal. As each server passes on a KILL message, it usually prepends the bottommost part (up to the first .) of it's name followed by a ! character. When unreal receives a KILL from a directly connected irc operator, it will usually add that oper's vhost (or realhost if -x) as the first hop in the kill path, then follow with it's own name as mentioned before if it is passing to another server.</p>
+		<p>A server can also send KILLs on it's own. This is done in cases involving nickname collisions, fake senders, bad direction, and other cases of protocol errors. Usually, in these cases, the server puts it's own name as the source, and also prefixes with <i>bottompart</i>! like for any other ircop on that server. For example: @3 . someone :irc!irc.example.com (Nick collision)</p>
+		<h2><a name="S3_5"></a>3.5 SETHOST/CHGHOST - Change virtual host (TOKEN: AA or AL)</h2>
+		<p><b>Syntax (SETHOST):</b> <tt>:<i>source</i> AA <i>newvhost</i></tt></p>
+		<p><b>Syntax (CHGHOST):</b> <tt>:<i>source</i> AL <i>target</i> <i>newvhost</i></tt></p>
+		<p>Indicates the change of a user's virtual host. Currently, servers are expected to assume UMODE2 +xt on the target user in both commands. (In the case of SETHOST, the target is the sender.) Servers using PROTOCTL VHP will receive the cloaked host in a SETHOST message when a user activates his cloaked host. A server can also send CHGHOST (from one of it's opered clients) to change a user's hostname. This is generally used by HostServ implementations. To disable a cloaked host, use CHGHOST to set the user's virtual host equal to his real host, or use SVSMODE -xt, but the latter requires services.</p>
+		<h2><a name="S3_6"></a>3.6 SETIDENT/CHGIDENT - Change a user's username (TOKEN: AD or AZ)</h2>
+		<p><b>Syntax (SETIDENT):</b> <tt>:<i>source</i> AD <i>newusername</i></tt></p>
+		<p><b>Syntax (CHGIDENT):</b> <tt>:<i>source</i> AZ <i>target</i> <i>newusername</i></tt></p>
+		<p>Indicates the change of a user's username. No usermode change is associated with this. Unreal does not use a distinguished virtual username, so servers should only keep the original username (from the NICK message) if they intend to allow the user to reset the original username. Servers can use CHGIDENT to change a user's username.</p>
+		<h2><a name="S3_7"></a>3.7 SETNAME/CHGNAME - Change a user's realname (TOKEN: AE or BK)</h2>
+		<p><b>Syntax (SETNAME):</b> <tt>:<i>source</i> AE :<i>newrealname</i></tt></p>
+		<p><b>Syntax (CHGNAME):</b> <tt>:<i>source</i> BK <i>target</i> :<i>newrealname</i></tt></p>
+		<p>Indicates the change of a user's realname. No usermode change is associated with this. Unreal does not use a distinguished virtual realname, so servers should only keep the original realname (from the NICK message) if they intend to allow the user to reset the original realname. Servers can use CHGNAME to change a user's username. Note that servers must NOT check that the sender be an IRCop in SETNAME - normal users are permitted to use SETNAME.</p>
+		<h2><a name="#S3_8"></a>3.8 WHOIS - User Information (TOKEN: #)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> # [<i>from-server</i> ]<i>nick</i></tt></p>
+		<p>Requests the information on a user. This works exactly like the user /whois command - in fact, the source parameter must be a user, or the command will do nothing. <i>from-server</i> is the server to request the information from; if a server recives a WHOIS message without this parameter, it should return its own information on the user, otherwise it should pass the message to the given server. Note that <i>from-server</i> may name a user instead of a server (such as when a user uses /whois nick nick), in which case the the nick should be interpreted as naming the server that user is on. <i>nick</i> may be several users seperated by commas, but may not contain wildcards.</p>
+		<p>The reply to a WHOIS message uses the same numeric replies as the user command.</p>
+		<hr/>
+		<h1><a name="S4"></a>4 Server Operations</h1>
+		<p>This is different from server negotiation. Negotiation is when you are first connecting. Server introduction is used for introducing additional servers behind an existing server (aka hubbing). Hubbing is limited as specified by the hub, leaf, and leafdepth parameters in the link block and attempted violation of a hub restriction results in termination of the link. If no hub or leaf directive is given your server is a leaf by default, so any introduction of any server behind you would be an automatic drop. U:Lines don't matter here; services must be configured as a hub in the link block. The reason is U:Line is a permission rule, but hub privilege is a network structure rule.</p>
+		<h2><a name="S4_1"></a>4.1 SERVER - Server Introduction (TOKEN: ')</h2>
+		<p><b>Note: This command is also used for negotiation. Be warned that the token for this command is NOT VALID at that time! See section 2.3 for the syntax for negotiation.</b></p>
+		<p><b>Syntax (without PROTOCTL NS):</b> <tt>:<i>source</i> SERVER <i>new.server</i> <i>hopcount</i> :<i>description</i></tt></p>
+		<p><b>Syntax (with PROTOCTL NS):</b> <tt>@<i>sourcenumeric</i> SERVER <i>new.server</i> <i>hopcount</i> <i>numeric</i> :<i>description</i></tt></p>
+		<p>The command indicates that the server named new.server is being introduced by the source (the source is the server which new.server is directly linked to). The hopcount will be the number of links the receiving server would have to cross to reach new.server. In other words, new.server introduced itself with a hopcount of 1, and as the SERVER message is passed along, hopcount is incremented.</p>
+		<p>As an example, a services server faking a SERVER message for JUPE functionality would use a hopcount of 2.</p>
+		<h2><a name="S4_2"></a>4.2 SQUIT - Server Removal (TOKEN: -)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> SQUIT <i>server.name</i> <i>:reason</i></tt></p>
+		<p>From an IRCop or when server.name is not behind the source, this command requests the removal of the specified server.name. The command in this case is treated very much like KILL in the respect that the message is broadcasted to all servers, except server.name and any servers behind it. When the SQUIT reaches server.name's uplink, that server closes the link to server.name (which would then generate it's own SQUIT on behalf of it's uplink for the servers behind it).</p>
+		<p>A server can also use SQUIT in the same manner as QUIT to note the removal of a server behind it, or that it itself is quitting. In the former case, server.name is behind source, and the message is forward on to all other servers. In the latter case, source and server.name are equal, the receiving server closes the link and forwards the SQUIT message.</p>
+		<p>Unreal closes a direct link by simply sending an ERROR message and then closing the TCP connection. This typically causes the other end to generate an SQUIT bearing the message "Client exited" or similar, however, the ERROR will usually cause the server to send a message to all IRCops.</p>
+		<h2><a name="S4_3"></a>4.3 SDESC - Server Description (TOKEN: AG)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> AG :<i>newdesc</i></tt></p>
+		<p>The server to which source is connected to should have it's description updated to newdesc. This does NOT include the VL inforamtion.</p>
+		<h2><a name="S4_4">4.4 PING - Live Connection Query (TOKEN: 8)</a></h2>
+		<p><b>Syntax:</b> <tt>8 <i>source</i>[ :<i>destination</i>]</tt></p>
+		<p>Used to check if a connection is still live if it has been &quot;quiet&quot; for a certain amount of time. Typically, unreal will send PING requests at intervals determined by the class::pingfreq setting. PINGs originating from the direct uplink will use the token, but it seems PINGs originating from a distant server will not.</p>
+		<p>The response to a PING is sent with the <a href="#S4_5">PONG</a> command.</p>
+		<p>When receiving a two-parameter PING, the second parameter is the target. If the target isn't you, you can either reply on behalf of that target (using its name instead of yours), or if there is a real connection representing the target, forward the PING to the target.</p>
+		<h2><a name="S4_5">4.5 PONG - Live Connection Reply (TOKEN: 9)</a></h2>
+		<p><b>Syntax:</b> <tt>9 <i>source</i>[ :<i>destination</i>]</tt></p>
+		<p>Used to respond to a <a href="#S4_4">PING</a> query.</p>
+		<p><b>Responding to a ping:</b> Once a PING is received, you usually have an amount of time to respond equal to your class::pingfreq. The correct response will always have two parameters. If you received one parameter, then the received parameter becomes the second parameter of your response, and the first parameter is your server name. If you received two parameters, the response returns both parameters in reverse order.</p>
+		<p>For example, the response to <tt>8 uplink.server</tt> is <tt>9 my.name uplink.server</tt>, while the response to <tt>PING distant.server your.server</tt> is <tt>9 your.server distant.server</tt>. Unreal typically includes a : prior to the last parameter. This isn't required if that parameter contains no spaces, but it is especially important to not include the colon when reversing the parameters, or else Unreal mistake it for a single-parameter PONG.
+		<p>If a two-parameter PONG is received, the second parameter names the target. If the target is not you, and a real connection represents that target, you should forward the PONG message via that connection.</p>
+		<h2><a name="#S4_6"></a>4.6 STATS - Server Stats (TOKEN: 2)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> 2 [<i>type</i> [<i>server</i>] [<i>extended-params</i>]]</tt></p>
+		<p>Requests statistics or configuration information from a server. This command is used to transport cross-server STATS requests from users (eg: /stats o other.server), and should only be sent from a user (not a server). With no parameters, this will cause unreal to simply dump its help output. <i>type</i> is the type of stats to request, <i>server</i> names a server (or a user on that server) to request stats from, and <i>extended-params</i> is used to filter output from STATS G, etc. When received, it is up to the receiver to determine what stats to support and how to reply, but generally numeric replies are used. For the list of unreal's stats types, type /stats in a client for the helptext dump.</p>
+		<p><b>Note:</b> Stats set as oper-only (see set::oper-only-stats) will be refused from a server. In this case, it will be necessary to send the stats request from a psuedo-oper (such as a services agent, etc) for services/stats/etc.</p>
+		<hr/>
+		<h1><a name="S5"></a>5 Channel Operations</h1>
+		<p>These commands deal with the state of channels across the network. Unreal only supports Network Channels, where the first character is a # character.</p>
+		<h2><a name="S5_1"></a>5.1 SJOIN - Channel Burst (TOKEN: ~)</h2>
+		<p><b>Syntax:</b> <tt>@<i>servernumeric</i> ~ <i>timestamp</i> <i>channel</i> +<i>modes</i>[ <i>modeparams</i>] :<i>memberlist</i> <i>&amp;ban</i> <i>"exempt</i> <i>'invex</i></tt></p>
+		<p>Timestamp is the channel timestamp and can be !b64 as defined by PROTOCTL SJB64. Modes should only include those in the last three mode sets listed in CHANMODES. Modeparams is one parameter for each mode character that requires one. Memberlist is a series of users (all of which must at least be behind the server sending the SJOIN), each user is prefixed with one or more characters indicating their status. Owners (+q) are prefixed with *, admins (+a) ~, ops (+o) @, halfops (+h) %, voices (+v) +. Normal users are not prefixed with anything. Ban, ban exception, and invite exception masks are also included, with bans prefixed with &amp;, ban exceptions prefixed with ", and invite exceptions with '. Note that when a &amp;, " or ' is encountered as the first character, further processing of ~, *, @, %, or + characters must not continue because ban, exempt, and invite masks can contain any of those characters. (Plus it's just not right for a ban mask to be marked as a channel admin...)</p>
+		<p>If the channel didn't already exist it is created with the information given in the SJOIN. Otherwise the timestamp is used to determine how the SJOIN information is handled. As a given, all members are joined into the channel, regardless. The mode information (modes, modeparams, memberlist prefixes, bans, exempts, and invites) is subject to the timestamp rules:</p>
+		<ul>
+			<li>If the channel's current timestamp is equal to the timestamp in SJOIN, then the mode information is merged.</li>
+			<li>If the channel's current timestamp is less than the SJOIN timestamp, then the mode information is ignored.</li>
+			<li>If the channel's current timestamp is greater than the SJOIN timestamp, then the channel's existing mode information is cleared (for example, deop, etc all local clients), and the SJOIN mode information is added.</li>
+		</ul>
+		<p>When merging modes, conflicting modes (including +p vs +s, differing +l limits or +k keys, etc) are handled as follows:</p>
+		<ul>
+			<li><b>Private (+p) vs. Secret (+s):</b> Secret (+s) is preferred. Private (+p) is removed. (Note: there is a <a href="http://bugs.unrealircd.org/view.php?id=2391">bug</a> in Unreal versions prior to 3.2.3 in which a desynch will occur in which one side is +p and the other is +s. Update to Unreal 3.2.4 if you have problems with this.)</li>
+			<li><b>Strip Color (+S) vs. Block Color (+c):</b> Block (+c) is preferred. Strip (+S) is removed. (Note: Bug for +p vs. +s in prior unreal versions apply here as well.)</li>
+			<li><b>Channel Limit:</b> Numericly larger limit is preferred (for example, +l 30 versus +l 15 : +l 30 wins).</li>
+			<li><b>Channel Key:</b> &quot;Larger&quot; key (as defined by strcmp) is preferred (for example, +k moo versus +k meow : +k moo wins).</li>
+			<li><b>Channel Link:</b> &quot;Larger&quot; link name (as defined by stricmp - not case sensitive) is preferred (for example, +L #moo versus +L #meow : +L #moo wins, but +L #Meow versus +L #meow : values are equal).</li>
+			<li><b>Flood String:</b> Not really sure on this. I think larger value in each component wins.</li>
+			<li><b>Join-Throttle:</b> Highest of time period wins, if equal, highest of join amount wins (so +j 3:40 beats +j 5:20 but +j 5:20 beats +j 3:20).</li>
+			<li>Parameterized modes in third party modules will define their own conflict resolution formula.</li>
+		</ul>
+		<h2><a name="S5_2"></a>5.2 JOIN - Channel Join (TOKEN: C)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> C <i>#channel</i></tt></p>
+		<p>Indicates a user has joined a channel. Only one channel is sent this way, and the key is not sent even if the user gave one one joining. If the channel parameter is the special "0" case, the server must interpret the message as a PART for all channels the user is on.</p>
+		<h2><a name="S5_3"></a>5.3 PART - Channel Part (TOKEN: D)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> D <i>#channel</i>[ :<i>reason</i></tt>]</p>
+		<p>Indicates a user has left a channel. Only one channel is sent this way. The reason parameter may be left out if no reason was given.</p>
+		<h2><a name="S5_4"></a>5.4 KICK - Channel Kick (TOKEN: H)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> H <i>#channel</i> <i>user</i> :<i>reason</i></tt></p>
+		<p>Orders the forced removal of user from #channel with the given reason. When updating state for this command, it should be the same as if :user PART #channel had been received - the user is removed from #channel's memberlist.</p>
+		<h2><a name="S5_5"></a>5.5 MODE - Channel Mode (TOKEN: G)</h2>
+		<p><b>Note:</b> This is the same command as that used for usermode changes.</p>
+		<p><b>Syntax:</b> <tt>:<i>source</i> G <i>#channel</i> <i>modechange</i> <i>modeparams</i>[ <i>timestamp</i>]</tt></p>
+		<p>Changes the specified modes on the given channel. If the source is a server and the last parameter is numeric, it is interpreted as timestamp (although it can also be consumed as a parameter for modes. For example: :server.name MODE #channel +l 4 &lt;-- 4 will be a timestamp and the +l parameter). When a mode change is timestamped in this way, the mode is treated as it is with SJOIN: the MODE message is ignored if the timestamp is greater than the channel timestamp. (If the timestamp is equal, the mode is simply added replacing any conflicting modes already in place.)</p>
+		<p>A services implementation can easily clear all entries in a list mode such as bans with SVSMODE (see below).</p>
+		<h2><a name="S5_6"></a>5.6 INVITE - Invite a user to a channel (TOKEN: *)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> * <i>target</i> <i>#channel</i></tt></p>
+		<p>Sends to target an invitation to join #channel. If the source is a channel operator on #channel, or a U:Lined server, the invitation grants the user the temporary ability to join the channel regardless of any bans or some restricting channel modes (not +O or +A).</p>
+		<h2><a name="S5_7"></a>5.7 SAJOIN - Channel Force Join (TOKEN: AX)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> AX <i>targetuser</i> <i>#channel</i></tt></p>
+		<p>This requests the forced join of targetuser to #channel. This type of forced join overrides bans, and most modes. The server to which targetuser is connected to must actually acknowledge the join for it to occur. Service implementations may ignore this command, as they would only ever receive it if an SAJOIN was targeted at a service client, in which case it should be ignored...</p>
+		<h2><a name="S5_8"></a>5.8 SAPART - Channel Force Part (TOKEN: AY)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> AY <i>targetuser</i> <i>#channel</i>[ :<i>reason</i>]</tt></p>
+		<p>This requests the forced part of targetuser from #channel. This is slightly different from a KICK in that the user's removal is announced with PART. The server to which targetuser is connected to must actually acknowledge the part for it to occur. Service implementations may ignore this command, as they would only ever receive it if an SAPART was targeted at a service client, in which case it should be ignored...</p>
+		<p>The reason field is optional. If provided the acknowledging PART message should prefix the message with &quot;SAPart:&quot;.</p>
+		<h2><a name="S5_9"></a>5.9 SAMODE - Channel Force Mode (TOKEN: o)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> o <i>#channel</i> <i>modechange</i> <i>modeparams</i></tt></p>
+		<p>This has the same parameters as for MODE. The only difference is that servers probably will never receive this (but is best to document just in case), and that absolutely NO permission checking is done on anything.</p>
+		<h2><a name="S5_10"></a>5.10 TOPIC - Channel Topic (TOKEN: ) )</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> ) <i>#channel</i> <i>nick</i> <i>timestamp</i> :<i>topic</i></tt></p>
+		<p>Changes the channel topic information. This format is used when synching, as well as when a topic is changed normally. Nick is the user who changed the topic (depending on compile options, it can be just nick or a full nick!user@host), timestamp is when the change occured, and topic is the new topic text. Normally, only a newer timestamp will actually change the topic, but a U:Lined server can use an older timestamp as well (such as for TOPICLOCK).
+		<hr/>
+		<h1><a name="S6"></a>6 Services Commands</h1>
+		<p>These are commands typically employed by a service implementation, in addition to some of the normal commands. All of the commands listed here require the sender to be correctly U:Lined. This means that the services server name must appear within a ulines {} block in the unrealircd.conf configuration for ALL servers in the network. All servers and clients behind a U:Lined server are themselves U:Lined.</p>
+		<h2><a name="S6_1"></a>6.1 SVSKILL - Force Disconnect by Service (TOKEN: h)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> h <i>target</i> :<i>reason</i></tt></p>
+		<p>This command is similar to KILL but differs in several ways. First of all: there is no mutilation of the reason value. The reason given is the exact reason used to generate QUIT messages sent to users. Second, it is silent; no server notice is generated in response to this command. Third, it can only be used by a U:Lined server or client (such as services).</p>
+		<p>Because this command can be dangerous in the hands of an abusive person, service implementations should avoid granting humans control over the reason parameter. In cases of commands where a person has control over such parameter, either use a regular KILL instead, or otherwise modify the reason so that operators can be held accountable if necessary.</p>
+		<h2><a name="S6_2"></a>6.2 SVSMODE, SVS2MODE - Force User Mode Change (TOKEN: n or v)</h2>
+		<p><b>Syntax (SVSMODE):</b> <tt>:<i>source</i> n <i>target</i> +<i>usermodes</i></tt></p>
+		<p><b>Syntax (SVS2MODE):</b> <tt>:<i>source</i> v <i>target</i> +<i>usermodes</i></tt></p>
+		<p>Judging by these commands alone, you'd think they are identical. Both commands force a usermode change to occur. This is typically used by services to set +r on a user who has successfully identified. They differ in that SVS2MODE also sends the mode change to the user, while SVSMODE does not (hidden mode change).</p>
+		<p>SVSMODE and SVS2MODE also give special treatment to usermode +d. Rather than setting the deaf mode like you might expect, SVS(2)MODE +d allows services to change a user's services stamp (which is given in the NICK message). This could allow services to set the service stamp to an easily identifiable value that could then be used to say "hey, this person identified already". The syntax of this is: +d <i>newservicestamp</i> and can be combined with setting other usermodes as well. The deaf mode <b>can</b> be set by using +d without the service stamp parameter; however, in this case you <b>cannot</b> set the service stamp in the same SVS(2)MODE message.</p>
+		<p><b>Note:</b> Do <b>NOT</b> use SVSMODE to remove IRCop status from a user. Use the SVSO command for that instead.</p>
+		<p>Alternatively, target can name a channel. In this case, the mode change parameter can consist of a - character, followed by any or all of: b, e, I, q, a, o, h, or v. These characters cause the corresponding lists to be cleared of all entries. For example: SVSMODE #channel -b removes ALL bans from #channel, and SVSMODE #channel -qaohv turns ALL users on #channel into normal users (removes all owner, admin, op, halfop, and voice status). In this case, the uplink will acknowledge with a MODE listing the bans, etc that were removed.</p>
+		<p>To completely clear a channel of all modes: MODE #channel -cfijklmnprstzACGMKLNOQRSTVu (plus any added by third-party module) followed by SVSMODE #channel -beIqaohv.</p>
+		<h2><a name="S6_3"></a>6.3 SVSSNO, SVS2SNO - Forced SNomask Change (TOKEN: BV or BW)</h2>
+		<p><b>Syntax (SVSSNO):</b> <tt>:<i>source</i> BV <i>target</i> +<i>snomasks</i></tt></p>
+		<p><b>Syntax (SVS2SNO):</b> <tt>:<i>source</i> BW <i>target</i> +<i>snomask</i></tt></p>
+		<p>Changes a user's snomasks. The difference between SVSSNO and SVS2SNO is the same as with SVSMODE versus SVS2MODE. If the user is not +s, you must add it via SVSMODE +s. For example:</p>
+		<pre>:OperServ v someuser +s
+:OperServ BW someuser +ks</pre>
+		<h2><a name="S6_4"></a>6.4 SVSNICK - Forced Nick Change (TOKEN: e)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> e <i>target</i> <i>newnick</i> :<i>newtimestamp</i></tt></p>
+		<p>Forces the specified user to change his nick to newnick and also sets the nick timestamp to newtimestamp (so, for example, services could protect identified users from a nick collision by simply setting the nick timestamp to something way less than "now" - though currently this requires actually changing the nick too). SVSNICK requires the server to which the target is connected to acknowledge the nick change. If the user specified by newnick already exists, then target will be disconnected (even if it's something like a case-change).</p>
+		<h2><a name="S6_5"></a>6.5 SVSJOIN - Forced Join (TOKEN: BX)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> BX <i>target</i> <i>#channel</i></tt></p>
+		<p>This is identical to SAJOIN with a few exceptions: 1) It is U:Line-only. 2) No opernotice on use. 3) Bans and restricting modes are respected, a prior INVITE message must be sent to cause bans to be ignored.</p>
+		<h2><a name="S6_6"></a>6.6 SVSPART - Forced Part (TOKEN: BT)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> BT <i>target</i> <i>#channel</i> :<i>reason</i></tt></p>
+		<p>Also identical to SAPART with a few exceptions: no static prefix on the optional part reason, and no global notice, and requires a U:Line. Usage recommendation of SVSPART versus KICK is the same as for SVSKILL versus KILL.</p>
+		<h2><a name="S6_7"></a>6.7 SVSO - Oper Permissions (TOKEN: BB)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> BB <i>target</i> <i>flagchanges</i></tt></p>
+		<p>This allows a service to add or remove IRCop permission flags for a user. Flagchanges is formatted similar to that of MODE with the exception that operflags are used instead of usermodes. If the change string consists only of -, then all oper permissions, usermodes, and snomasks are removed (as if the user had himself typed MODE nick -Oo).</p>
+		<p>If you are granting IRCop permissions to a user who is not currently an IRCop, you should follow up with an SVSMODE +o or SVSMODE +O as appropriate. For example:</p>
+<pre>:OperServ BB somenick +o
+:OperServ BW somenick +cefknoqsSv
+:OperServ AL somenick local.oper.somethinghere.net
+:OperServ v somenick +Ohs </pre>
+		<h2><a name="S6_8"></a>6.8 SVSNOOP - Oper Lockdown (TOKEN: f)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> f <i>(op)</i><i>server.name</i></tt></p>
+		<p>The (op) parameter is either a + or - indicating if NOOP mode should be activated (+) or deactivated (-). When NOOP mode is activated, all IRCops on the server are deopered (including local operators) and the /oper command is disabled. IRCop privileges can still be granted through use of SVSO. On UnrealIRCd, it is not necessary to masskill all IRCops on the nooped server, as they are deopered automatically.</p>
+		<h2><a name="S6_9"></a>6.9 SVSNLINE - RealName Ban (TOKEN: BR)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> BR <i>op</i> <i>reason</i> :<i>realname mask</i></tt></p>
+		<p>Op is either + (add) or - (remove). In the case of +, reason is a space-escaped string (all space chars are encoded as _). If -, reason is ignored.</p>
+		<h2><a name="S6_10"></a>6.10 SVSFLINE - File Ban (TOKEN: BC)</h2>
+		<p><b>Syntax (add):</b> <tt>:<i>source</i> BC + <i>filemask</i> :<i>reason</i></tt></p>
+		<p><b>Syntax (remove):</b> <tt>:<i>source</i> BC - <i>filemask</i></tt></p>
+		<p><b>Syntax (clear):</b> <tt>:<i>source</i> BC *</tt></p>
+		<p>Adds or removes a DCCDENY item for the specified filemask on all servers. These DCCDENYs are hard dccdenies - the /dccallow command cannot override it. The last form removes all dccdenies added via SVSFLINE.</p>
+		<hr/>
+		<h1><a name="S7"></a>7 Messaging</h1>
+		<p>What good is Internet Relay <b>CHAT</b> if users cannot <b>CHAT</b>? This section addresses the commands through which arbitrary user messages are sent.</p>
+		<h2><a name="S7_1"></a>7.1 PRIVMSG, NOTICE - Simple Message Transmission (Token: ! or B)</h2>
+		<p><b>PRIVMSG Syntax:</b> <tt>:<i>source</i> ! <i>target</i> :<i>message</i></tt></p>
+		<p><b>NOTICE Syntax:</b> <tt>:<i>source</i> B <i>target</i> :<i>message</i></tt></p>
+		<p>Sends a messages to the given target. The target either names a single client, or identifies a list of clients in which the message is to be sent to. The available targets include:</p>
+		<ul>
+			<li><i>nickname</i>: Names a single user to whom the message is delivered.</li>
+			<li><i>nickname</i>@<i>servermask</i>: Also names a single user, but the message will only be delivered if the user is connected to a server matching the specified servermask. This is typically used for sending messages to services. The target must not be changed at any point along the path it must travel for delivery, even up to the final receipt of the message by the target. This allows the target to know it has been sent a message in this way.</li>
+			<li>#<i>channelname</i>: Sends a message to all users on the specified channel (except when channel is a moderated auditorium (+mu), in which case the wierd +mu sending behavior goes off).</li>
+			<li><i>modeprefix</i>#<i>channelname</i>: Sends a message to all users on the given channel having the given status or higher. For example: + means all voices, halfops, etc.</li>
+			<li>$<i>servermask</i>: Sends a message to ALL users on all servers matching the specified servermask (known as a server broadcast message). The RFC requirements of having a TLD with no wildcards is not applied to U:Lined clients.</li>
+		</ul>
+		<p>Unreal does not support the #hostmask format.</p>
+		<h2><a name="S7_2"></a>7.2 SENDUMODE, SMO - Usermode-based Delivery (TOKEN: AP or AU)</h2>
+		<p><b>Syntax:</b> <tt>@<i>servernumeric</i> AU <i>umode</i> :<i>message</i></tt></p>
+		<p>Sends the specified message to all users with the given mode. Only one usermode may be given. This is a server-only command if you can't tell from the sender prefix :) .</p>
+		<p>The message will be displayed as coming from the receiving client's own server. It may be appropriate to add a &quot;*** Notice (or other leader here) -- from blah:&quot; if you wish to clarify where the message is from.</p>
+		<h2><a name="S7_3"></a>7.3 SENDSNO - SNomask-based Delivery (TOKEN: Ss)</h2>
+		<p><b>Syntax:</b> <tt>@<i>servernumeric</i> Ss <i>snomask</i> :<i>message</i></tt></p>
+		<p>Sends the specified message to all users with the given snomask. Only one snomask may be given. This is a server-only command if you can't tell from the sender prefix :) .</p>
+		<p>The message will be displayed as coming from the receiving client's own server. It may be appropriate to add a &quot;*** Notice (or other leader here) -- from blah:&quot; if you wish to clarify where the message is from.</p>
+		<h2><a name="S7_4"></a>7.4 CHATOPS - IRCop Chat (TOKEN: p)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> p :<i>message</i></tt></p>
+		<p>Sends the message to all IRCops on all servers.</p>
+		<h2><a name="S7_5"></a>7.5 WALLOPS - Wallop Chat (TOKEN: =)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> = :<i>message</i></tt></p>
+		<p>Sends the message to all users with usermode +w, whether they are ircops or not.</p>
+		<h2><a name="S7_6"></a>7.6 GLOBOPS - FailOp Chat (TOKEN: ])</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> ] :<i>message</i></tt></p>
+		<p>Send the message to all IRCops with usermode +g.</p>
+		<h2><a name="S7_7"></a>7.7 ADCHAT - Admin Chat (TOKEN: x)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> x :<i>message</i></tt></p>
+		<p>Send the message to all Server and Network Admins (usermode +A).</p>
+		<h2><a name="S7_8"></a>7.8 NACHAT - NetAdmin Chat (TOKEN: AC)</h2>
+		<p><b>Syntax:</b> <tt>:<i>source</i> AC :<i>message</i></tt></p>
+		<p>Send the message to all Network Admins (usermode +N).</p>
+		<hr/>
+		<h1><a name="S8"></a>8 Ban Control</h1>
+		<p>Sometimes, you have the misfortune of encountering a user who has no purpose but to serve as an annoyance to your server or network. These commands transmit network-wide ban information amongst each other.</p>
+		<h2><a name="S8_1"></a>8.1 TKL - Master Ban Control (TOKEN: BD)</h2>
+		<p>The TKL command seems to have one oddity about it: the real ban source is included in the TKL command rather than in the sender prefix. Most likely this is done for synching reasons (so that the *line ban can be credited to the proper person even if he/she is offline). For this reason, the command syntax is given without any sender prefix at all. It is still permissible to use one, however.</p>
+		<h3><a name="S8_1_1"></a>8.1.1 GLINE - Network-wide user@host ban</h3>
+		<p><b>Add Syntax (TKL):</b> <tt>BD + G <i>userpart</i> <i>hostpart</i> <i>source</i> <i>expiretimestamp</i> <i>settimestamp</i> :<i>reason</i></tt></p>
+		<p><b>Remove Syntax (TKL):</b> <tt>BD - G <i>userpart</i> <i>hostpart</i> <i>source</i></tt></p>
+		<p>Adds and Removes Network-wide user@host bans, known as G:Lines. The GLINE command itself must not be used. The userpart and hostpart are the user portion and hostname portion of the ban mask. The expiretimestamp is 0 if the G:Line should not expire, otherwise it will expire at the given time. It is an absolute time, not relative, thus it's imperitive to have reasonably synchrnoized clocks or bans may be removed too early or even immediately!</p>
+		<h3><a name="S8_1_2"></a>8.1.2 GZLINE - Network-wide IP ban</h3>
+		<p><b>Add Syntax (TKL):</b> <tt>BD + Z * <i>ipmask</i> <i>source</i> <i>expiretimestamp</i> <i>settimestamp</i> :<i>reason</i></tt></p>
+		<p><b>Remove Syntax (TKL):</b> <tt>BD - Z * <i>ipmask</i> <i>source</i></tt></p>
+		<p>Adds and Removes Network-wide IP bans, known as Global Z:Lines. The GZLINE command itself must not be used. Ipmask permits CIDR notation as well as wildcard masks.</p>
+		<h3><a name="S8_1_3"></a>8.1.3 SQLINE, UNSQLINE - Network-wide Nickname ban (TOKEN: c or d)</h3>
+		<p><b>Add Syntax (TKL):</b> <tt>BD + Q <i>hold</i> <i>nickmask</i> <i>source</i> <i>expiretimestamp</i> <i>settimestamp</i> :<i>reason</i></tt></p>
+		<p><b>Add Syntax (SQLINE):</b> <tt>:<i>source</i> c <i>nickmask</i> :<i>reason</i></tt></p>
+		<p><b>Remove Syntax (TKL):</b> <tt>BD - Q <i>hold</i> <i>nickmask</i> <i>source</i></tt></p>
+		<p><b>Remove Syntax (UNSQLINE):</b> <tt>:<i>source</i> d <i>nickmask</i></tt></p>
+		<p>In the TKL syntax, the hold parameter is either a * to mark the qline as a nick ban, or an H to mark it as a services hold. A services hold does not trigger qline rejection notice, and is typically used by NickServ to reserve registered nicks until they are released by the owner. The (UN)SQLINE syntax can only be used by a server, but any user can be used as the source for the TKL syntax. Unlike G and GZ lines, Q:Lines do not cause existing matching users to be disconnected or otherwise affected.</p>
+		<p>The TKL syntax is preferred, since it is more flexible, but (UN)SQLINE is permitted for compatibility.</p>
+		<h3><a name="S8_1_4"></a>8.1.4 SPAMFILTER - Message Spam Filtration System</h3>
+		<p>Proper use of spamfilter in TKL commands requires use of PROTOCTL TKLEXT, which increases the number of parameters allowed in TKL.</p>
+		<p><b>Add Syntax (TKL):</b> <tt>BD + F <i>target(s)</i> <i>action</i> <i>source</i> 0 <i>settimestamp</i> <i>tklduration</i> <i>tklreason</i> :<i>regex</i></tt></p>
+		<p><b>Remove Syntax (TKL):</b> <tt>BD - F <i>target(s)</i> <i>action</i> <i>source</i> 0 <i>settimestap</i> :<i>regex</i></tt></p>
+		<p>Adds and Removes network-wide spamfilters. The SPAMFILTER command itself must not be used. See <a href="http://vulnscan.org/UnrealIrcd/unreal32docs.html#feature_spamfilter">http://vulnscan.org/UnrealIrcd/unreal32docs.html#feature_spamfilter</a> for a list of valid targets. For actions, a single character is used to identify the action to be taken:</p>
+		<ul>
+			<li>K (kill) - The user is simply disconnected, with the reason given.</li>
+			<li>S (tempshun) - A temporary shun is placed on the user. This shun is applied only to that user, and disappears if the user reconnects.</li>
+			<li>s (shun) - A regular shun on the user's IP address is added. This causes all users with the same hostname to be shunned, but they will also stay shunned if they reconnect.</li>
+			<li>k (kline) - A K:Line is added on the user's IP address.</li>
+			<li>z (zline) - A Z:Line is added on the user's IP address.</li>
+			<li>g (gline) - A G:Line is added on the user's IP address.</li>
+			<li>Z (gzline) - A Global Z:Line is added on the user's IP address.</li>
+			<li>b (block) - Messages (or users!) matching the filter are simply blocked.</li>
+			<li>d (dccblock) - The user is prevented from sending files using DCC for the remainder of his session (in other words, until he quits).</li>
+			<li>v (viruschan) - User is removed from all channels, joined to the viruschan as defined in conf, and cannot message anything but that channel.</li>
+			<li>w (warn) - No action on the user is taken. Only the Spamfilter notice is sent to opers with snomask +S.</li>
+		</ul>
+		<h1><a name="S9">9 Base64 Tables</a></h1>
+		<p>Unreal uses base64 encoding to allow saving bandwidth by encoding numbers in a more compact format. Unreal uses two different variations of base64, one used for the SJB64 PROTOCTL option (in NICK and SJOIN), and one used for NICKIP.</p>
+		<h2><a name="S9_1">9.1 Table for SJB64 (NICK and SJOIN).</a></h2>
+		<p>In NICK and SJOIN, remember that the timestamp will be prefixed with ! to signal a base64 timestamp.</p>
+		<p>Just like in base10, the least significant &quot;digit&quot; is last.</p>
+		<pre> 0 0            17 H            34 Y            51 p
+ 1 1            18 I            35 Z            52 q
+ 2 2            19 J            36 a            53 r
+ 3 3            20 K            37 b            54 s
+ 4 4            21 L            38 c            55 t
+ 5 5            22 M            39 d            56 u
+ 6 6            23 N            40 e            57 v
+ 7 7            24 O            41 f            58 w
+ 8 8            25 P            42 g            59 x
+ 9 9            26 Q            43 h            60 y
+10 A            27 R            44 i            61 z
+11 B            28 S            45 j            62 {
+12 C            29 T            46 k            63 }
+13 D            30 U            47 l
+14 E            31 V            48 m
+15 F            32 W            49 n
+16 G            33 X            50 o</pre>
+		<h2><a name="S9_2">9.2 Table for NICKIP.</a></h2>
+		<p>In this table, the IP is encoded in network byte order. In terms of IPs, this means the first byte of the address really is first. Each &quot;digit&quot; in the base64 encoded IP corresponds to 6 bits of the IP address.</p>
+		<p>An IPv4 address is 32 bits, so 6 base64 &quot;digits&quot; are needed. Since base64 requires values to come in multiples of 4 &quot;digits&quot;, padding characters (=) need to be added if a value comes up short. In the case of IPv4 addresses, two are needed.</p>
+		<p>IPv6 addresses are 128-bit. They therefore need 22 base64 &quot;digits&quot; plus 2 pad characters.</p>
+		<pre> 0 A            17 R            34 i            51 z
+ 1 B            18 S            35 j            52 0
+ 2 C            19 T            36 k            53 1
+ 3 D            20 U            37 l            54 2
+ 4 E            21 V            38 m            55 3
+ 5 F            22 W            39 n            56 4
+ 6 G            23 X            40 o            57 5
+ 7 H            24 Y            41 p            58 6
+ 8 I            25 Z            42 q            59 7
+ 9 J            26 a            43 r            60 8
+10 K            27 b            44 s            61 9
+11 L            28 c            45 t            62 +
+12 M            29 d            46 u            63 /
+13 N            30 e            47 v
+14 O            31 f            48 w         (pad) =
+15 P            32 g            49 x
+16 Q            33 h            50 y</pre>
+	</body>
+</html>

doc/technical/token.txt

@@ -0,0 +1,109 @@
+Token List (c) 2002-2004 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
+
+Command     Token 
+------------------------------------------------------------------------------------------------
+PRIVMSG     !
+WHOIS       #
+NICK        &
+SERVER      '
+TOPIC       )
+INVITE      *
+VERSION     +
+QUIT        ,
+SQUIT       -
+KILL        .
+INFO        /
+LINKS       0
+STATS       2
+HELP        4
+ERROR       5
+AWAY        6
+CONNECT     7
+PING        8
+PONG        9
+PASS        <
+TIME        >
+ADMIN       @
+SETHOST     AA
+NACHAT      AC
+SETIDENT    AD
+SETNAME     AE
+LAG         AF
+SDESC       AG
+KNOCK       AI
+CREDITS     AJ
+LICENSE     AK
+CHGHOST     AL
+RPING       AM
+RPONG       AN
+NETINFO     AO
+SENDUMODE   AP
+ADDMOTD     AQ
+ADDOMOTD    AR
+SVSMOTD     AS
+SMO         AU
+OPERMOTD    AV
+TSCTL       AW
+SAJOIN      AX
+SAPART      AY
+CHGIDENT    AZ
+NOTICE      B
+SWHOIS      BA
+SVSO        BB
+SVSFLINE    BC
+TKL         BD
+VHOST       BE
+BOTMOTD     BF
+HTM         BH
+DCCDENY     BI
+UNDCCDENY   BJ
+CHGNAME     BK
+SHUN        BL
+CYCLE       BP
+MODULE      BQ
+SVSNLINE    BR
+SVSPART     BT
+SVSLUSERS   BU
+SVSSNO      BV
+SVS2SNO     BW
+SVSJOIN     BX
+SVSSILENCE  Bs
+SVSWATCH    Bw
+JOIN        C
+PART        D
+LUSERS      E
+EOS         ES
+MOTD        F
+MODE        G
+KICK        H
+REHASH      O
+RESTART     P
+CLOSE       Q
+SENDSNO     Ss
+DNS         T
+TEMPSHUN    Tz
+SILENCE     U
+AKILL       V
+UNKLINE     X
+RAKILL      Y
+GLOBOPS     ]
+LOCOPS      ^
+PROTOCTL    _
+WATCH       `
+TRACE       b
+SQLINE      c
+UNSQLINE    d
+SVSNICK     e
+SVSNOOP     f
+SVSKILL     h
+SVSMODE     n
+SAMODE      o
+CHATOPS     p
+UNZLINE     r
+RULES       t
+MAP         u
+SVS2MODE    v
+DALINFO     w
+ADMINCHAT   x
+UMODE2      |
+SJOIN       ~

doc/technical/vl.txt

@@ -0,0 +1,36 @@
+VL Information (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
+
+Protocol       Version
+------------------------------------------------------------------------------------------------
+2308           3.2.5
+2307           3.2.4
+2306           3.2.3
+2305           3.2.2
+2304           3.2.1
+2303           3.2-beta*, 3.2-RC*, 3.2
+2302           3.1.1-Darkshades, 3.1.2-Darkshades, 3.1.3-Komara, 3.1.4-Meadows
+2301           3.1-Silverheart
+2300           3.0-Morrigana
+
+Flag           Description
+------------------------------------------------------------------------------------------------
+c              Server is chrooted
+C              command line config enabled
+D              Server is in debugmode
+F              Using file descriptor lists
+h              Compiled as a hub
+i              Shows invisible users in /trace
+n              NOSPOOF enabled
+V              Uses valloc()
+W              Windows version
+Y              Syslog logging enabled
+K              No ident checking (?)
+6              IPv6 supported
+X              STRIPBADWORDS enabled (chmode/umode +G)
+P              Uses poll()
+e              SSL supported
+O              OperOverride enabled
+o              OperOverride without verify
+Z              Zip links supported
+3              3rd party modules (were) loaded or unreal is any other way 'tainted' (eg: bad libs)
+E              Extended channel modes supported

doc/translations.txt

@@ -0,0 +1,48 @@
+NOTE: For 3.3* we are not maintaining translated documents until reaching alpha or
+beta1 status.
+
+==[ Translations ]============================================================
+
+Starting with the release of Unreal 3.2 we have begun accepting translated
+documentation files. For now, only translations of unreal32docs.html and
+example.conf are accepted. Other stuff might be translated later, but
+this will probably be postponed to 3.3 (numerics/ircd text/help.conf/etc).
+
+There a few requirements however:
+- When you submit your translation it should be a translation of the
+  very latest doc... So be sure to translate the cvs version of
+  unreal32docs.html (www.vulnscan.org/UnrealIrcd/unreal32docs.html).
+- Of course the translation should be correct.. So also 'technically',
+  it's therefore recommended that have some real experience with Unreal ;)
+- If you are accepted and start working on it, it would be nice if you
+  could put your docs-in-progress online somewhere so we can see how
+  progress is going a bit.
+- You should use a proper HTML editor, this especially excludes Microsoft
+  Word and Frontpage since it enlarges the .html file by (at least) 30%.
+  Don't worry, there are enough free&simple html editors out there that
+  work perfectly fine, you won't need to be an HTML expert at all!
+- Someone, usually the person who translated it, needs to be willing
+  to actively maintain the docs. This is very important! If docs are
+  out of date (out-of-synch) there will be confusion among users.
+  Translators will receive once a week (and right before every release)
+  all changes that were made in unreal32docs.html. Then the translator
+  should update his/her doc and send it in (or commit it via cvs).
+  Count on an average of 15 minutes a week (it varies).
+
+Now, we should tell you that the first-time translation of unreal32docs.html
+is a LOT of work.. probably 20 hours or so. After that, the weekly updates
+take really just 5, 10, 15 minutes a week, which is pretty much "no time".
+Now why would you translate at all? Well, by translating UnrealIRCd
+documentation you will help out your fellow citizens and/or other people
+of that language, you will make Unreal a bit more 'internationalized',
+and it's a worthwile contribution to the UnrealIRCd project.
+Upon successful completion you will also receive an @unrealircd.org
+forwarder email address, and of course your name will be in the docs.
+
+If you want to start translating a document, please send an email to
+coders@lists.unrealircd.org and mention the language you are willing
+to translate to.. You will then receive an email back saying you can
+go ahead (or not). This is mainly to avoid multiple persons working 
+on the same translation.
+
+==============================================================================

doc/unrealircd.doc

@@ -1,407 +0,0 @@
-                ****** UnrealIRCd v2.1.7 Documentation ******
-        [ $Id$ ]
-
-1) About UnrealIRCd
-
-  	I started making UnrealIRCd about 1-2 months ago. (July 1999 now)
-  	First it was called mpx2.0b13.soundforge - as I was
-  	inspired of the 'forge' word. I quickly changed name
-  	after I realized the IRCd had more potential.
-        Unreal is based off Elite2.0b13 and some of
-  	the minor bugfixes Potvin came up with. First lemme
-  	introduce myself. My nick is Techie/Stskeeps. I hang
-  	out at Global-IRC.net, DALnet, DragonWings.org and so on
-  	
-	Unreal is a hybrid of Elite (as I said) mixed with some
-	Twilight IRCd, TerraIRCd, TS4 (channel mode +h & +e) features
-	(IMHO TwilightIRCd is one of the best dreamforge hybrids I've seen!
-	Unreal is not a rip-off of other IRCds - I added a lot of features myself!
-	I really cannot mention some major features as I think a IRCd is a
-	IRCd when it has got useful commands- and people actually say mine has!
-	
-	Anyways I dunt demand donations or anything. I just do coding for fun
-	I treat coding like playing with toys. It makes me happy(or is it just
-	caffeine?;). An addy to send donations is at the Donation file in the IRCd dir
-	And.. I don't sweat while making features unlike some Potvin coder so dunt
-	send me towels;) I would be more happy if someone e-mailed me with ideas
-	to the IRCd.. The whole IRCd is GNU so if you want to rip off any of my ideas
-	You are generally welcome:) Just remember to do what's said in the Changes file!
-	-- So.. Enjoy this IRCd:) It may become a dream to IRCd owners as its infact
-	   a sortof hybrid of EliteIRCd (Cite .man-pages/page1 in Elite:
-	EliteIRCD has become a dream to many ircd owners</end cite>
-	   -- Carsten Munk / Techie .. =)
-
-2) Commands (User Commands)
-
-       *** WATCH Command ***
-	Watch is a new notify-type system in UnrealIRCd which is both faster
-	and uses less network resources than any old-style notify
-	system. You may add entries to your Watch list with the command
-	/watch +nick1 [+nick2 +nick3 ..., and the server will send
-	you a message when any nickname in your watch list logs on or off.
-	Use /watch -nick to remove a nickname from the watch list, and
-	just /watch to view your watch list.
-	The watch list DOES NOT REMAIN BETWEEN SESSIONS - you (or your
-	script or client) must add the nicknames to your watch list every
-	time you connect to an IRC server. /Watch was made in DreamForge IRCd
-	which UnrealIRCd in ground is based off
-
-   	 *** HELPOP Command ***
-   	HelpOp is a new system of getting IRC Server help. You type either
-   	/HelpOp ? <help system topic>  or /HelpOp ! <question>
-   	The "?" in /HelpOp means query the help system and if you get no
-   	response you can choose '!' to send it to the Help Operators online
-   	------------oOo--------------
-
-     *** LIST Command ***
-	New extended /list command options are supported.  To use these
-	features, you will likely need to prefix the LIST command with
-	/quote to avoid your client interpreting the command.
-
-	Usage: /quote LIST options
-	
-	If you don't include any options, the default is to send you the
-	entire unfiltered list of channels. Below are the options you can
-	use, and what channels LIST will return when you use them.
-	>number  List channels with more than <number> people.
-	<number  List channels with less than <number> people.
-	C>number List channels created between now and <number> minutes ago.
-	C<number List channels created earlier than <number> minutes ago.
-	T>number List channels whose topics are older than <number> minutes
-	         (Ie., they have not changed in the last <number> minutes.
-	T<number List channels whose topics are newer than <number> minutes.
-	*mask*   List channels that match *mask*
-	!*mask*  List channels that do not match *mask*
-	LIST defaults to sending a list of channels with 2 or more members,
-	so use the >0 option to get the full channel listing.  
-
-		*** PRIVMSG Command ***
-	PRIVMSG and NOTICE, which are used internally by the client for
-	/msg and /notice, in UnrealIRCd support two additional formats:
-	/msg @#channel <text> will send the text to channel-ops on the
-	given channel only. /msg @+#channel <text> will send the text
-	to both ops and voiced users on the channel. While some clients
-	may support these as-is, on others (such as ircII), it's necessary
-	to use /quote privmsg @#channel <text> instead. It's perhaps a
-	good idea to add the/alias omsg /quote privmsg @$0 $1 into
-	your script (.ircrc) file in that case.
-
-	**** KNOCK Command ****
-	/Knock is a new UnrealIRCd command which enables you to
-	'knock' on a channel if it is +i and these criteria is met
-	- Channel is not +K (No knocks)
-	- Channel is not +I (No invites!)
-	- You're not banned!
-	- And you are not already there:)
-
-	Syntax:
-      /Knock #Channel :Reason
-     
-      **** LICENSE Command ****
- 	This command shows the GNU License
- 	Which is hard-coded into the IRCd:)
-	Syntax: /License [optional server]
-
-	*** SetName Command ***
-   	/SetName is a new feature in UnrealIRCd
-   	Which allows users to change their 'Real name'
-   	(GECOS) directly online at IRC without reconnecting
-   	
-	Syntax:
-   	/SetName :New Real Name
-
-
-   	*** MODE Command ***
-   	This is basically the /mode command as it has always
-   	been on IRC. Thou in Channel mode basis it has got an
-   	Extra feature (/mode #Channel ^ ) which reports channel
-   	modes represented in a bitstring (may be handy, maybe not)
-   	UnrealIRCd has got some new channel / usermodes I think you
-   	wish to take a look at
-   	Channel Modes Help: /HelpOp CHMODES
-   	User modes help: /HelpOp UMODES
- 
-	*** STATSERV Command ***
-  	This is a alias for the /msg StatServ command,
-   	But is more secure. If the IRC network doesn't have StatServ
-   	It will report it is down.
-   	
-	Syntax:
-   	/StatServ <command>
-
-   	*** /Credits Help ***
-  	This command will list the credits I've created
-   	to thank the people who has helped me with making
-   	UnrealIRCd. Anyone who I've forgotten all my kind
-   	thoughts go to -- Techie'99
-   	
-	Syntax:
-   	/Credits [optional server]
-
-   	*** /DALINFO Help ***
-   	This command will list the credits that the
-   	Dreamforge IRCd team/the IRCd developers
-   	from the start when IRCd got developed
-   	
-	Syntax:
-   	/DALInfo [optional server]
-
-3) Operator Commands
-
- 	This section is the IRCOp's only commands
-   	area:) - These topics are available:
-   	Note: This doesnt include Dreamforge commands
-
-   	SETHOST    SETIDENT     SDESC
-   	ADCHAT     NACHAT       TECHAT
-   	GLINE      REMGLINE     STATS
-   	MKPASSWD   SNOTES       SNOTE
-   	ADDLINE    LAG          RPING
-	ADDMOTD	   ADDOMOTD     OPERMOTD
-	CHGHOST	   TSCTL        SAJOIN
-
-	*** ADDMOTD Command Help ***");
-	This will add the text you specify to the MOTD
-	(the general motd - T:lines doesnt count ..)
-	Server Admin & Co-Admin only
-
-	Syntax: /ADDMOTD :text
-
-	*** ADDOMOTD Command Help ***
-	This will add the text you specify to the Operator MOTD
-	Server Admin & Co-Admin only
-	
-	Syntax: /ADDOMOTD :text
-
-	*** OPERMOTD Command Help ***
-	This is a IRCop only command - shows the IRCd Operator MOTD
-	Syntax: /OperMotd
-			
-   	*** SETHOST Command Help ***
-   	This command is so you can change your
-   	Virtual host (hiddenhost) to everything you want to
-   	Except special characters;). 
-	
-	Syntax:
-  	/SetHost <new hostname>)
-  	
-	Example:
-   	/Sethost ircaddicts.org
-   	
-	*** SETIDENT Command Help ***
-   	With this command you can change your
-   	ident (username).
-   	
-	Syntax:
-   	/SetIdent <new ident>
-
-	Example:
-	/SetIdent root
-
-   	*** SDesc Command help ***
-   	NOTE: This is a Server Admin/Co Admin only command
-   	With this command you can change your Server Info Line
-   	Without having to squit and reconnect.
-   	Syntax: /SDesc :New description
-   	Example: /SDesc :If you belong to me..		
-
-   	*** AdChat Command Help ***
-   	This command sends to all Admins online (IsAdmin)
-   	Only for Admins. This is a ChatOps style command
-   	Syntax: /AdChat :<text>
-	Example: /AdChat :Hey guys!
-  
- 	*** NAChat Command Help ***
-   	This command sends to all NetAdmins & TechAdmins online
-   	Only for Net/Techadmins. This is a ChatOps style command
-   	Syntax: /NAChat :<text>
-	Example: /NAChat :Hey guys!
-   	
-	*** Stats Command Help ***
-   	UnrealIRCd has got a extension called /Stats G
-   	Which will list the current G:Lines
-   	Syntax: /Stats G
-
-   	*** TEChat Command Help ***
-   	This command sends to all TechAdmins online
-   	Only for Net/Techadmins. This is a ChatOps style command
-   	Syntax: /TEChat :<text>
-	Example: /TEChat :Hey guys!
-
-   	*** CHGHOST Command help ***
-   	This command makes you able to change other people's virtual hostname
-   	- IRCop only.
-   	Syntax: /CHGHOST <nick> <newhost>
-  	
-	*** TSCTL Command Help ***");
-  	This is a highly advanced command");
-  	Syntax:");
-  	 /TSCTL OFFSET +|- <time> - Adjust internal IRC clock");
- 	 /TSCTL TIME - Will give TS report");
-
-  	*** SAJOIN Command help **");
-  	Makes <nick> join channel <channel>");
-  	Services Admin only..");
-  	Syntax: /SAJOIN nick channel");
-
-
-   	*** RemGline Command Help
-   	This command can remove G:Lines
-   	
-	Syntax:
-   	/RemGline <user@host mask>
-   	
-	Example:
-   	/RemGline *@*.flirt.org
- 
-  	*** G:line command Help ***
-   	This command provides timed G:Lines. If you match
-   	a G:Line you cannot connect to ANY server at the
-   	IRC network
-   	Syntax:
-   	/GLINE <user@host mask> <seconds to be banned> :<reason>
-   	Example:
-   	/GLINE *@*.dal.net 900 :Spammers
-   	this will ban all users matching *@*.dal.net for 15 minutes
-   	with reason 'Spammers'
-
-   	*** MkPasswd Command help ***
-   	This command will encrypt the string it has been given
-   	So u can add it directly to the ircd.conf if you use
-   	Encrypted passwords. /MKPassWd is disabled in UnrealIRCd/32
-	Syntax : /MkPasswd :string to be encrypted
-   
-	*** SNOTE Command Help ***
-   	This will store the parameter of the command to a file
-   	Which then can be read by using /SNOTES LIST
-	Syntax:  /SNOTE :<message>
-   	
-	*** SNOTES Command Help ***
-   	This command is made to view notes
-   	Written to the SNOTE file by using /SNOTE
-   	Syntax: /SNOTES LIST
-      or /SNOTES <number>
-
-  	*** ADDLINE Command Help ***
-  	This command can be used to add lines to the ircd.conf file
-  	Only for Server Admins
-  	Syntax: /AddLine :<line>
-
-	*** LAG Command Help ***
-	This command is like a sonar/traceroute for IRC servers
-	You type in /lag server1.irc.net and it will
-	reply from every server it passes with time and so on
-	Useful for looking where lag is and optional TS future/past travels
-	Syntax: /LAG <servername>
-
-	**** RPING Command help ***	
-        This will calculate the milliseconds (lag) between servers
-	
-        Syntax: /RPING <servermask>
-
- 4) *** UnrealIRCd Usermodes ***
-		o = Global IRCop
-		O = Local IRCop
-		i = Invisible (Not shown in /who searches)
-		w = Can listen to wallop messages
-		g = Can read & send to globops, and locops
-		h = Available for help
-		s = Can listen to server notices
-		k = See's all the /KILL's which were executed
-		S = For services only. (Protects them)
-		a = Is a services admin
-		A = Is a server admin
-		N = Is a network admin
-		T = Is a tech admin
-		C = Is a co admin
-		c = See's all connects/disconnects on local server
-		f = Listen to flood alerts from server
-		r = Identifies the nick as being registered
-		x = Gives the user hidden hostname
-		e = Can listen to server messages sent to +e users
-		b = Can read & send to chatops
-		W = (IRCops only) Lets you see when people does a /whois on you
-		q = (Services Admins only) Gets you unable to be
-		     kicked unless by U:Lines
-		B = (users) Marks you being a Bot
-		F = (net|tech admin only) Lets you see far client connect/disconnects
-		I = (net|tech admin only) Invisible Join/Part. Makes you
-                    being hidden at channels
-		1 = (IRCops only) Marks you a Coder 
-5) *** UnrealIRCd Channel Modes ***
-	    p = Private channel
-	    s = Secret channel
-	    i = Invite-only allowed
-	    m = Moderated channel, noone can speak except users with mode +voh
-	    n = No messages from outside channel
-	    t = Only channel operators may set the topic
-	    r = Channel is registered
-	    R = Requires a registered nickname to join the channel
-	    x = No ANSI color can be sent to the channel
-	    q = Channel owner (The big cheese)
-	    Q = No kicks able in channel unless by U:Lines
-	    O = IRCop only channel (setable by Opers)
-	    A = Server Admin | Network Admin | Tech Admin only channel (same as above)
-	    K = /Knock is not allowed
-	    I = /Invite is not allowed
-	    S = Strip all incoming colours away
-	    l <number of max users> = Channel may hold at most <number> of users
-	    b <nick!user@host>      = Bans the nick!user@host from the channel
-	    k <key>                 = Needs the channel key to join the channel
-	    o <nickname>            = Gives operator status to the user
-	    v <nickname>            = Gives voice to the user (May talk if chan is +m)
-	    a <nickname>            = Gives protection to the user (No kick/drop)
-	    e <exception ban>       = Exception ban - If someone matches it
-		                          they can join even if some else ban matches!
-	    h <nickname>            = Gives halfop status to the user	    
-	    L <chan2>		    = If channel is full (+l) the next user
-					will autojoin <chan2>
-	    You can get additional explanation on modes:
-		 Q h
-	    With /HELPOP mode-<x> where <x> is Q f.x. like mode-Q
-
- 	*** Channel mode +Q ***
-   		This is the 'peace' mode. Noone can kick eachother
-   		except by U:Lines. Bans can be placed thou.
-
-	*** Channel halfops (+h) *** 
-  		If you are marked as halfop (% in /names) you can do:
-  		 - Set topic
-  		 - Kick non-ops
-  		 - Set modes +vmntibe
-
-6) *** UnrealIRCd O:Line flags ***
-		r = Access to /rehash server
-		R = Access to /restart server
-		D = Access to /die server
-		h = Oper can send /help ops - gets +h on oper up
-		g = Oper can send /globops
-		w = Oper can send /wallops
-		l = Oper can send /locops
-		c = Access to do local /squits and /connects
-		Y = Access to do remote /squits and /connects
-		k = Access to do local /kills
-		K = Access to do global /kills
-		b = Oper can /kline users from server
-		B = Oper can /unkline users from server
-		n = Oper can send local server notices(/notice $servername message)
-		N = Oper can send global notices(/notice $*.network.net message)
-		u = Oper can set /umode +c
-		f = Oper can set /umode +f
-		o = Local oper, flags included: rhgwlckbBnuf
-		O = Global oper, flags included: oRDCKN
-		A = Gets +A on oper up. Is server admin
-		a = Gets +a on oper up. Is services admin
-		N = Gets +N on oper up. Is network admin
-		T = Gets +T on oper up. Is tech admin
-		C = Gets +C on oper up. Is co admin
-		z = Can add /zlines
-		H = Gets +x on oper up.
-		W = Gets +W on oper up.	  
-                ^ = Allows to use umode +I
-
-7) Last word
-
-This documentation is based off src/help.c in Unreal2.1.7
-For version Unreal2.1.7 - $Date$ 
-Made by Carsten Munk 1999 (Stskeeps)

dynconf

@@ -1,21 +0,0 @@
-                    [ $Id$ ]
-             Dynamic Configuration Guide
-
-Okay first you have to go edit the file "unrealircd.conf" in 
-the directory "networks/". In that file you see a field with
-name "Include" .. if you want to create your own network file
-(IRC network specification) you have to write like 
-"networks/<irc network>.network" like "networks/myircnetwork.network"
-
-If there is already a network file you can just put in the path
-like : "networks/dragonwings.org"
-
-If you want to create your own network file 
-copy the file "template.network" to the name you want to use for 
-your network file and edit it.
-
-If you experince any problems email me at stskeeps@tspre.org
-or try msg me at /server irc.global-irc.net : #UnrealIRCd
-My nick is mostly Stskeeps or Techie (or Nightwalker if i had a bad night:P)
-
---Stskeeps

extras/burst.c

@@ -0,0 +1,311 @@
+/*
+** burst.c
+**
+** Nicolas Pioch, Dec 93
+** <Nicolas.Pioch@enst.fr>
+** Carsten V. Munk Nov 2000
+*/
+
+#include <sys/types.h>
+#include <sys/time.h>
+#include <sys/socket.h>
+#include <sys/param.h>
+#include <sys/signal.h>
+#include <netinet/in.h>
+#include <sys/un.h>
+#include <netdb.h>
+#include <errno.h>
+#include <arpa/inet.h>
+#include <sys/ioctl.h>
+#include <ctype.h>
+#include <string.h>
+#include <fcntl.h>
+#include <stdio.h>
+
+#ifdef POSIX
+#include <sys/select.h>
+#endif
+
+#define MYBUFSIZE 2048
+
+char *jupedservername, *uplinkservername, *jupereason;
+int	options;
+char *password;
+typedef struct aClient {
+  int socket;
+  char buffer[MYBUFSIZE+1];
+  int read;
+  int write;
+} aClient;
+
+void fatalrestart(aClient *robotptr, const char *s);
+
+void fatal(const char *s) {
+  perror(s);
+  exit(1);
+}
+
+typedef void (*signalhandler)(int);
+static void signal_catcher(int sig, int code, struct sigcontext *scp) {
+  fprintf(stderr, "Caught signal %d with code %d\n", sig, code);
+
+  switch(sig) {
+  case SIGFPE:  /* Floating point exception */
+  case SIGILL:  /* Illegal instruction */
+  case SIGSEGV: /* Segmentation violation */
+  case SIGBUS:  /* Bus error */
+  case SIGSYS:  /* Bad argument to system call */
+    fatal("Fatal signal received, aborting...");
+    break;
+
+  case SIGQUIT:
+  case SIGINT:
+  case SIGTERM: /* On se barre */
+    fatal("AAAAAAAAArrrrrrrrgh!");
+    break;
+  }
+
+  signal(sig, (signalhandler)signal_catcher);
+}
+
+
+typedef union socket_address {
+  struct sockaddr_un unixx;
+  struct sockaddr_in inet;
+} socket_address;
+
+void name_to_number(int address_family, const char *hostname, int port,
+		    socket_address *addr, int *len2) {
+  u_long iaddr;
+  int len;
+  struct hostent *host;
+  char *inaddr;
+  bzero ((char *) addr, sizeof (socket_address) );
+
+  if ( address_family == AF_UNIX ) {
+    strcpy(addr->unixx.sun_path,hostname);
+    *len2=sizeof( struct sockaddr_un );
+  } else {
+    if ((hostname) && (hostname[0])) {
+      if (hostname[0] >= '0' && hostname[0] <= '9') {
+        iaddr = inet_addr(hostname);
+        inaddr = (char *) &iaddr;
+        len=sizeof(iaddr);
+      } else {
+        host=gethostbyname (hostname);
+        if (!host)
+          fatal("Unknown host");
+        inaddr=host->h_addr_list[0];
+        len=host->h_length;
+      }
+    bcopy(inaddr, (char *)&addr->inet.sin_addr, len);
+    }
+  addr->inet.sin_port=htons((u_short) port);
+  *len2=sizeof(struct sockaddr_in);
+  }
+  addr->inet.sin_family = address_family;
+}
+
+int read_data(aClient *robotptr) {
+  int nbytes;
+
+  if ((nbytes=read(robotptr->socket, &(robotptr->buffer[robotptr->write]),
+		  (sizeof(robotptr->buffer) - robotptr->write - 1))) < 0)
+    fatalrestart(robotptr, "read on socket");
+
+  if (nbytes == 0) {
+    close(robotptr->socket);
+    fatalrestart(robotptr, "Connection Closed");
+  }
+
+  robotptr->write+=nbytes;
+  robotptr->buffer[robotptr->write]=0;
+
+  return(nbytes);
+}
+
+void send_data(int socketfd, const char *data, int length) {
+  int length2;
+  length2=write(socketfd, data, length);
+  if (length2 != length)
+    fprintf(stderr, "*** write truncated to %d chars...\n", length2);
+}
+
+int create_client(const char *hostname, const int hostport) {
+  int descript;
+  socket_address hostaddr;
+  int adlen;
+
+  /* winlocal
+  if ((descript=socket(PF_INET, SOCK_STREAM, 0)) < 0)
+  */
+  if ((descript=socket(PF_INET, SOCK_STREAM, 0)) == -1)		// winlocal
+    fatal("socket");
+
+  name_to_number(AF_INET, hostname, hostport, &hostaddr, &adlen);
+
+  if (connect(descript, &hostaddr.inet, adlen) < 0)
+    fatal("connect");
+
+  return(descript);
+}
+
+void parse_line(aClient *robotptr) {
+  char *toparse;
+
+  toparse=(robotptr->buffer + robotptr->read);
+
+  printf("%s\n",toparse);
+  /* Special handling for PING messages */
+  if (!strncasecmp(toparse, "PING ", 5) || !strncasecmp(toparse, "8 ", 2)){
+    toparse=strtok(toparse, "\r\n");
+    toparse[1]='\0';
+    send_data(robotptr->socket, toparse, strlen(toparse));
+    return;
+  }
+  if (!strncasecmp(toparse, "AO", 2) || !strncasecmp(toparse, "NETINFO", 7))
+  {
+	if (!(options & 0x80))
+	  	exit(1);
+  }
+}
+
+void parse_data(aClient *robotptr) {
+  int next;
+
+  while((robotptr->read < robotptr->write)
+	&& ((robotptr->buffer[robotptr->read] == '\r')
+	    || (robotptr->buffer[robotptr->read] == '\n')))
+    robotptr->read++;
+
+  for(next=robotptr->read; next<=robotptr->write; next++) {
+    if ((robotptr->buffer[next] == '\r')
+	|| (robotptr->buffer[next] == '\n'))
+      break;
+  }
+
+  if (next<robotptr->write) {
+    robotptr->buffer[next]=0;
+    next++;
+    parse_line(robotptr);
+    robotptr->read=next;
+    parse_data(robotptr);
+  }
+
+  if (robotptr->read == robotptr->write) {
+    robotptr->read=robotptr->write=0;
+  } else {
+    bcopy((robotptr->buffer + robotptr->read),
+	  (robotptr->buffer), (robotptr->write-robotptr->read));
+    robotptr->write-=robotptr->read;
+    robotptr->read=0;
+  }
+}
+
+void run_client(aClient *robotptr) {
+  fd_set mask, returnmask[3];
+  int selectval;
+
+  FD_ZERO(&mask);
+  FD_SET(robotptr->socket, &mask);
+
+  while (1) {
+    bcopy((char *)&mask,(char *)returnmask,sizeof(fd_set));
+    FD_ZERO(returnmask+1);
+    bcopy((char *)&mask,(char *)(returnmask+2),sizeof(fd_set));
+
+    selectval=select(FD_SETSIZE,
+		     returnmask, returnmask+1, returnmask+2, NULL);
+
+    if (selectval) {
+      read_data(robotptr);
+      parse_data(robotptr);
+    }
+  }
+}
+
+
+void initialize(aClient *robotptr) {
+  char passphrase[MYBUFSIZE];
+  robotptr->socket=create_client(uplinkservername, atol(jupereason));
+  sprintf(passphrase,
+	  "PROTOCTL %s %s %s %s %s %s %s %s %s\r\n", 
+	  	(options & 0x1) ? "NOQUIT" : "",
+	  	(options & 0x2) ? "TOKEN" : "",
+	  	(options & 0x4) ? "NICKv2" : "",
+	  	(options & 0x8) ? "SJOIN" : "",
+	  	(options & 0x10) ? "SJOIN2" : "",
+	  	(options & 0x20) ? "UMODE2" : "",
+	  	(options & 0x40) ? "NS" : "",
+	  	(options & 0x100) ? "SJ3" : "",
+	  	(options & 0x200) ? "SJB64" : "");
+  write(robotptr->socket, passphrase, strlen(passphrase));
+  sprintf(passphrase, "PASS %s\r\nSERVER %s 1 :[Burst analysis].\r\n",
+	  password,jupedservername);
+  write(robotptr->socket, passphrase, strlen(passphrase));
+}
+
+void fatalrestart(aClient *robotptr, const char *s) {
+  perror(s);
+  close(robotptr->socket);
+  sleep(10);
+  initialize(robotptr);
+  run_client(robotptr);
+}
+
+int main(int argc, char* argv[]) {
+  aClient robot;
+  char *p;
+  
+  if (argc != 6) {
+    fprintf(stderr, "IRCd burst generator, by Carsten V. Munk 2000, based off jupe.c by Nicolas Pioch\n");
+    fprintf(stderr,
+	    "Usage: %s <burstservername> <uplink> <port> <options> <password>\n", argv[0]);
+    fprintf(stderr, "Options can be a combination of these:\n");
+    fprintf(stderr, "1 = Enable NOQUIT  2 = Enable TOKEN\n");
+    fprintf(stderr, "3 = Enable NICKv2  4 = Enable SJOIN\n");
+    fprintf(stderr, "5 = Enable SJOIN2  6 = Enable UMODE2\n");
+    fprintf(stderr, "7 = Enable NS      8 = Ignore end of burst\n");
+    fprintf(stderr, "9 = Enable SJ3     a = Enable SJB64\n");
+    fatal("incorrect argument count");
+    exit(1);
+  }
+  
+  jupedservername=argv[1];
+  uplinkservername=argv[2];
+  jupereason=argv[3];
+  password = argv[5];
+  p = argv[4];
+  for (; *p; p++)
+  {
+  	if (*p == '1')
+  		options |= 0x1;
+  	if (*p == '2')
+  		options |= 0x2;
+  	if (*p == '3')
+  		options |= 0x4;
+  	if (*p == '4')
+  		options |= 0x8;
+  	if (*p == '5')
+  		options |= 0x10;
+  	if (*p == '6')
+  		options |= 0x20;
+	if (*p == '7') 
+		options |= 0x40;
+	if (*p == '8') 
+		options |= 0x80;
+	if (*p == '9')
+		options |= 0x100;
+	if (*p == 'a')
+		options |= 0x200;
+  }
+  /* installe le signal_catcher */
+  signal(SIGTERM,(signalhandler)signal_catcher);
+
+  robot.read=robot.write=0;
+
+  initialize(&robot);
+  run_client(&robot);
+
+  exit(0);
+}

extras/channeldumper.c

@@ -0,0 +1,128 @@
+/*
+ *   IRC - Internet Relay Chat, src/modules/channeldumper.c
+ *   (C) 2002 Carsten V. Munk <stskeeps@tspre.org>
+ *
+ *
+ *   See file AUTHORS in IRC package for additional names of
+ *   the programmers.
+ *
+ *   This program is free software; you can redistribute it and/or modify
+ *   it under the terms of the GNU General Public License as published by
+ *   the Free Software Foundation; either version 1, or (at your option)
+ *   any later version.
+ *
+ *   This program is distributed in the hope that it will be useful,
+ *   but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *   GNU General Public License for more details.
+ *
+ *   You should have received a copy of the GNU General Public License
+ *   along with this program; if not, write to the Free Software
+ *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ */
+#include "config.h"
+#include "struct.h"
+#include "common.h"
+#include "sys.h"
+#include "numeric.h"
+#include "msg.h"
+#include "channel.h"
+#include <time.h>
+#include <sys/stat.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#ifdef _WIN32
+#include <io.h>
+#endif
+#include <fcntl.h>
+#include "h.h"
+#include "proto.h"
+#ifdef STRIPBADWORDS
+#include "badwords.h"
+#endif
+#ifdef _WIN32
+#include "version.h"
+#endif
+
+#ifndef DYNAMIC_LINKING
+ModuleHeader channeldumper_Header
+#else
+#define channeldumper_Header Mod_Header
+ModuleHeader Mod_Header
+#endif
+  = {
+	"channeldumper",
+	"$Id$",
+	"Channel dump to text timed", 
+	"3.2-b8-1",
+	NULL 
+    };
+
+static ModuleInfo	ChannelDumperModInfo;
+
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Init(ModuleInfo *modinfo)
+#else
+int    channeldumper_Init(ModuleInfo *modinfo)
+#endif
+{
+	tainted++;
+	bcopy(modinfo,&ChannelDumperModInfo, modinfo->size);
+	return MOD_SUCCESS;
+}
+
+EVENT(e_channeldump);
+static Event *ChannelDumpEvent = NULL;
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Load(int module_load)
+#else
+int    channeldumper_Load(int module_load)
+#endif
+{
+	LockEventSystem();
+	ChannelDumpEvent = EventAddEx(ChannelDumperModInfo.handle, "e_channeldump", 5, 0, e_channeldump, NULL);
+	UnlockEventSystem();
+	return MOD_SUCCESS;
+}
+
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Unload(int module_unload)
+#else
+int	channeldumper_Unload(int module_unload)
+#endif
+{
+	tainted--;
+	LockEventSystem();
+	EventDel(ChannelDumpEvent);
+	UnlockEventSystem();
+	return MOD_SUCCESS;
+}
+
+EVENT(e_channeldump)
+{
+	aChannel *chptr;
+	unsigned int hashnum;
+	Member	*m;
+	FILE	*f;
+	
+	f = fopen("ircd.channeldump", "w");
+	if (!f)
+		return;
+	for (hashnum = 0; hashnum < CH_MAX; hashnum++)
+	{
+		for (chptr = (aChannel *)hash_get_chan_bucket(hashnum); chptr; chptr
+			= chptr->hnextch)
+		{
+			if (SecretChannel(chptr))
+				continue;
+		 	fprintf(f, "C %s %s\r\n", 
+		 		chptr->chname, chptr->topic ? chptr->topic : "");
+			for (m = chptr->members; m; m = m->next)
+				fprintf(f, "M %s\r\n",
+					m->cptr->name);   			
+		}
+	}
+	fclose(f);
+	return;
+}

extras/defizzer.c

@@ -0,0 +1,128 @@
+/*
+ * Defizzer, 3rd party module for Unreal3.2-beta15 and up
+ * (C) Carsten V. Munk 2003 <stskeeps@tspre.org>
+ * You can do everything you desire with this module, under the condition that if you 
+ * meet the author, you must buy him a drink of his choice.
+ * Copyright notice must ALWAYS stay in place.
+ *
+ * Removes unidented fizzer clients from the network pre-local-connect
+*/
+#include "config.h"
+#include "struct.h"
+#include "common.h"
+#include "sys.h"
+#include "numeric.h"
+#include "msg.h"
+#include "channel.h"
+#include <time.h>
+#include <sys/stat.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#ifdef _WIN32
+#include <io.h>
+#endif
+#include <fcntl.h>
+#include "h.h"
+#ifdef STRIPBADWORDS
+#include "badwords.h"
+#endif
+#ifdef _WIN32
+#include "version.h"
+#endif
+DLLFUNC int h_defizzer_connect(aClient *sptr);
+
+static Hook *LocConnect = NULL;
+ModuleInfo DefizzerModInfo;
+
+ModuleHeader MOD_HEADER(defizzer)
+  = {
+	"defizzer",	/* Name of module */
+	"$Id$", /* Version */
+	"de-Fizzer", /* Short description of module */
+	"3.2-b8-1",
+	NULL 
+    };
+
+DLLFUNC int MOD_INIT(defizzer)(ModuleInfo *modinfo)
+{
+	bcopy(modinfo,&DefizzerModInfo,modinfo->size);
+	LocConnect = HookAddEx(DefizzerModInfo.handle, HOOKTYPE_PRE_LOCAL_CONNECT, h_defizzer_connect);
+	return MOD_SUCCESS;
+}
+
+DLLFUNC int MOD_LOAD(defizzer)(int module_load)
+{
+	return MOD_SUCCESS;
+}
+
+
+DLLFUNC int MOD_UNLOAD(defizzer)(int module_unload)
+{
+	HookDel(LocConnect);
+	return MOD_SUCCESS;
+}
+
+static void ban_fizzer(aClient *cptr)
+{
+	int i;
+	aClient *acptr;
+	char hostip[128], mo[100], mo2[100];
+	char *tkllayer[9] = {
+		me.name,	/*0  server.name */
+		"+",		/*1  +|- */
+		"z",		/*2  G   */
+		"*",		/*3  user */
+		NULL,		/*4  host */
+		NULL,
+		NULL,		/*6  expire_at */
+		NULL,		/*7  set_at */
+		NULL		/*8  reason */
+	};
+
+	strlcpy(hostip, Inet_ia2p(&cptr->ip), sizeof(hostip));
+
+	tkllayer[4] = hostip;
+	tkllayer[5] = me.name;
+	ircsprintf(mo, "%li", 86400 + TStime());
+	ircsprintf(mo2, "%li", TStime());
+	tkllayer[6] = mo;
+	tkllayer[7] = mo2;
+	tkllayer[8] = "Fizzer";
+	m_tkl(&me, &me, 9, tkllayer);
+	return;
+}
+
+DLLFUNC int h_defizzer_connect(aClient *sptr)
+{
+	char user[USERLEN + 1];
+	char *infobackup;
+	char *s1, *s2;
+
+	/*
+	 * Algorithm is basically like this, inspired by Zaphod:
+	 * Exchange first word with second in realname, prepend with 
+	 * ~, then add in second word and first word upto limit of username.
+	 * sounds fun?
+	*/
+	infobackup = strdup(sptr->info);
+	if (!(s1 = strtok(infobackup, " ")))
+	{
+		free(infobackup);
+		return 0;
+	}		
+	if (!(s2 = strtok(NULL, " ")))
+	{
+		free(infobackup);
+		return 0;
+	}		
+	snprintf(user, sizeof(user), "%s%s%s", (IDENT_CHECK ? "~" : ""), s2, s1);
+	free(infobackup);	
+	if (!strcmp(user, sptr->user->username))
+	{
+		ircstp->is_ref++;
+		ban_fizzer(sptr);			
+		return exit_client(sptr, sptr, &me, "Fizzer client");
+	}	
+	return 0;
+}

extras/extras.txt

@@ -1 +1,43 @@
-...
+
+These are 3rd party programs modules, or unsupported modules.
+
+Custom modules are compiled by copying them to src/modules
+and running from the root directory
+
+$ make custommodule MODULEFILE=modulename
+
+This will produce a .so you can load. Upon load, this will show a "3" in the
+/version flags, as it contains third party modules (we do not support if it
+crashes because of the tainted module)
+
+======================
+Name: burst.c
+Description:
+Little program to test out the different aspects of the unreal protocol and
+produce net.burst dumps
+
+=======================
+Name: m_rawto.c
+Is a 3rd party module
+Description:
+
+Implements the RAWTO command, will allow U:lines to send raw data to
+anywhere it pleases. 
+
+:uline.server RAWTO towho :what to send
+
+=========================
+
+Name: channeldumper.c
+Is a 3rd party module
+Description:
+
+Dumps a list of non secret channels to ircd.channels or something every 5 seconds,
+
+C #channel topic
+M member1
+M member2
+C #channel2 topic
+M member3
+
+You can't rely on topic being there

extras/m_rawto.c

@@ -0,0 +1,157 @@
+/*
+ *   Unreal Internet Relay Chat Daemon, m_rawto.c
+ *   (C) 2002 Carsten V. Munk
+ *   RAWTO Module - 3rd party
+ *
+ *   This program is free software; you can redistribute it and/or modify
+ *   it under the terms of the GNU General Public License as published by
+ *   the Free Software Foundation; either version 1, or (at your option)
+ *   any later version.
+ *
+ *   This program is distributed in the hope that it will be useful,
+ *   but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *   GNU General Public License for more details.
+ *
+ *   You should have received a copy of the GNU General Public License
+ *   along with this program; if not, write to the Free Software
+ *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ * 
+ *   Use of this module will make it a 3rd party module, and will
+ *   add to your /version thing. We DO NOT SUPPORT THIS.
+ */
+
+#include "config.h"
+#include "struct.h"
+#include "common.h"
+#include "sys.h"
+#include "numeric.h"
+#include "msg.h"
+#include "channel.h"
+#include <time.h>
+#include <sys/stat.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#ifdef _WIN32
+#include <io.h>
+#endif
+#include <fcntl.h>
+#include "h.h"
+#include "proto.h"
+#ifdef STRIPBADWORDS
+#include "badwords.h"
+#endif
+#ifdef _WIN32
+#include "version.h"
+#endif
+
+DLLFUNC int m_rawto(aClient *cptr, aClient *sptr, int parc, char *parv[]);
+
+/* Place includes here */
+#define MSG_RAWTO       "RAWTO" /*  */
+#define TOK_RAWTO       "3A"     /* 112 */
+
+
+#ifndef DYNAMIC_LINKING
+ModuleHeader m_rawto_Header
+#else
+#define m_rawto_Header Mod_Header
+ModuleHeader Mod_Header
+#endif
+  = {
+	"rawto",	/* Name of module */
+	"$Id$", /* Version */
+	"command /rawto", /* Short description of module */
+	"3.2-b5",
+	NULL 
+    };
+
+
+/* The purpose of these ifdefs, are that we can "static" link the ircd if we
+ * want to
+*/
+
+/* This is called on module init, before Server Ready */
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Init(int module_load)
+#else
+int    m_rawto_Init(int module_load)
+#endif
+{
+	/*
+	 * We call our add_Command crap here
+	*/
+	add_Command(MSG_RAWTO, TOK_RAWTO, m_rawto, 2);
+	tainted++;
+	return MOD_SUCCESS;
+}
+
+/* Is first run when server is 100% ready */
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Load(int module_load)
+#else
+int    m_rawto_Load(int module_load)
+#endif
+{
+	
+	return MOD_SUCCESS;
+}
+
+
+/* Called when module is unloaded */
+#ifdef DYNAMIC_LINKING
+DLLFUNC int	Mod_Unload(int module_unload)
+#else
+int	m_rawto_Unload(int module_unload)
+#endif
+{
+	if (del_Command(MSG_RAWTO, TOK_RAWTO, m_rawto) < 0)
+	{
+		sendto_realops("Failed to delete commands when unloading %s",
+				m_rawto_Header.name);
+	}
+	tainted--;
+	return MOD_SUCCESS;
+}
+
+
+/*
+ *  m_rawto                      Send a raw string to anywhere
+ *                               if you are U:line
+ *    parv[0] = sender prefix
+ *    parv[1] = whoto
+ *    parv[2] = string
+ */
+
+DLLFUNC int m_rawto(aClient *cptr, aClient *sptr, int parc, char *parv[])
+{
+	aClient *acptr = NULL;
+	if (!IsULine(sptr))
+	{
+		sendto_one(sptr, err_str(ERR_NOPRIVILEGES), me.name, parv[0]);
+		return -1;
+	}
+	if (parc < 3)
+	{
+		sendto_one(sptr, err_str(ERR_NEEDMOREPARAMS),
+		    me.name, parv[0], "RAWTO");
+		return -1;
+	}
+	if ((acptr = find_client(parv[1], NULL)))
+	{
+		if (MyConnect(acptr))
+		{
+			sendto_one(acptr, "%s", parv[2]);
+			return 0;
+		}		
+		else
+		{
+			sendto_one(acptr, ":%s %s %s :%s",
+				parv[0], IsToken(acptr->from) ? TOK_RAWTO : MSG_RAWTO,
+					parv[1], parv[2]);
+			return 0;
+		}
+	}
+	return 0;
+}

extras/regex/Makefile.in

@@ -0,0 +1,98 @@
+# Makefile for regex.
+# 
+# Copyright (C) 1992, 1993 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+version = 0.12
+
+# You can define CPPFLAGS on the command line.  Aside from system-specific
+# flags, you can define:
+#   -DREGEX_MALLOC to use malloc/realloc/free instead of alloca.
+#   -DDEBUG to enable the compiled pattern disassembler and execution
+#           tracing; code runs substantially slower.
+#   -DEXTRACT_MACROS to use the macros EXTRACT_* (as opposed to
+#           the corresponding C procedures).  If not -DDEBUG, the macros
+#           are used.
+CPPFLAGS = 
+
+# Likewise, you can override CFLAGS to optimize, use -Wall, etc.
+CFLAGS = -g
+
+# Ditto for LDFLAGS and LOADLIBES.
+LDFLAGS =
+LOADLIBES =
+
+srcdir = @srcdir@
+VPATH = @srcdir@
+
+CC = @CC@
+DEFS = @DEFS@
+
+SHELL = /bin/sh
+
+subdirs = moo
+
+default all:: regex.o
+.PHONY: default all
+
+regex.o: regex.c regex.h
+	$(CC) $(CFLAGS) $(CPPFLAGS) $(DEFS) -I. -I$(srcdir) -c $<
+
+clean mostlyclean::
+	rm -f *.o
+
+distclean:: clean
+	rm -f Makefile config.status
+
+extraclean:: distclean
+	rm -f patch* *~* *\#* *.orig *.rej *.bak core a.out
+
+configure: configure.in
+	autoconf
+
+config.status: configure
+	sh configure --no-create
+
+Makefile: Makefile.in config.status
+	sh config.status
+
+makeargs = $(MFLAGS) CPPFLAGS='$(CPPFLAGS)' CFLAGS='$(CFLAGS)' CC='$(CC)' \
+DEFS='$(DEFS)' LDFLAGS='$(LDFLAGS)' LOADLIBES='$(LOADLIBES)'
+
+default all install \
+mostlyclean clean distclean extraclean realclean \
+TAGS check::
+	for d in $(subdirs); do (cd $$d; $(MAKE) $(makeargs) $@); done
+.PHONY: install mostlyclean clean distclean extraclean realclean TAGS check
+
+# Prevent GNU make 3 from overflowing arg limit on system V.
+.NOEXPORT:
+
+distfiles = AUTHORS ChangeLog COPYING INSTALL NEWS README \
+            *.in configure regex.c regex.h 
+distdir = regex-$(version)
+distargs = version=$(version) distdir=../$(distdir)/$$d
+dist: TAGS configure
+	@echo "Version numbers in: Makefile.in, ChangeLog, NEWS,"
+	@echo "  regex.c, regex.h,"
+	@echo "  and doc/xregex.texi (if modified)."
+	rm -rf $(distdir)
+	mkdir $(distdir)
+	ln $(distfiles) $(distdir)
+	for d in $(subdirs); do (cd $$d; $(MAKE) $(distargs) dist); done
+	tar czhf $(distdir).tar.Z $(distdir)
+	rm -rf $(distdir)
+.PHONY: dist

extras/regex/README

@@ -0,0 +1,60 @@
+This directory contains the GNU regex library.  It is compliant with
+POSIX.2, except for internationalization features.
+
+See the file NEWS for a list of major changes in the current release.
+
+See the file INSTALL for compilation instructions.  (The only thing
+installed is the documentation; regex.c is compiled into regex.o, but
+not installed anywhere.)
+
+The subdirectory `doc' contains a (programmers') manual for the library.
+It's probably out-of-date.  Improvements are welcome.
+
+The subdirectory `test' contains the various tests we've written.
+
+We know this code is not as fast as it might be.  If you have specific
+suggestions, profiling results, or other such useful information to
+report, please do.
+
+Emacs 18 is not going use this revised regex (but Emacs 19 will).  If
+you want to try it with Emacs 18, apply the patch at the end of this
+file first.
+
+Mail bug reports to bug-gnu-utils@prep.ai.mit.edu.
+
+Please include an actual regular expression that fails (and the syntax
+used to compile it); without that, there's no way to reproduce the bug,
+so there's no way we can fix it.  Even if you include a patch, also
+include the regular expression in error; otherwise, we can't know for
+sure what you're trying to fix.
+
+Here is the patch to make this version of regex work with Emacs 18.
+
+*** ORIG/search.c	Tue Jan  8 13:04:55 1991
+--- search.c	Sun Jan  5 10:57:00 1992
+***************
+*** 25,26 ****
+--- 25,28 ----
+  #include "commands.h"
++ 
++ #include <sys/types.h>
+  #include "regex.h"
+***************
+*** 477,479 ****
+  				/* really needed. */
+!       && *(searchbuf.buffer) == (char) exactn /* first item is "exact match" */
+        && searchbuf.buffer[1] + 2 == searchbuf.used) /*first is ONLY item */
+--- 479,482 ----
+  				/* really needed. */
+!          /* first item is "exact match" */
+!       && *(searchbuf.buffer) == (char) RE_EXACTN_VALUE
+        && searchbuf.buffer[1] + 2 == searchbuf.used) /*first is ONLY item */
+***************
+*** 1273,1275 ****
+    searchbuf.allocated = 100;
+!   searchbuf.buffer = (char *) malloc (searchbuf.allocated);
+    searchbuf.fastmap = search_fastmap;
+--- 1276,1278 ----
+    searchbuf.allocated = 100;
+!   searchbuf.buffer = (unsigned char *) malloc (searchbuf.allocated);
+    searchbuf.fastmap = search_fastmap;

extras/regex/configure

@@ -0,0 +1,462 @@
+#!/bin/sh
+# Guess values for system-dependent variables and create Makefiles.
+# Generated automatically using autoconf.
+# Copyright (C) 1991, 1992, 1993 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+# Usage: configure [--srcdir=DIR] [--host=HOST] [--gas] [--nfp] [--no-create]
+#        [--prefix=PREFIX] [--exec-prefix=PREFIX] [--with-PACKAGE] [TARGET]
+# Ignores all args except --srcdir, --prefix, --exec-prefix, --no-create, and
+# --with-PACKAGE unless this script has special code to handle it.
+
+
+for arg
+do
+  # Handle --exec-prefix with a space before the argument.
+  if test x$next_exec_prefix = xyes; then exec_prefix=$arg; next_exec_prefix=
+  # Handle --host with a space before the argument.
+  elif test x$next_host = xyes; then next_host=
+  # Handle --prefix with a space before the argument.
+  elif test x$next_prefix = xyes; then prefix=$arg; next_prefix=
+  # Handle --srcdir with a space before the argument.
+  elif test x$next_srcdir = xyes; then srcdir=$arg; next_srcdir=
+  else
+    case $arg in
+     # For backward compatibility, also recognize exact --exec_prefix.
+     -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* | --exec=* | --exe=* | --ex=* | --e=*)
+	exec_prefix=`echo $arg | sed 's/[-a-z_]*=//'` ;;
+     -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- | --exec | --exe | --ex | --e)
+	next_exec_prefix=yes ;;
+
+     -gas | --gas | --ga | --g) ;;
+
+     -host=* | --host=* | --hos=* | --ho=* | --h=*) ;;
+     -host | --host | --hos | --ho | --h)
+	next_host=yes ;;
+
+     -nfp | --nfp | --nf) ;;
+
+     -no-create | --no-create | --no-creat | --no-crea | --no-cre | --no-cr | --no-c | --no- | --no)
+        no_create=1 ;;
+
+     -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
+	prefix=`echo $arg | sed 's/[-a-z_]*=//'` ;;
+     -prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
+	next_prefix=yes ;;
+
+     -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=* | --s=*)
+	srcdir=`echo $arg | sed 's/[-a-z_]*=//'` ;;
+     -srcdir | --srcdir | --srcdi | --srcd | --src | --sr | --s)
+	next_srcdir=yes ;;
+
+     -with-* | --with-*)
+       package=`echo $arg|sed 's/-*with-//'`
+       # Delete all the valid chars; see if any are left.
+       if test -n "`echo $package|sed 's/[-a-zA-Z0-9_]*//g'`"; then
+         echo "configure: $package: invalid package name" >&2; exit 1
+       fi
+       eval "with_`echo $package|sed s/-/_/g`=1" ;;
+
+     *) ;;
+    esac
+  fi
+done
+
+trap 'rm -f conftest* core; exit 1' 1 3 15
+
+rm -f conftest*
+compile='${CC-cc} $CFLAGS $DEFS conftest.c -o conftest $LIBS >/dev/null 2>&1'
+
+# A filename unique to this package, relative to the directory that
+# configure is in, which we can look for to find out if srcdir is correct.
+unique_file=regex.c
+
+# Find the source files, if location was not specified.
+if test -z "$srcdir"; then
+  srcdirdefaulted=yes
+  # Try the directory containing this script, then `..'.
+  prog=$0
+  confdir=`echo $prog|sed 's%/[^/][^/]*$%%'`
+  test "X$confdir" = "X$prog" && confdir=.
+  srcdir=$confdir
+  if test ! -r $srcdir/$unique_file; then
+    srcdir=..
+  fi
+fi
+if test ! -r $srcdir/$unique_file; then
+  if test x$srcdirdefaulted = xyes; then
+    echo "configure: Can not find sources in \`${confdir}' or \`..'." 1>&2
+  else
+    echo "configure: Can not find sources in \`${srcdir}'." 1>&2
+  fi
+  exit 1
+fi
+# Preserve a srcdir of `.' to avoid automounter screwups with pwd.
+# But we can't avoid them for `..', to make subdirectories work.
+case $srcdir in
+  .|/*|~*) ;;
+  *) srcdir=`cd $srcdir; pwd` ;; # Make relative path absolute.
+esac
+
+
+if test -z "$CC"; then
+  echo checking for gcc
+  saveifs="$IFS"; IFS="${IFS}:"
+  for dir in $PATH; do
+    test -z "$dir" && dir=.
+    if test -f $dir/gcc; then
+      CC="gcc"
+      break
+    fi
+  done
+  IFS="$saveifs"
+fi
+test -z "$CC" && CC="cc"
+
+# Find out if we are using GNU C, under whatever name.
+cat > conftest.c <<EOF
+#ifdef __GNUC__
+  yes
+#endif
+EOF
+${CC-cc} -E conftest.c > conftest.out 2>&1
+if egrep yes conftest.out >/dev/null 2>&1; then
+  GCC=1 # For later tests.
+fi
+rm -f conftest*
+
+# Make sure to not get the incompatible SysV /etc/install and
+# /usr/sbin/install, which might be in PATH before a BSD-like install,
+# or the SunOS /usr/etc/install directory, or the AIX /bin/install,
+# or the AFS install, which mishandles nonexistent args.  (Sigh.)
+if test -z "$INSTALL"; then
+  echo checking for install
+  saveifs="$IFS"; IFS="${IFS}:"
+  for dir in $PATH; do
+    test -z "$dir" && dir=.
+    case $dir in
+    /etc|/usr/sbin|/usr/etc|/usr/afsws/bin) ;;
+    *)
+      if test -f $dir/install; then
+	if grep dspmsg $dir/install >/dev/null 2>&1; then
+	  : # AIX
+	else
+	  INSTALL="$dir/install -c"
+	  INSTALL_PROGRAM='$(INSTALL)'
+	  INSTALL_DATA='$(INSTALL) -m 644'
+	  break
+	fi
+      fi
+      ;;
+    esac
+  done
+  IFS="$saveifs"
+fi
+INSTALL=${INSTALL-cp}
+INSTALL_PROGRAM=${INSTALL_PROGRAM-'$(INSTALL)'}
+INSTALL_DATA=${INSTALL_DATA-'$(INSTALL)'}
+
+
+echo checking for AIX
+echo checking how to run the C preprocessor
+if test -z "$CPP"; then
+  CPP='${CC-cc} -E'
+  cat > conftest.c <<EOF
+#include <stdio.h>
+EOF
+err=`eval "$CPP $DEFS conftest.c 2>&1 >/dev/null"`
+if test -z "$err"; then
+  :
+else
+  CPP=/lib/cpp
+fi
+rm -f conftest*
+fi
+
+cat > conftest.c <<EOF
+#ifdef _AIX
+  yes
+#endif
+
+EOF
+eval "$CPP $DEFS conftest.c > conftest.out 2>&1"
+if egrep "yes" conftest.out >/dev/null 2>&1; then
+  DEFS="$DEFS -D_ALL_SOURCE=1"
+fi
+rm -f conftest*
+
+
+echo checking for DYNIX/ptx libseq
+cat > conftest.c <<EOF
+#if defined(_SEQUENT_)
+  yes
+#endif
+
+EOF
+eval "$CPP $DEFS conftest.c > conftest.out 2>&1"
+if egrep "yes" conftest.out >/dev/null 2>&1; then
+  SEQUENT=1
+fi
+rm -f conftest*
+
+test -n "$SEQUENT" && test -f /usr/lib/libseq.a &&
+  LIBS="$LIBS -lseq"
+
+echo checking for POSIXized ISC
+if test -d /etc/conf/kconfig.d &&
+  grep _POSIX_VERSION /usr/include/sys/unistd.h >/dev/null 2>&1
+then
+  ISC=1 # If later tests want to check for ISC.
+  DEFS="$DEFS -D_POSIX_SOURCE=1"
+  if test -n "$GCC"; then
+    CC="$CC -posix"
+  else
+    CC="$CC -Xp"
+  fi
+fi
+
+echo checking for minix/config.h
+cat > conftest.c <<EOF
+#include <minix/config.h>
+EOF
+err=`eval "$CPP $DEFS conftest.c 2>&1 >/dev/null"`
+if test -z "$err"; then
+  MINIX=1
+fi
+rm -f conftest*
+
+# The Minix shell can't assign to the same variable on the same line!
+if test -n "$MINIX"; then
+  DEFS="$DEFS -D_POSIX_SOURCE=1"
+  DEFS="$DEFS -D_POSIX_1_SOURCE=2"
+  DEFS="$DEFS -D_MINIX=1"
+fi
+
+
+echo checking for ANSI C header files
+cat > conftest.c <<EOF
+#include <stdlib.h>
+#include <stdarg.h>
+#include <string.h>
+#include <float.h>
+EOF
+err=`eval "$CPP $DEFS conftest.c 2>&1 >/dev/null"`
+if test -z "$err"; then
+  # SunOS string.h does not declare mem*, contrary to ANSI.
+echo '#include <string.h>' > conftest.c
+eval "$CPP $DEFS conftest.c > conftest.out 2>&1"
+if egrep "memchr" conftest.out >/dev/null 2>&1; then
+  # SGI's /bin/cc from Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
+cat > conftest.c <<EOF
+#include <ctype.h>
+#define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
+#define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
+#define XOR(e,f) (((e) && !(f)) || (!(e) && (f)))
+int main () { int i; for (i = 0; i < 256; i++)
+if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) exit(2);
+exit (0); }
+
+EOF
+eval $compile
+if test -s conftest && (./conftest; exit) 2>/dev/null; then
+  DEFS="$DEFS -DSTDC_HEADERS=1"
+fi
+rm -f conftest*
+fi
+rm -f conftest*
+
+fi
+rm -f conftest*
+
+for hdr in string.h
+do
+trhdr=HAVE_`echo $hdr | tr '[a-z]./' '[A-Z]__'`
+echo checking for ${hdr}
+cat > conftest.c <<EOF
+#include <${hdr}>
+EOF
+err=`eval "$CPP $DEFS conftest.c 2>&1 >/dev/null"`
+if test -z "$err"; then
+  DEFS="$DEFS -D${trhdr}=1"
+fi
+rm -f conftest*
+done
+
+
+# The Ultrix 4.2 mips builtin alloca declared by alloca.h only works
+# for constant arguments.  Useless!
+echo checking for working alloca.h
+cat > conftest.c <<EOF
+#include <alloca.h>
+main() { exit(0); } 
+t() { char *p = alloca(2 * sizeof(int)); }
+EOF
+if eval $compile; then
+  DEFS="$DEFS -DHAVE_ALLOCA_H=1"
+fi
+rm -f conftest*
+
+decl="#ifdef __GNUC__
+#define alloca __builtin_alloca
+#else
+#if HAVE_ALLOCA_H
+#include <alloca.h>
+#else
+#ifdef _AIX
+ #pragma alloca
+#else
+char *alloca ();
+#endif
+#endif
+#endif
+"
+echo checking for alloca
+cat > conftest.c <<EOF
+$decl
+main() { exit(0); } 
+t() { char *p = (char *) alloca(1); }
+EOF
+if eval $compile; then
+  :
+else
+  alloca_missing=1
+fi
+rm -f conftest*
+
+if test -n "$alloca_missing"; then
+  # The SVR3 libPW and SVR4 libucb both contain incompatible functions
+  # that cause trouble.  Some versions do not even contain alloca or
+  # contain a buggy version.  If you still want to use their alloca,
+  # use ar to extract alloca.o from them instead of compiling alloca.c.
+  ALLOCA=alloca.o
+fi
+
+prog='/* Ultrix mips cc rejects this.  */
+typedef int charset[2]; const charset x;
+/* SunOS 4.1.1 cc rejects this. */
+char const *const *p;
+char **p2;
+/* HPUX 7.0 cc rejects these. */
+++p;
+p2 = (char const* const*) p;'
+echo checking for working const
+cat > conftest.c <<EOF
+
+main() { exit(0); } 
+t() { $prog }
+EOF
+if eval $compile; then
+  :
+else
+  DEFS="$DEFS -Dconst="
+fi
+rm -f conftest*
+
+
+if test -z "$prefix"
+then
+  echo checking for gcc to derive installation directory prefix
+  saveifs="$IFS"; IFS="$IFS:"
+  for dir in $PATH; do
+    test -z "$dir" && dir=.
+    if test $dir != . && test -f $dir/gcc; then
+      # Not all systems have dirname.
+      prefix=`echo $dir|sed 's%/[^/][^/]*$%%'`
+      break
+    fi
+  done
+  IFS="$saveifs"
+fi
+
+
+if test -n "$prefix"; then
+  test -z "$exec_prefix" && exec_prefix='${prefix}'
+  prsub="s%^prefix\\([ 	]*\\)=\\([ 	]*\\).*$%prefix\\1=\\2$prefix%"
+fi
+if test -n "$exec_prefix"; then
+  prsub="$prsub
+s%^exec_prefix\\([ 	]*\\)=\\([ 	]*\\).*$%\
+exec_prefix\\1=\\2$exec_prefix%"
+fi
+
+trap 'rm -f config.status; exit 1' 1 3 15
+echo creating config.status
+rm -f config.status
+cat > config.status <<EOF
+#!/bin/sh
+# Generated automatically by configure.
+# Run this file to recreate the current configuration.
+# This directory was configured as follows,
+# on host `(hostname || uname -n) 2>/dev/null`:
+#
+# $0 $*
+
+for arg
+do
+  case "\$arg" in
+    -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
+    exec /bin/sh $0 $* ;;
+    *) echo "Usage: config.status --recheck" 2>&1; exit 1 ;;
+  esac
+done
+
+trap 'rm -f Makefile; exit 1' 1 3 15
+CC='$CC'
+INSTALL='$INSTALL'
+INSTALL_PROGRAM='$INSTALL_PROGRAM'
+INSTALL_DATA='$INSTALL_DATA'
+CPP='$CPP'
+ALLOCA='$ALLOCA'
+LIBS='$LIBS'
+srcdir='$srcdir'
+DEFS='$DEFS'
+prefix='$prefix'
+exec_prefix='$exec_prefix'
+prsub='$prsub'
+EOF
+cat >> config.status <<\EOF
+
+top_srcdir=$srcdir
+for file in .. Makefile; do if [ "x$file" != "x.." ]; then
+  srcdir=$top_srcdir
+  # Remove last slash and all that follows it.  Not all systems have dirname.
+  dir=`echo $file|sed 's%/[^/][^/]*$%%'`
+  if test "$dir" != "$file"; then
+    test "$top_srcdir" != . && srcdir=$top_srcdir/$dir
+    test ! -d $dir && mkdir $dir
+  fi
+  echo creating $file
+  rm -f $file
+  echo "# Generated automatically from `echo $file|sed 's|.*/||'`.in by configure." > $file
+  sed -e "
+$prsub
+s%@CC@%$CC%g
+s%@INSTALL@%$INSTALL%g
+s%@INSTALL_PROGRAM@%$INSTALL_PROGRAM%g
+s%@INSTALL_DATA@%$INSTALL_DATA%g
+s%@CPP@%$CPP%g
+s%@ALLOCA@%$ALLOCA%g
+s%@LIBS@%$LIBS%g
+s%@srcdir@%$srcdir%g
+s%@DEFS@%$DEFS%
+" $top_srcdir/${file}.in >> $file
+fi; done
+
+exit 0
+EOF
+chmod +x config.status
+test -n "$no_create" || ./config.status
+

extras/regex/configure.in

@@ -0,0 +1,23 @@
+dnl Process this file with autoconf to produce a configure script.
+AC_INIT(regex.c)
+
+AC_PROG_CC
+AC_PROG_INSTALL
+
+dnl I'm not sure if AC_AIX and AC_DYNIX_SEQ are really necessary.  The
+dnl Autoconf documentation isn't specific about which BSD functions they
+dnl provide.
+AC_AIX
+AC_DYNIX_SEQ
+AC_ISC_POSIX
+AC_MINIX
+
+AC_STDC_HEADERS
+AC_HAVE_HEADERS(string.h)
+
+AC_ALLOCA
+AC_CONST
+
+AC_PREFIX(gcc)
+
+AC_OUTPUT(Makefile doc/Makefile test/Makefile)

extras/regex/moo/Makefile

@@ -0,0 +1,4 @@
+clean:
+default:
+all:
+	echo "."