fixup commit for branch 'experimentalweirdnes'

+- Removed unrealircd.conf from stock

.CHANGES.NEW

@@ -1,20 +1,18 @@
-
- _   _                      _ ___________  _____     _
-| | | |                    | |_   _| ___ \/  __ \   | |
-| | | |_ __  _ __ ___  __ _| | | | | |_/ /| /  \/ __| |
-| | | | '_ \| '__/ _ \/  _ | | | | |    / | |    /  _ |
-| |_| | | | | | |  __/ (_| | |_| |_| |\ \ | \__/\ (_| |
- \___/|_| |_|_|  \___|\__,_|_|\___/\_| \_| \____/\__,_|
-
-                               Configuration Program
-                                for Unreal3.2
-                                    
-This program will help you to compile your IRC server, and ask you
-questions regarding the compile-time settings of it during the process. 
+Welcome to the UnrealIRCd configuration program. This program
+will help you to compile your IRC server, and ask you questions
 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
+If you need help to set the IRCd up, mail
+unreal-support@lists.sourceforge.net or ask at IRC:
+/server irc.ircsystems.net, /join #unrealircd
 
+For any sake, read Unreal.nfo and read doc/faq before asking questions
+ 
+NOTE: If the code is changed in any way, or the version string is changed, 
+      we do _NOT_ support the product, except if you got explicit permission
+      from one of the UnrealIRCd coders. If it fails and you messed with it, 
+      you can't blame noone but yourself. Also, non-official UnrealIRCd/32 
+      builds (if it doesn't say "geniune" in the display) are _NOT_
+      supported.
+
+-Stskeeps (Head coder of UnrealIRCd)

.CONFIG.RANT

@@ -1,35 +0,0 @@
-
-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

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

.RELEASE.NOTES

@@ -1,50 +1,23 @@
 
-Unreal3.2 Release Notes
-========================
+Unreal3.1.1-Darkshades Release Notes
+===================================
 
-==[ GENERAL INFORMATION ]==
-* If you are upgrading, make sure you run make clean and ./Config before doing make
-* The official UnrealIRCd documentation is doc/unreal32docs.html
-  online version at: http://www.vulnscan.org/UnrealIrcd/unreal32docs.html
-  FAQ: http://www.vulnscan.org/UnrealIrcd/faq/
-  Read them before asking for help.
-* Report bugs at http://bugs.unrealircd.org/
+* It is REALLY RECOMMENDED that you run only Unreal3.1.1<->Unreal3.1.1,
+  as Unreal3.1+sf got some funny SJOIN bugs that causes the network to
+  desynch
 
-== [ NEW ]==
-- Added german docs (doc/unreal32docs.de.html)
-- In a spamfilter reason field '_' gets converted to a space (' '),
-  now also added '__' which gets converted to underscore itself ('_').
+* It is ADVISABLE that you allocate numerics to each server on your network.
+  You simply in the M: line, just after the port, add :numeric, like:
+  
+   M:irc.fyremoon.net:*:Description:6667:20
 
-==[ MAJOR BUGS FIXED ]==
-- '/spamfiltere remove' was often removing the wrong entry (RC2 bug)
-- The TRE regex library was sometimes matching too much if [range].+
-  was used multiple times.
-- Fixed a remote include issue and added timeouts in case a connection/transfer fails
+  Where 20 is the numeric. Numerics are 1-255, 0 means no numeric (bad),
+  and no server must have same numeric
 
-==[ MINOR BUGS FIXED ]==
-- Sometimes hosts were not resolved on Windows due to a resolver bug
-- spamfilter and sqline: memory leak on /rehash (a few kb)
-- spamfilter: protect against insane long reason/regex fields in configfile
-- set::modes-on-join now accepts extended channelmodes
-- Opteron: various crashbugs fixed, should work ok now.
-- Win32 GUI "rehash all" option did not reload motd/rules.
-- Same for ./unreal rehash on *NIX
-- Usermode 'r' (registered) was unset if you changed the case of your
-  nick (eg: 'blah'->'Blah'), this affected at least ircservices.
-- vhost::swhois wasn't shown if you did a remote /whois.
-- Made './curlinstall' work with new c-ares-1.0.0.
-- Fixed compile problem on some machines related to TRE / libintl.
-- /who +m was incorrectly hiding +H users even for opers.
-- Fixed /rehash bug if an .so or remote include didn't load properly
+* We have introduced encrypted irc connections, using SSL
+      You need to set up a SSL port, P:IP:s:*:port
+      To connect securely to another server, add :S at the end of the C:line
+       and make sure it autoconnect/connects to a SSL port
 
-==[ CHANGED ]==
-- spamfilter.conf: fixed fyle sig, added sigs for: soex, Nkie, LOI, Gaggle,
-  changed a lot of sigs from block to gline.
-- Windows: now using new Inno Setup which made the installer 300k smaller
-- Docs, help.conf and other text updates.
-
-==[ COMMING UP ]==
-- You can expect module support on windows in a nearby release.
-
-==[ ADDITIONAL INFO ]==
-* See Changelog
+* Read Unreal.nfo for any sake AND THE DOCS IN doc/. To update/upgrade your IRCd,
+  please run the ./update script. This requires "wget" and "cvs" on the box to function

.SICI

@@ -4,12 +4,17 @@
 | 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.                                          |
+| A initiative have been started, to help this problem, as more and more  |
+| SSL-enabled IRC servers will be started in the future, and people will  |
+| have trouble authenticating that they are really at the right server.   |
+| This initiative is called SICI (Secure IRC Certification Initiative. We |
+| sign your certificates for free, using the simple way of authenticating |
+| you by going to your IRC server and testing if it's really you.         |
 |                                                                         |
-| To get a free signed certificate please visit http://www.CACert.org     |
-|                                                _________________________|
-| 	                                       	| Press enter to continue |
+| You can send in your "server.req.pem" file to us at our email           |
+| certs@sici.ircsystems.net, with contact info on you (IRC network, nick, |
+| status). We will then contact you, and check if you have provided true  |
+| information. If you need more information about SICI, visit our website |
+| http://sici.ircsystems.net, where you can download our root certificate,|
+| and read even more about this project.        | Press enter to continue |
 ---------------------------------------------------------------------------
-

.bugreport.gdb

@@ -1,77 +0,0 @@
-#
-# 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

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

CREDITS.potential

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

Donation

@@ -1,32 +1,15 @@
-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.com&
-item_name=UnrealIRCd+Donation&no_shipping=1&cn=Comments&tax=0&currency_code=USD>
-
-Or simply send a payment through PayPal to:
-donation@unrealircd.com
-
-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:
 
+Send donations to:
+------------------
 UnrealIRCd Project
 C/O Carsten Munk
 P.O.Box 52
 7400 Herning
 Denmark
 
-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. 
+(if you want to that is .. it will just make us a little more able to code
+even more on this project. You will get in /credits if you do so). 
 
-Thank you for your support,
-The UnrealIRCd Team
+-- Stskeeps
 
 [ $Id$ ]

INSTALL

@@ -0,0 +1,99 @@
+###############################################################################
+####               Unreal IRC Unix Daemon Installation Guide               ####
+####                         UnrealIRCD ver 3.1.1                          ####
+####                    unreal-dev@lists.sourceforge.com                   ####
+####                      http://www.unrealircd.com/                       ####
+###############################################################################
+####                       Unpackaging the IRCD                            ####
+####                                                                       ####
+####   1) gzip -d Unreal3.1.1.tar.gz                                       ####
+####                                                                       ####
+####   2) tar xvf Unreal3.1.1.tar                                          ####
+####                                                                       ####
+####   3) cd Unreal3.1.1/                                                  ####
+###############################################################################
+####                        Compiling the IRCD                             ####
+####                                                                       ####
+####   1) Supported Operating Systems                                      ####
+####                                                                       ####
+####   OS and Version     Compiler and Version           Comments          ####
+####   --------------- ------------------------ ------------------------   ####
+####   NetBSD 1.2B       gcc 2.7.2                                         ####
+####   FreeBSD 2.1.0     gcc 2.6.3                Don't 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                                       ####
+####   PUX 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                 ####
+####   Linux 2.3.x       gcc 2.95.2               glibc 2.1.3              ####
+####                                                                       ####
+####   2) DO NOT edit the MakeFile or any of the files to configure your   ####
+####      IRCd. The newest releases of Unreal only require you to run:     ####
+####                                                                       ####
+####      ./Config                                                         ####
+####                                                                       ####
+####   2a) Windows users: please read WIN32                                ####
+####                                                                       ####
+####   3) When in ./Config put in the best answers to your knowledge.      ####
+####      This is all pretty self explanatory. We suggest, to advoid       ####
+####      problems later on, put the DPATH and SPATH as the default.       ####
+####      (When it asks where the config files and binarys will be).       ####
+####      Also, when it asks for max file connections, the default is      ####
+####      1024, but above it you will see what your true limit is.         ####
+####      Please put the maxfd number in or else your IRCD will not        ####
+####      start at all and you will have to re-compile.                    ####
+####                                                                       ####
+####   4) make                                                             ####
+####      This will compile your server based on you settings chosen in    ####
+####      ./Config                                                         ####
+####                                                                       ####
+####   4a) 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. Another suggestion is going on IRC    ####
+####       /server irc.ircsystems.net #UnrealIRCD                          ####
+####                                                                       ####
+####   4b) make install  - IS NOT NEEDED                                   ####
+####                                                                       ####
+###############################################################################
+####                     Configuring the Server                            ####
+####                                                                       ####
+####   1) ./makeconf                                                       ####
+####      This executable has been created to help with your ircd.conf     ####
+####      creation process. It walks you through the steps and makes the   ####
+####      file for you. Note: If you want to edit your ircd.conf you       ####
+####      should only need to: edit ircd.conf. If you ./makeconf again     ####
+####      it will delete the old ircd.conf and re-write a new one.         ####
+####                                                                       ####
+###############################################################################
+####                        Starting the Server                            ####
+####                                                                       ####
+####   1) Make sure you're in the top level Unreal3.1.1 directory..        ####
+####                                                                       ####
+####   2) ./ircd                                                           ####
+####                                                                       ####
+####   3) If you get the error screen, please go through and check each    ####
+####      point presented, if you have no luck, go on IRC                  ####
+####      /server irc.ircsystems.net  #UnrealIRCD                          ####
+####                                                                       ####
+####   4) /server yourserverip or domainname                               ####
+####                                                                       ####
+###############################################################################
+####                          Updating the IRCD                            ####
+####                                                                       ####
+####   1) ./update                                                         ####
+####      Newer releases of Unreal allow the use of ./update which logs    ####
+####      into the Unreal server and allows you to pick a new version to   ####
+####      to upgrade to.                                                   ####
+####                                                                       ####
+###############################################################################
+
+
+

INSTALL.REMOTEINC

@@ -1,23 +0,0 @@
-**** 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.dist

@@ -19,11 +19,10 @@
 #*   $Id$
 #*/
 
-CC=@CC@
+CC=gcc
 INCLUDEDIR=../include
 NETWORKSDIR=
 FROMDOS=/home/cmunk/bin/4dos
-
 # [CHANGEME]
 # Default flags:
 # Change XCFLAGS if you don't like what Config puts there.  Same with
@@ -32,13 +31,10 @@ 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=-O -g -export-dynamic
-IRCDLIBS=@IRCDLIBS@ @TRELIBS@
-CRYPTOLIB=@CRYPTOLIB@
+XCFLAGS=
+IRCDLIBS=
+CRYPTOLIB=
 OPENSSLINCLUDES=
-
-XCFLAGS=-I@TREINCDIR@ @CFLAGS@
 #
 # use the following on MIPS:
 #CFLAGS= -systype bsd43 -DSYSTYPE_BSD43 -I$(INCLUDEDIR)
@@ -92,49 +88,64 @@ IRCDMODE = 711
 # [CHANGEME]
 # IRCDDIR must be the same as DPATH in include/config.h
 #
-IRCDDIR=@IRCDDIR@
+IRCDDIR=/usr/local/lib/ircd
 
+# [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=
 
-URL=@URL@
+#
+# If your system is lacking regex, uncomment this line
+#
+#REGEX=../extras/regex/regex.o
+REGEX=
+
+# [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=
 
 # [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=
 
 # Where is your openssl binary
-OPENSSLPATH=@OPENSSLPATH@
+OPENSSLPATH=
 
-CFLAGS=-I$(INCLUDEDIR) $(XCFLAGS) @LDFLAGS@ $(FD_SETSIZE)
+CFLAGS=-I$(INCLUDEDIR) $(XCFLAGS) $(NEED_U_INT32_T) $(FD_SETSIZE)
 
 SHELL=/bin/sh
 SUBDIRS=src
-BINDIR=@BINDIR@
-INSTALL=@INSTALL@
-RM=@RM@
-CP=@CP@
-TOUCH=@TOUCH@
-RES=
+BINDIR=$(IRCDDIR)
+MANDIR=/usr/local/man
+INSTALL=/usr/bin/install
+RM=rm
+CP=cp
+TOUCH=touch
+
 all:	build
 
 MAKEARGS =	'CFLAGS=${CFLAGS}' 'CC=${CC}' 'IRCDLIBS=${IRCDLIBS}' \
 		'LDFLAGS=${LDFLAGS}' 'IRCDMODE=${IRCDMODE}' \
-		'RES=${RES}' 'BINDIR=${BINDIR}' 'INSTALL=${INSTALL}' \
+		'BINDIR=${BINDIR}' 'INSTALL=${INSTALL}' \
 		'INCLUDEDIR=${INCLUDEDIR}' 'IRCDDIR=${IRCDDIR}' \
-		'RM=${RM}' 'CP=${CP}' 'TOUCH=${TOUCH}' \
-		'SHELL=${SHELL}' 'STRTOUL=${STRTOUL}' \
-		'CRYPTOLIB=${CRYPTOLIB}' \
-		'CRYPTOINCLUDES=${CRYPTOINCLUDES}' 'URL=${URL}'
-
-custommodule:
-	cd src; ${MAKE} ${MAKEARGS} MODULEFILE=${MODULEFILE} 'EXLIBS=${EXLIBS}' custommodule
+		'MANDIR=${MANDIR}' 'RM=${RM}' 'CP=${CP}' 'TOUCH=${TOUCH}' \
+		'RES=${RES}' 'SHELL=${SHELL}' 'STRTOUL=${STRTOUL}' \
+		'CRYPTOLIB=${CRYPTOLIB}' 'REGEX=${REGEX}' \
+		'CRYPTOINCLUDES=${CRYPTOINCLUDES}'
 
 server:
 build:
@@ -148,9 +159,13 @@ build:
 		( cd $$i; ${MAKE} ${MAKEARGS} build; ) \
 	done
 	@echo ' __________________________________________________ '
-	@echo '| Compile is now complete.                         |'
-	@echo '| You should now read the documentation and learn  |'
-	@echo '| how to configure your IRCd.                      |'
+	@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 '| You might want to see include/config.h to adjust |'
+	@echo '| some settings                                    |'
 	@echo '|                                                  |'
 	@echo '| If you really like UnrealIRCd, and would like to |'
 	@echo '| make a donation, please read the Donation file in|'
@@ -170,13 +185,16 @@ 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 Makefile Settings
+	rm -rf include/networks.h include/setup.h include/settings.h Makefile Settings
 
 makex:
 	chmod +x Config newnet ircd ircdcron/ircdchk killircd
-	chmod +x rehash ircdreg
+	chmod +x makeconf rehash ircdreg
 
 fromdos: cleandir
 	$(FROMDOS) -dv *
@@ -201,27 +219,11 @@ depend:
 	done
 
 install: all
-	$(INSTALL) -m 0700 -d $(IRCDDIR)
-	$(INSTALL) -m 0700 src/ircd $(BINDIR)
-	$(INSTALL) -m 0700 -d $(IRCDDIR)/networks
-	$(INSTALL) -m 0600 networks/*.network $(IRCDDIR)/networks
-	$(INSTALL) -m 0700 networks/makenet $(IRCDDIR)/networks
-	$(INSTALL) -m 0600 networks/networks.ndx $(IRCDDIR)/networks
-	$(INSTALL) -m 0700 -d $(IRCDDIR)/doc
-	$(INSTALL) -m 0600 doc/Authors doc/example.conf doc/example.settings doc/coding-guidelines doc/tao.of.irc doc/unreal32docs.html $(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) -m 0600 badwords.*.conf help.conf LICENSE Donation $(IRCDDIR)
-	$(INSTALL) -m 0700 unreal $(IRCDDIR)
-	$(INSTALL) -m 0700 -d $(IRCDDIR)/modules
-	$(INSTALL) -m 0700 src/modules/*.so $(IRCDDIR)/modules
+	@echo "Now install by hand; make install is broken."
 
 pem:	src/ssl.cnf
 	@echo "Generating certificate request .. "
-	$(OPENSSLPATH) req -new \
-              -config src/ssl.cnf -out server.req.pem \
+	$(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 \
@@ -232,15 +234,4 @@ pem:	src/ssl.cnf
 	@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
-
+	@echo "Done!."

README

@@ -1,24 +0,0 @@
-==[ 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.

READMENOW.Win32.txt

@@ -0,0 +1,23 @@
+Unreal IRCD Win32 Version
+-=-=-=-=-=-=-=-=-=-=-=-=-
+
+Ok, in order to save time, and my nerves i am writing this short readme, and eventually an FAQ (after people ask questions) =)
+
+This is information on how to run the win32 version, it does not say, and WILL not say how to use an ircd, as that is sufficiently docuimented in the docs !!!!
+
+you will NEED to modify/create an ircd.conf, follow the documentation for that.
+
+
+Right, thats almost it( that i can think of), but what happens if the server Crashes ???
+----------------------------------------------------------------------------------------
+ok i Have now coded the first bit of usefull (for me) code that dumps the stack to a dialog box, WHAT EVER YOU DO you must do the following:
+		1. Copy and paste EVERYTHING in that dialog box, and send it to me in an e-mail
+		2. Include in that e-mail EVERYTHING that happened in the lead up to the crash
+
+i hope thats SIMPLE to follow, but it will help me soo much !!!!!
+
+
+DrBin (Dave)
+drbin@tspre.org
+
+

READTHIS.NOW

@@ -0,0 +1,15 @@
+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$ ]

Setup

@@ -0,0 +1,37 @@
+#!/bin/sh
+clear
+echo "Starting up UnrealIRCd Setup"
+echo ""
+echo "Press enter to proceed to setup..."
+read cc
+more -d Unreal.nfo
+echo "Press enter to proceed to FAQ..."
+read cc 
+more -d doc/faq
+echo "Press enter to proceed to configuration..."
+read cc
+if [ "$1" != "-noconfig" ] ; then
+	./Config
+fi
+
+echo "Press enter to proceed to compiling..."
+read cc
+make
+echo "Press enter to proceed to ircd.conf making..."
+read cc
+./makeconf
+echo "Press enter to proceed to network configuration..."
+read cc
+clear
+echo "Do you want to use one of these network files, or make your own?"
+cd networks
+ls *.network
+echo "[Type "no" if you want to make your own]"
+read cc
+if [ "$cc" == "no" ] ; then
+	./makenet
+fi
+echo "Press enter to proceed to dynamic ircd configuration..."
+read cc
+pico unrealircd.conf
+echo "You should be able to run UnrealIRCd using ./ircd now".

TODO

@@ -0,0 +1,170 @@
+TODO for Unreal Next:
+
+Write in entries in this form:
+==============================
+
+* nick - date - priority - [ title ] Flag:
+  description
+
+Flags: 
+   CLOSED 
+     = Bug/Idea fixed/implemented. Bug/Idea is up for deletion
+   OPEN 
+     = Bug/Idea up for fixing
+   IN-REPAIR <nick>
+     = Bug/Idea In Progress/Repair by <nick>
+   NO-PRODUCE
+     = Bug/Idea is not able to be (re)produced
+   POSTPONED
+     = Bug/Idea is scheduled for another release/time
+
+If you think that a priority should be higher, make it++
+
+   Priority is 1..10, where 10 is highest, and 1 is lowest.
+----
+TODO :
+----
+
+* stskeeps - Tue Dec 12 2000 - 1 - [ IPv6 ] OPEN:
+    Add IPv6 compatiblity (requested by many people). Must allow :'s in
+    hostnames, will kill backwards compatiblity when IPv6 is enabled
+
+* stskeeps - Tue Dec 12 2000 - 1 - [ Code ] OPEN:
+    Split up code, and make the placement of functions more logic
+
+* codemastr - Tue Dec 12 2000 - 4 - [ Zip_Links ] OPEN:
+    Actually add this since it was planned for 3.0
+
+* codemastr - Tue Dec 12 2000 - 5 - [ Dynconf Recode ] IN-REPAIR stskeeps:
+    Dynconf has a bunch of bugs that can be resolved with a recode
+    We are doing this with the newconf :) -stskeeps
+
+* codemastr - Tue Dec 12 2000 - 8 - [ +I Fixes ]:
+    +I still has some bugs that may cause desync and show users
+    that the +I user is actually on the channel.
+
+* stskeeps - Tue Dec 12 2000 - 1 - [ Bugfixes/Hash ] CLOSED stskeeps:
+    Check for possible hash bug with del_from_client_table or something
+    People still complain about crashes
+    We might have fixed this with recent SERVER passwd fix and other passwd
+    fixes
+
+
+* stskeeps - Wed Dec 13 2000 - 10 - [ Bugfixes ] NO-PRODUCE:
+[[r00t3d](~lok70@168.213.226.rox-62220)] The other one, is lets say you are on
+          server (a), and you set +p to your channel. All the users on Server
+          (b,c, etc..) when they do a /list can see the +p channel in the
+          list. Now if I set it wih chanserv ie.. mlock +ntp, it doesn't do
+          that.. ON all servers (a,b,c) no one sees the +p channel in /list
+          unless they are in the channel allready. 
+    Solution: Fix send_list to use PubChannel instead of SecretChannel
+	(Unable to reproduce. +p channels are hidden on all servers -- codemastr)
+
+
+* stskeeps - Wed Dec 13 2000 - 10 - [ Bugfixes ]:
+[[r00t3d](~lok70@168.213.226.rox-62220)] If you are set +I (Tech
+          Admin/Network Admin) and you are set +q/+a in a channel. When someone /whoises
+          you hey see the channel names: *#channel ^#channel.
+  Fix /whois ShowChannel code
+
+* stskeeps - Wed Dec 13 2000 - 5 - [ Bugfixes ]:
+[RexHsu(~webmin@202.109.72.rox-42822)] #TVB ÄÖÄÖ H root@61.151.53.User-42432
+          :0 none
+[RexHsu(~webmin@202.109.72.rox-42822)] #TVB ÄÖÄÖ H@
+          ~webmin@202.109.72.User-42822 :0 none
+[RexHsu(~webmin@202.109.72.rox-42822)] * End of /WHO list.
+     Chinese nicks "clash", this is not the right nicks i typed in
+
+* stskeeps - Wed Dec 13 2000 - 5 - [ Bugfixes ]:
+[eYe-Man(none@of.your.fucking.business)] <eYe-Man> Can you show me how you
+got
+          OP?
+[eYe-Man(none@of.your.fucking.business)] <Sexy_20> me i dont know how!!!!!
+          even i dont see where i got OP
+[eYe-Man(none@of.your.fucking.business)] <Sexy_20> or when some server gave
+me
+     SJOIN gives people ops? :P
+
+* stskeeps - Thu Dec 14 2000 - 10 - [ Bugfixes ]
+InTe[_:#roxnet> -oxygen.phrozen.org- *** Global -- from Irc.LinuxFreakz.Net:
+                 No response from dumper.roxnet.org[130.240.202.121], closing
+                 link
+             Users can see that using +g ???
+          FIXED: Sat Dec 30 2000 by stskeeps
+
+* stskeeps - Fri Dec 14 2000 - 1 - [ SSL ]
+	Challenge/Response kind of thing.
+            
+	/CHALLENGE nick keyname/commonidentifier type :b64text
+	  type = 0, challenge type = 1, response
+         Must be flood controlled in some way
+         Can only work between servers and or U:lines and or 
+           +z users
+
+	Example:
+          > :Stskeeps CHALLENGE RaYmAn rayman.pem 0 :0D0FE5F6D46
+          < :RaYmAn CHALLENGE Stskeeps rayman.pem 1 :D0F5F543433
+        
+	The way this works is, that the challenger got RaYmAn's public RSA key
+        and he needs to authenticate that he is really talking to RaYmAn (the
+        real one). He then sends a random string to RaYmAn, encrypted with 
+        RaYmAn's public key. RaYmAn then decrypts it using his private key, and
+        then re-encrypts the random stuff using his private key, and sends back
+        to Stskeeps, Sts then checks with decrypting the crypted text using the public
+        key, and if its OK, then considers him OK. 
+
+        We can use this for NickServ authentication using RSA keys, 
+        or server<->server authentication, or /oper authentication
+        (no more stolen passwords, yipieeeeeeee)
+
+        This is also easily possible to add, in IRCii, in BitchX, EPIC, 
+        mIRC (DLLs), etc.
+        
+        This is also good for raising security/authenticating to another level.
+        Users can check if they are talking to the right person, NickServ databases
+        no longer needs to have passwords, just use RSA keys
+
+* stskeeps - Sun 17 Dec 2000 - 1 - [ General ]
+          
+         P:ip:W:*:port
+           UnrealHTTPD!
+         Sat 30 Dec 2000 - stskeeps - *cough* listen::option http ;)
+
+* codemastr - Wed 20 Dec 2000 - 3 - [ General ]
+	
+	Recode badwords to allow a different replace word for each word
+
+* codemastr - Wed 20 Dec 2000 - 1 - [ Install ]
+	
+	Add make install
+
+* codemastr - Wed 20 Dec 2000 - 9 - [ Bugfixes ]
+
+	connect to a server, /oper, then run telnet and link a server. Close the telnet but do NOT
+ 	send a SQUIT, the server displays no notice to opers that the server split.
+          Stskeeps> +j? but yes, there's a bug there
+
+        FIXED Sat 30 Dec 2000 by Stskeeps
+
+* stskeeps - Sat Dec 23 2000 - 10 - [ Bugfixes ]
+         There's some kind of bug that shows people being on same channel
+         twice. I got a feeling its to do with JOIN/SJOIN as its only remote.
+          [ Stskeeps  ] [@ChanServ  ] [@Fresh-Prin] [ Fresh-Prin] [@Fresh-Prin] 
+         Same person 
+
+* codemastr - Tue Dec 26 2000 - 6 - [ Bugfixes ]
+	(too lazy to type it out)
+	http://sourceforge.net/bugs/?func=detailbug&bug_id=126645&group_id=1968
+	That fix will work except it needs to be modified so it checks remote
+	before denying because of not being oper
+* stskeeps - Wed Dec 27 2000 - 5 - [Configuration]
+        Add a SWHOIS option to oper {} block, suggested by Robertsog
+* codemastr - Tue Dec 26 2000 - 6 - [ Bugfixes ]
+	(too lazy to type it out)
+	http://sourceforge.net/bugs/?func=detailbug&bug_id=126645&group_id=1968
+	That fix will work except it needs to be modified so it checks remote
+	before denying because of not being oper
+* stskeeps  - Sun Dec 30 2000 - 10 - [ Bugfixes ]
+       /whois shows what channels +S are in
+* codemastr - Tue Jan 03 2001 - 1 - [ Idea ]
+	Add /kill logging option suggested by Cerb

TSpre.doc

@@ -0,0 +1,56 @@
+
+
+
+
+
+
+
+
+
+NOTE: tspre.org does not exist at the moment, 
+      as I dont have a shell for it anymore. 
+      If anyone want to donate a shell with a background process, 
+      and 1 IP with port 6667 open, they are welcome.
+      however, when i get my adsl connection, it will run off that - on a
+      50mhz machine *g*
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+       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,70 +1,59 @@
 ===============================================
-=               UnrealIRCd v3.2               =
+=            UnrealIRCd v3.1.1                =
 ===============================================
  Was brought to you by:
-
-  The core team:
-  ==============
   * Stskeeps  <stskeeps@tspre.org>
   * codemastr <codemastr@unrealircd.com>
-  * Syzop     <syzop@unrealircd.org>
-  * Luke      <luke@unrealircd.com>
-
-  Contributors
-  ============
-  * McSkaf    <mcskaf@unrealircd.org>
-  * Zogg      <zogg@unrealircd.org>
-  * NiQuiL    <niquil@unrealircd.org>
-  * assyrian  <assyrian@unrealircd.org>
-  * nighthawk <nighthawk@unrealircd.com>
   * DrBin     <drbin@unrealircd.com>
-  * llthangel <llthangel@unrealircd.org>
-  * Griever   <griever@unrealircd.com>
   
-  Documentation:
-  ==============
-  * CKnight^ <cknight@unrealircd.com>
-
  Precenses on the Internet:
   * http://www.unrealircd.com
  
- CVS
- ====
- To get anonymous access: (read only)
- "cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot login"
+ 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:
+press enter when asked for password
 
- latest 3.2 release ("stable"):
- "cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r stable -d Unreal-stable unreal"
+and to get latest stable:
+"cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r stable -d Unreal-stable unreal"
 
- latest 3.2 fixes / development ("unreal3_2_fixes"):
- "cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r unreal3_2_fixes -d Unreal-stable unreal"
+latest beta:
+"cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r beta -d Unreal-beta 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/)
+  * To get support
+  ================
+    * IRC: /server irc.ircsystems.net 6667 - /join #unrealircd
+      [Note: 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-support@lists.sourceforge.net (for support)
+    * READ doc/faq BEFORE ASKING QUESTIONS!
+ 
+  * 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
 
- Means of support:
- * 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.]
- * Forum: http://forums.unrealircd.com/
- * Mailing list: unreal-users@lists.sourceforge.net
-   (http://lists.sourceforge.net/lists/listinfo/unreal-users also
-    has links to the archive).
+    * 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.
 
- UnrealIRCd Bugtracker (Where to report bugs or make suggestions)
- ==================================================================
- http://bugs.unrealircd.org
+  * Got a suggestion?
+  ===================
+    * Mail it to unreal-dev@lists.sourceforge.net :) or catch one from
+      the Unreal team online on IRC:)
 
- Want to discuss, chat, etc?
- =============================
- * IRC: /server irc.ircsystems.net 6667 - /join #UnrealIRCd
+ 

aliases/aliases.conf

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

aliases/anope.conf

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

aliases/auspice.conf

@@ -1,16 +0,0 @@
-/* Auspice Aliases */
-
-alias nickserv { type services; };
-alias ns { nick nickserv; type services; };
-alias chanserv { type services; };
-alias cs { nick chanserv; type services; };
-alias memoserv { type services; };
-alias ms { nick memoserv; type services; };
-alias helpserv { type services; };
-alias hs { nick helpserv; type services; };
-alias operserv { type services; };
-alias os { nick operserv; type services; };
-alias rootserv { type services; };
-alias rs { nick rootserv; type services; };
-
-include "aliases/aliases.conf";

aliases/cygnus.conf

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

aliases/epona.conf

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

aliases/generic.conf

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

aliases/genericstats.conf

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

aliases/ircservices.conf

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

aliases/operstats.conf

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

autoconf/Makefile

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

autoconf/aclocal.m4

@@ -1,141 +0,0 @@
-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`
-		CFLAGS="$CFLAGS $CURLCFLAG -DUSE_LIBCURL"
-		CURLLIBS=`$enableval/bin/curl-config --libs`
-
-		dnl curl-7.11.0 and up will include the ares info, older versions do not
-		if test "x`echo $CURLLIBS |grep .*ares.*`" = x ; then
-			CURLLIBS="$CURLLIBS -lares"
-		fi
-		IRCDLIBS="$IRCDLIBS $CURLLIBS"
-		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)
-	AC_WARN(disabling ssl support)
-    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)
-	AC_WARN(disabling ziplink support)
-    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

@@ -1,400 +0,0 @@
-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
-
-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"
-		;;
-	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)
-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_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_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(hostname, [AC_HELP_STRING([--with-hostname=host],[Specify the local hostname of the server])], AC_DEFINE_UNQUOTED(DOMAINNAME,"$withval"),AC_DEFINE_UNQUOTED(DOMAINNAME,"`hostname`"))
-AC_DEFINE_UNQUOTED(MYOSNAME,"`uname -a`")
-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"; mkdir $withval/tmp, AC_DEFINE_UNQUOTED(DPATH,"`pwd`") IRCDDIR="`pwd`" mkdir `pwd`/tmp)
-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") 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))
-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 RELEASE!
-tre_version="0.6.6"
-AC_MSG_RESULT(extracting TRE regex library)
-cur_dir=`pwd`
-cd extras
-dnl remove old tre directory to force a recompile...
-rm -rf tre-$tre_version
-if test "x$ac_cv_path_GUNZIP" = "x" ; then
-	tar xfz tre.tar.gz
-else
-	cp tre.tar.gz tre.tar.gz.bak
-	gunzip -f tre.tar.gz
-	cp tre.tar.gz.bak tre.tar.gz
-	tar xf tre.tar
-fi
-AC_MSG_RESULT(configuring TRE regex library)
-cd tre-$tre_version
-./configure --disable-agrep --disable-shared --disable-system-abi --disable-wchar --disable-multibyte --prefix=$cur_dir/extras/regexp
-AC_MSG_RESULT(compiling TRE regex library)
-$ac_cv_prog_MAKER
-AC_MSG_RESULT(installing TRE regex library)
-$ac_cv_prog_MAKER install
-TREINCDIR="$cur_dir/extras/regexp/include"
-AC_SUBST(TREINCDIR)
-if test "x$ac_cv_path_PKGCONFIG" = "x" ; then
-	TRELIBS="-L../extras/regexp/lib -ltre"
-else
-	TRELIBS=`$ac_cv_path_PKGCONFIG --libs tre.pc`
-fi
-AC_SUBST(TRELIBS)
-cd $cur_dir
-AC_OUTPUT(Makefile src/modules/Makefile unreal ircdcron/ircdchk)
-chmod 0700 unreal
-chmod 0700 ircdcron/ircdchk

badwords.channel.conf

@@ -1,52 +1,53 @@
-/*  
- 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"; };
+# 
+# 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
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+#
+pussy
+fuck
+whore
+slut
+shit
+asshole
+bitch
+cunt
+vagina
+penis
+jackass
+*fucker*
+faggot
+fag
+horny
+gay
+dickhead
+sonuvabitch
+*fuck*
+boobs
+tits

badwords.message.conf

@@ -1,52 +1,53 @@
-/*  
- 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"; };
+# 
+# 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
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+# 
+#
+#
+#
+pussy
+fuck
+whore
+slut
+shit
+asshole
+bitch
+cunt
+vagina
+penis
+jackass
+*fucker*
+faggot
+fag
+horny
+gay
+dickhead
+sonuvabitch
+*fuck*
+boobs
+tits

badwords.quit.conf

@@ -1,52 +0,0 @@
-/*  
- 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"; };

crypt/Makefile

@@ -0,0 +1,40 @@
+#************************************************************************
+#*   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
+LIBS=-lcrypt
+
+all: mkpasswd
+crypt: install
+
+mkpasswd: mkpasswd.c
+	cc ${LIBS} -O mkpasswd.c -o mkpasswd
+
+install:
+	chmod 700 crypter
+	./crypter ${IRCDCONF}
+	@echo 'done.'
+
+clean:
+	/bin/rm -f mkpasswd

crypt/README

@@ -0,0 +1,63 @@
+/************************************************************************
+ *   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

@@ -0,0 +1,77 @@
+#!/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];
+
+$ircdout = "IRCDOUT";
+
+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
+if ($text =~ /^o/i) {
+    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");
+}
+elsif ($text =~ /^n/i) {
+    chop($text);
+    @nline = split(':', $text);
+    $salt = $saltset[rand(time)%64].$saltset[(rand(time)>>6)%64];
+    $nline[2] = crypt(@nline[2], $salt);
+    print ($ircdout join(':',@nline)."\n");
+}
+elsif ($text =~ /^x/i) {
+    chop($text);
+    @xline = split(':', $text);
+    $salt1 = $saltset[rand(time)%64].$saltset[(rand(time)>>6)%64];
+    $salt2 = $saltset[rand(time)%64].$saltset[(rand(time)>>6)%64];
+    $xline[1] = crypt(@xline[1], $salt1);
+    $xline[2] = crypt(@xline[2], $salt2);
+    print ($ircdout join(':',@xline)."\n");
+}
+else {
+    print $ircdout "$text";
+}
+}
+close ($ircdout);
+close ($ircdin);
+print "/bin/cp ",$tmpfile," ",$ircdconf,"\n";
+(fork()==0) ? exec("/bin/cp", $tmpfile, $ircdconf) : wait;
+
+#unlink($tmpfile);

crypt/mkpasswd.c

@@ -0,0 +1,43 @@
+/* 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

@@ -1,66 +0,0 @@
-#!/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."
-

devel/aln.doc

@@ -0,0 +1,26 @@
+
+ALN, Alphanumeric System
+(C) Stskeeps 2000
+
+ALN is a quick hack to short down usage of bandwidth-using servernames
+in prefixes, NICK commands, etc etc. It replaces the name with a 
+1 or 2 byte prefix in a system, look at src/aln.c for the prefix
+types/values. It will be an PROTOCTL, and used in NICK messages and so on, 
+and introduce a new prefix server<->server called |server. The value of the
+server is calculated by a hash value, the scache system, so that the server
+can lookup with a new scache function, scache_find_by_hash(int i). The
+question of it will conflict in similar-hash server names, is a wonder to me
+:P, we will find out, but scache will fail at same time then. 
+
+
+Examples: 
+& Medb 4 957458466 ~Medb bservice.org D2 0 +iwrx *
+:BotService Bot - bservice.org - Owner:  terri{J}
+
+where D2 is the hash value of oxygen.phrozen.org (/stats s on a
+#define DEVELOP server). irc.flirt.org has hash 96 (ALN code AX) for
+instance. 
+
+@D2 GLOBOPS :message
+will be a message from server with hash D2, found find-by-hash(256) 
+

devel/new.plines

@@ -0,0 +1,50 @@
+From cmunk@draconic.fyremoon.net Wed Apr  5 18:09:55 2000
+Date: Wed, 5 Apr 2000 18:07:55 +0100 (BST)
+From: "The Nightwalker (Stskeeps)" <cmunk@draconic.fyremoon.net>
+To: unreal-dev@lists.sourceforge.net
+Subject: [Unreal-dev] P:Lines
+
+
+Some stuff i got ideas about.. stripping the IP and port from the M:Line
+and enforcing the main port to be in a M:line
+
+M:irc.fyremoon.net:*:Forever is gonna start tonight:*
+
+P:ip:flags:password1,password2,password3:port
+  |   |    |                             \- port to bind to
+  |   |    |
+  |   |    \- Commaseperated lists of accepted passwords
+  |   |       * if none
+  |   |
+  |   \--- C = Allow clients
+  |        S = Allow servers
+  |        R = ONLY allow our remote admin connections 
+  |            (may only be on a P:line of its own)
+  |        J = Clients that connect here are counted as Java(Confroomhack)
+  |        s = Makes this a SSL port
+  |        * = CS 
+  | 
+  |
+  \--- IP to bind to, * = INADDR_ANY (all interfaces)
+
+Will make P:Lines more efficent
+
+---------------------------------------------------------------------
+Carsten V. Munk - The Nightwalker, known on IRC as Stskeeps or techie
+  * ICQ: 16465977 - E-Mail: stskeeps@tspre.org
+  * Author of UnrealIRCd (http://unreal.tspre.org)
+  * Technical Admin @ irc.roxnet.org, server admin of irc.fyremoon.net
+"To understand a program you must become both the machine and the program."
+----------------------------------------------------------------------
+
+-----BEGIN GEEK CODE BLOCK-----
+Version: 3.1
+GCS/CC d- s: a--- C+++ UL P L++ E-- W++ N+ o-- K- w--- O- M V-- PS+ PE- Y+
+PGP t+ 5 X R- tv- b+ DI++ D++ G e-- h! r z**
+------END GEEK CODE BLOCK------
+
+
+_______________________________________________
+Unreal-dev mailing list
+Unreal-dev@lists.sourceforge.net
+http://lists.sourceforge.net/mailman/listinfo/unreal-dev

doc/ADD-TO-IRCRC

@@ -0,0 +1,72 @@
+# $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,12 +118,8 @@ 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. :) 
 
-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, date
+Carsten Munk <stskeeps@mp3fans.co.uk> / May and futher 1999:
+* Made many features based on Elite.. :/
 
 Thanks go to those persons not mentioned here who have added their advice,
 opinions, and code to IRC.

doc/Crule.readme

@@ -0,0 +1,128 @@
+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/History/19.mu1-New

@@ -0,0 +1,16 @@
+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

@@ -0,0 +1,34 @@
+
+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

@@ -0,0 +1,41 @@
+                 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/Elite.Changes

@@ -0,0 +1,129 @@
+[ $Id$ ]
+Take this with a grain of salt.. it's heaps old and this isn't Elite anymore
+
+
+---------------------------
+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/Etiquette

@@ -0,0 +1,86 @@
+/************************************************************************
+ *   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

@@ -0,0 +1,963 @@
+/************************************************************************
+ *   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

@@ -0,0 +1,382 @@
+/************************************************************************
+ *   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

@@ -0,0 +1,241 @@
+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/Unreal31_to_32.html

@@ -1,195 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>UnrealIRCd - 3.2 - Offical Documentation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<p> <font size="-1">I M P O R T A N T R E A D I N G</font></p>
-<p><font size="-1">(YES, YOU WILL NEED TO READ ALL OF THIS)</font></p>
-<p><font size="-1">* Unreal3.2 is a lot different than Unreal3.1.1. Forget 
-  all you have learned about setting up Unreal3.1.1 - this is a lot different. 
-  We have got a new configuration format that integrates all the former config 
-  files,ircd.conf, vhost.conf, chrestrict.conf, unrealircd.conf, into to one newunrealircd.conf 
-  (what the ircd.conf is called now). See doc/ for more information on the configuration 
-  format</font></p>
-<p><font size="-1">* THIS IS A BETA VERSION, REPORT BUGS ON http://bugs.unrealircd.org</font></p>
-<p><font size="-1">* We have introduced a new cloaking algorithm (+x), which makes 
-  it incompatible with Unreal3.1.1 - these can however still link, but the hostname 
-  will look different. This is made of three big numbers, configured in the config 
-  file - and these MUST be the same on all servers on the network. Keep these 
-  numbers secret, and the cloaking algorithm is uncrackable (within 55 years, 
-  that is). The +x algorithm was changed slightly to fix a method of cracking 
-  that was found. #define COMPAT_BETA4_KEYS to use the beta4 system for compatibility 
-  with older betas.</font></p>
-<p><font size="-1">* If you use Linux and have problems where the IRCd complains 
-  that MAXCONNECTIONS is larger than FD_SETSIZE, you need to get your root to 
-  edit /usr/include/bits/types.h - #define __FD_SETSIZE 1024 to be somenumber 
-  that is equal or higher than MAXCONNECTIONS. This is a problem with Linux that 
-  it is hard coded and non override able in some distributions. We recommend you 
-  use FreeBSD or the variants of this if you need to run high load IRC servers.</font></p>
-<p><font size="-1">* We use autoconf to help with compilation, and this should 
-  make us able to a lot more platform (we have even ported to BeOS).</font></p>
-<p><font size="-1">* We require a pthreads library for the SOCKS scan now - and 
-  this is now done in the background (no more waiting!).</font></p>
-<p><font size="-1">* The IRCd is now modularized, and you load modules with the 
-  loadmodule command. You will most likely want to add these lines:<br>
-  loadmodule &quot;src/modules/commands.so&quot;;<br>
-  loadmodule &quot;src/modules/scan.so&quot;;<br>
-  loadmodule &quot;src/modules/scan_socks.so&quot;;<br>
-  loadmodule &quot;src/modules/scan_http.so&quot;;</font></p>
-<p><font size="-1"> If you would like to code a module, doc/ will contain a module 
-  guide,and we got an example module in src/modules/m_dummy.c.</font></p>
-<p><font size="-1">* We have some IPv6 support, and there are some minor bugs 
-  in it.</font></p>
-<p><font size="-1">* The documentation is NOT yet 100% complete</font></p>
-<p><font size="-1">* We have added snomask (similar to ircu), basically this allowed 
-  us to remove several modes. Modes +cfFkje are gone, but don't worry, you can 
-  still use them. They are now added like this:</font></p>
-<p><font size="-1"> /mode yournick +s +cF</font></p>
-<p><font size="-1"> You set the flags in the second parameter of the mode command 
-  for a mode change +s, setting -s with no parameters removes all your snomask. 
-  You can remove a specific snomask by doing:</font></p>
-<p><font size="-1"> /mode yournick -s -c</font></p>
-<p><font size="-1">The current snomasks are:</font></p>
-<p><font size="-1"> c - local connects<br>
-  F - far connects<br>
-  f - flood notices<br>
-  k - kill notices<br>
-  e - 'eyes' notices<br>
-  j - 'junk' notices<br>
-  v - vhost notices<br>
-  G - gline/shun notices<br>
-  n - nick change notices<br>
-  q - deny nick (Q:line) rejection notices</font></p>
-<p><font size="-1"> It shouldn't be too hard to figure out, just play around with 
-  it a bit :)</font></p>
-<p><font size="-1">* /who needs testing it was recorded and may contain bugs</font></p>
-<p><font size="-1">* We have added alias {} which allows you to dynamically create 
-  commands such as /nickserv Read example.conf for more information on how to 
-  create your own. To use standard ones include one of the following files</font></p>
-<p><font size="-1"> aliases/ircservices.conf (IRCServices, Daylight)<br>
-  aliases/epona.conf (Epona)<br>
-  aliases/auspice.conf (Auspice)<br>
-  aliases/generic.conf (Magick, Sirius, Wrecked)<br>
-  aliases/operstats.conf (OperStats)<br>
-  aliases/genericstats.conf (GeoStats, NeoStats)</font></p>
-<p><font size="-1">* You can now use an IP in the oper::from and vhost::from fields 
-  even if the host resolves</font></p>
-<p><font size="-1">* Added an http proxy scanner (scan_http.so)</font></p>
-<p><font size="-1">* Added oper::snomask to specify default oper snomask modes</font></p>
-<p><font size="-1">* /helpop text has been moved to a config directive, help {}. 
-  To keep the standard help text you need to include help.conf so add include 
-  &quot;help.conf&quot;; to your config file.</font></p>
-<p><font size="-1">* To be able to use G:lines you must now have the can_gkline 
-  flag (or t if old style flags)</font></p>
-<p><font size="-1">* Usermode +T (Tech Admin) has been removed, since it is 100% 
-  useless</font></p>
-<p><font size="-1">* Added a make install to copy files to the installation location</font></p>
-<p><font size="-1">* Removed ./ircd, ./killircd, crypt/mkpasswd, ./rehash and 
-  merged them into a new ./unreal [start|stop|rehash|mkpasswd] for mkpasswd the 
-  format is</font></p>
-<p><font size="-1"> ./unreal mkpasswd [method] [password]</font></p>
-<p><font size="-1">* Added a new system for crypting passwords. You now do for 
-  example password &quot;my password&quot; { crypt; }; This allows you to have 
-  some crypted passwords and others not. If you have SSL enabled you may also 
-  use the md5 and sha1 methods.</font></p>
-<p><font size="-1">* The old blackhole is now set::scan::endpoint and specifies 
-  an IP and port to tell proxies to connect to.</font></p>
-<p><font size="-1">* You can now specify a cipher list for SSL links (read doc/conf.doc 
-  for more info)</font></p>
-<p><font size="-1">* +I is now in invisibility.so so it is easily disabled</font></p>
-<p><font size="-1">* set::socks has been replaced by set::scan (read doc/conf.doc 
-  for more info)</font></p>
-<p><font size="-1">* If you experience problems with the scanners, perhaps check 
-  out BOPM (http://www.blitzed.org/bopm)</font></p>
-<p><font size="-1">* log {} syslog support added (read doc/unreal32docs.html for 
-  more info)</font></p>
-<p><font size="-1">* Added ripemd-160 password encryption support</font></p>
-<p><font size="-1">* Enabled sha1 and md5 password encryption on Win32 regardless 
-  of whether SSL is used.</font></p>
-<p><font size="-1">* Added WinNT/2k/XP service support (experimental) To use this 
-  you use the unreal.exe utility: unreal install -installs the service<br>
-  unreal uninstall -uninstalls the service <br>
-  unreal start -starts the service <br>
-  unreal stop -stops the service<br>
-  unreal restart -restarts the service<br>
-  unreal rehash -rehashes the config file</font></p>
-<p><font size="-1"> Config errors and crashes are now logged to service.log when 
-  in service mode.</font></p>
-<p><font size="-1">* Implemented a new win32 debugger to make fixing bugs much 
-  easier.</font></p>
-<p><font size="-1">* Added a win32 installer to simplify installing under Windows.</font></p>
-<p><font size="-1">* AKILL/RAKILL is deprecated. Server command still works but 
-  will be removed eventually (aliases to TKL G). For normal opers it notices that 
-  the commands are deprecated.</font></p>
-<p><font size="-1">Made the config parser smarter when it comes to time values 
-  and size values. Entries are no longer limited to 1d2h1m. You can now enter 
-  &quot;1day 2 hours 1 minute&quot; for example. See doc/conf.doc for more information.</font></p>
-<p><font size="-1">* The oper override code has been rewritten to be less intrusive. 
-  You can now no longer automatically join a channel for which you must override 
-  a mode. You must /invite yourself to the channel. The idea behind this is it 
-  prevents the accidental &quot;rejoin on kick&quot; ban override and joining 
-  a +s channel without realizing it is +s and therefore you shouldn't know it 
-  exists.</font></p>
-<p><font size="-1">* If you use the SSL features of Unreal, you should use OpenSSL 
-  0.9.6e or later. This is important as the older versions may make the program 
-  exploitable. See http://www.openssl.org for more information</font></p>
-<p><font size="-1">* We have made a lot of changes to deal with SSL, and if you 
-  find any flaws or problems, please contact the coder team. We however think 
-  that the changes will make SSL more transparent and make it work more efficiently.</font></p>
-<p><font size="-1">* Added technical documentation in doc/technical. This directory 
-  will contain information about the protocol used by Unreal.</font></p>
-<p><font size="-1">* Added EGD support for SSL. EGD allows entropy to be gathered 
-  on systems that do not have a random device (/dev/random or /dev/urandom) or 
-  have an unreliable random device. Unreal has been tested using EGADS (http://www.securesoftware.com/egads.php) 
-  [With EGD support enabled], PRNGD (http://www.aet.tu-cottbus.de/personen/jaenicke/postfix_tls/prngd.html), 
-  and EGD (http://egd.sourceforge.net). Other EGD compatible programs should work 
-  as well.</font></p>
-<p><font size="-1">* We have created a new complete set of docs! doc/unreal32docs.html 
-  is now a complete<br>
-  set of docs! It is still not finished, however it contains atleast what was 
-  already<br>
-  avail. in the other doc files. <br>
-  It can also be view online @ http://www.unrealircd.com/unreal32docs.html</font></p>
-<p><font size="-1">* We have removed ./Setup - Please read the new docs for information 
-  on configuring &amp;<br>
-  setting up Unreal3.2</font></p>
-<p><font size="-1">* Removed makeconf - Read the docs to make a config file</font></p>
-<p><font size="-1">* Added set::ssl::options with the following options:<br>
-    fail-if-no-clientcert   - If SSL client connects and doesn't provide a client<br>
-                              certificate, abort connection immediately<br>
-    verify-certificate      - Check the certificate's validity using X509 methods, check if<br>
-                              we trust CA's, etc. <br>
-                              It however does slip self signed certificates through UNLESS<br>
-    no-self-signed          - Don't allow self-signed certificates through (requires<br>
-                              verify-certificate)</font></p>
-
-<p><font size="-1">* Added the ability specify which CA's are trusted using set::ssl::trusted-ca-file</font></p>
-
-<p><font size="-1">* A new configuration system has been added. The system is a bit more strict (meaning it
-  will complain more often) but it will never crash due to configuration errors, just
-  display a message saying errors exist.</font></p>
-
-<p><font size="-1">* SVSLUSERS was added to all U:lines to change local and global max user counts (this is
-  NOT meant so you can make the max count higher than it really should be.)</font></p>
-
-<p><font size="-1">* A new oper flag, can_override/v has been added. This is an attempt to stop oper abuse.
-  All opers can no longer use oper-override, this oflag MUST be in place for oper-override
-  to be allowed. Can_override is NOT assumed to be present no matter what your flags,
-  meaning you could be +N but still not be allowed to use oper-override.</font></p>
-
-<p><font size="-1">* UNKLINE and UNZLINE have been removed in favor of a system like G:lines, to remove you
-  now /kline -user@host or /zline -user@host</font></p>
-<p><font size="-1">* MAKE SURE YOU RERUN ./Config AND RUN make clean BEFORE USING 
-  THIS VERSION!!!</font></p>
-<p> </p>
-<p> </p>
-<p><font size="+2"><strong>Notes on compatibility</strong><a name="notesoncompatibility" id="notesoncompatibility"></a></font><br>
-</p>
-<p>Unreal 3.2 is ONLY compatible with Unreal3.1.4 and Unreal3.2 servers. DO NOT 
-  ATTEMPT to link to servers that it is NOT compatible with.</p>
-<p>
-</body>
-</html>

doc/coding-guidelines

@@ -1,41 +0,0 @@
-
-Some minor rules about patches & modifications to UnrealIRCd
-
-1. When making a change, always add a small description in Changes, in the
-   BOTTOM
-
-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.
-

doc/commands.txt

@@ -0,0 +1,334 @@
+Written by ^MrMike^ (mike@sector001.org) for the UnrealIRCd
+Modified by codemastr to include a few other commands
+(note, this file will be updated in CVS asap)
+
+PRIVMSG
+ - Used to send a message to a person or a channel
+ Syntax: MSG <nick>,<nick2>,<nick3>,<nick4> <text>
+ Example: PRIVMSG Stskeeps :Hello. Unreal is a very good ircd.
+ Example: PRIVMSG Stskeeps,codemastr,DrBin :Hello Unreal Coding Team
+
+NOTICE
+ - Mainly used for one-time communication or for the results of a command.
+ Syntax: NOTICE <nick>,<nick2>,<nick3>,<nick4> <text>
+ Example: NOTICE codemastr :Hi. How are you?
+ Example: NOTICE codemastr,Stskeeps :Hi codemastr and Stskeeps.
+
+MODE
+ - Used to change the mode of a channel or a user. You can only change modes for channel you    are an Operator or Half-Op on. Also, you can only changes user modes for yourself.
+ Syntax: MODE <channel/user> <mode>
+ Example: MODE #UnrealIRCD +tn
+ Example: MODE #UnrealIRCD +ootn codemastr Stskeeps
+
+NICK
+ - Changes your "online identity" on a server. All those in the channel you are in will be    alerted of your nickname change.
+ Syntax: NICK <new nickname>
+ Example: NICK |codemastr|
+
+JOIN
+ - Used to enter one or more channels on an IRC server. All occupants of the channel will be    notified of your arrival.
+ Syntax: JOIN <chan>,<chan2>,<chan3>
+ Example: JOIN #UnrealIRCD
+ Example: JOIN #UnrealIRCD,#OperHelp
+
+PING
+ - Determines the amount of lag (time it takes for a response to reach a person and come    back) between yourself and someone else.
+ Syntax: PING <user>
+ Example: PING Stskeeps
+
+WHOIS
+  - Shows information about the user in question, such as their "name", channels they are     currently in, their hostmask, etc.
+ Syntax: WHOIS <user>
+ Example: WHOIS DrBin
+
+ISON
+ - Used to determine of a certain user or users are currently on the IRC server based upon     their nickname.
+ Syntax: ISON <user> <user2> <user3> <user4>
+ Example: ISON Stskeeps DrBin codemastr NickServ ChanServ OperServ MemoServ
+
+USER
+ - Used during registration to server (i.e. during inital connection sequence.)
+
+PART
+ - Used to part (or leave) a channel you currently occupy. All those in the channel will be    notified of your departure.
+ Syntax: PART <chan>,<chan2>,<chan3>,<chan4>
+ Example: PART #UnrealIRCD
+ Example: PART #UnrealIRCD,#OperHelp
+
+QUIT
+ - Disconnects you from the IRC server. Those in the channels you occupy will be notified of    your departure. If you do not specify a reason, your nickname becomes the reason.
+ Syntax: QUIT <reason>
+ Example: QUIT Leaving!
+
+USERHOST
+ - Returns the userhost of the user in question. Usually used by scripts or bots to retrieve    userhost information.
+ Syntax: USERHOST <nickname>
+ Example: USERHOST codemastr
+
+SVSNICK
+ - Can only be used by a U:Lined server (i.e. services). Changes the nickname of the user in    question.
+ Syntax: SVSNICK <nickname> <new nickname> :<timestamp>
+ Example: SVSNICK Stskeeps Techie :963086432
+
+SVSMODE
+ - Can only be used by a U:Lined server (i.e. services). Changes the mode of the channel or    user in question.
+ Syntax: SVSMODE <channel/user> :<mode>
+ Example: SVSMODE #UnrealIRCD :+o Stskeeps
+ Example: SVSMODE codemastr :+i
+
+LUSERS
+ - Provides local and global user information (such as current and maximum user count).
+ Syntax: LUSERS <server>
+
+CHANSERV
+ - Will send a secure message to ChanServ. Similar to /msg ChanServ, but more secure. May not work if server is configured improperly.
+
+TOPIC
+ - Sets/Changes the topic of the channel in question, or just display the current topic.
+ Syntax: TOPIC <channel>
+ Syntax: TOPIC <channel> <topic>
+ Example: TOPIC #operhelp
+ Example: TOPIC #UnrealIRCD Welcome to the Unreal IRCD Home Channel.
+
+INVITE
+ - Sends a user an invitation to join a perticular channel. You must be an operator on the    channel in order to invite a user into it.
+ Syntax: INVITE <user> <channel>
+ Example: INVITE codemastr #OperHelp
+
+KICK
+ - Removes a user from a channel. Can only be used by Operators or Half-Ops. If no reason is    specified, your nickname becomes the reason.
+ Syntax: KICK <channel> <user> <reason>
+
+WALLOPS
+ - Sends a "message" to all those with the umode +w. Only IRCops can send wallops, while anyone can view them.
+ Syntax: WALLOPS <message>
+
+KILL
+ - Forcefully disconnects a user from an IRC Sever. Can only be used by IRCops.
+ Syntax: KILL <user> <reason>
+ Example: KILL Clone5 Cloning is not allowed
+
+AWAY
+ - Sets your online status to "away".
+ Syntax: AWAY <reason> (AWAY without a reason will unset you away)
+ Example: AWAY Walking the dog...
+
+SQUIT
+ - Disconnects an IRC Server from the network
+ Syntax: SQUIT <server>
+ Example: SQUIT leaf.*
+
+WHO
+ - Searches user information (-i users only) for supplied information. IRCops are a ble to    search +i users.
+ Syntax: WHO <search>
+ Example: WHO *.aol.com
+
+WHOWAS
+ - Retrieves previous 'WHOIS' information for users no longer connected to the server.
+ Syntax: WHOWAS <nickname>
+ Example: WHOWAS Stskeeps
+
+LIST
+ - Provides a complete listing of all channels on the network. If a search string is    specified, it will only show those matching the search string.
+ Syntax: LIST <search string>
+ Example: LIST
+ Example: LIST *ircd*
+
+NAMES
+ - Provides a list of users on the specified channel.
+ Syntax: NAMES <channel>
+ Example: NAMES #help
+
+OPER
+ - Attempts to give a user IRCop status.
+ Syntax: OPER <uid> <pass>
+ Example: OPER codemastr codeit
+
+CONNECT
+ - Links another IRC server to the one you are currently on. Remote connections are also    possible.
+ Syntax: CONNECT <server>
+ Syntax: <CONNECT> <hub> <port> <leaf>
+ Example: CONNECT leaf.*
+ Example: CONNECT hub.* 6667 leaf.*
+
+VERSION
+ - Provides version information of the IRCD software in usage.
+ Syntax: VERSION
+
+STATS
+ - Provides certain statistical information about the server (for example, u will provide    uptime information).
+ Syntax: STATS <letter>
+ Example: STATS u
+
+LINKS
+ - Lists all of the servers currently linked to the network.
+ Syntax: LINKS
+
+ADMIN
+ - Provides administrative information regarding the server.
+ Syntax: ADMIN <server>
+
+SAMODE
+ - Allowed a services administrator to change the mode on a channel, without having operator   status.
+ Syntax: SAMODE <channel> <mode>
+ Example: SAMODE #UnrealIRCD +m
+
+SVSKILL
+ - Can only be used by a U:Lined server. Forcefully disconnects a user from the network.
+ Syntax: SVSKILL <user> <reason>
+ Example: SVSKILL codemastr Goodbye
+
+SVSNOOP
+ - Can only be used by a U:Lined server. Enabled or disables whether Global IRCop functions   exist on the server in question or not.
+ Syntax: SVSNOOP <server> <+/->
+ Example: SVSNOOP leaf.* -
+
+MOTD
+ - Displays the Message of the Day.
+ Syntax: MOTD
+ Syntax: MOTD <server>
+
+KLINE
+ - "Bans" a hostmask from connection to the IRC server.
+ Syntax: KLINE <hostmask> <reason>
+ Example: KLINE *@*.aol.com Abuse
+
+UNKLINE
+ - Removes a k:line from the server.
+ Syntax: UNKLINE <hostmask>
+ Example: UNKLINE *@*.aol.com
+
+ZLINE
+ - Disables all access to the IRC server from a specified IP.
+ Syntax: ZLINE <ip>
+ Example: ZLINE 127.0.0.1
+
+UNZLINE
+ - Removes a currently active z:Line.
+ Syntax: UNZLINE <ip>
+ Example: ZLINE 127.0.0.1
+
+GLOBOPS
+ - Sends a global "message" to all IRCops. Only viewable by IRCops (unlike WallOps, which can be viewed by normal users).
+ Syntax: GLOBOPS <message>
+ Example: GLOBOPS Going to be akilling those clones...
+
+CHATOPS
+ - GLOBOPS is usually reserved for important network information. Therefore, for Oper Chat,    CHATOPS was invented. IRCops with the +c flag enabled will be able to send/receive CHATOPS messages.
+ Syntax: CHATOPS <message>
+ Example: CHATOPS How's everyone doing today?
+
+LOCOPS
+ - Similar to GLOBOPS, except only received by those IRCops local to your server.
+ Syntax: LOCOPS <message>
+ Example: LOCOPS Going to be adding a temp k:line for that user...
+
+REHASH
+ - Prompts the server to reread its configuration file (ircd.conf). Will also remove any    temporarly lines (i.e. k:line).
+ Syntax: REHASH
+
+RESTART
+ - Kills and restarts the irc daemon, disconnecting all users currently on that server.
+ Syntax: RESTART
+ Syntax: RESTART <password>
+
+DIE
+ - Kills the irc daemon, disconnecting all users currently on that server.
+ Syntax: DIE
+ Syntax: DIE <password>
+
+RULES
+ - Reads the rules.conf file and sends the contents to the user.
+ Syntax: RULES
+
+MAP
+ - Provides a "network map" of the IRC network. Mainly used for routing purposes.
+ Syntax: MAP
+
+DALINFO
+ - Original DALnet ircd credits.
+ Syntax: DALINFO
+
+MKPASSWD
+ - Used for generating an encrypted password. Mainly used for encrypted O:Line passwords.
+ Syntax: MKPASSWD <password>
+ Example: MKPASSWD codeit
+
+ADDLINE
+ - Adds a line to the server's ircd.conf file. After added, you must REHASH the server for it to take affect.
+ Syntax: ADDLINE <line>
+ Example: ADDLINE C:127.0.0.1:server.dal.net:linking:7325:50
+
+TECHAT
+ - Similar to CHATOPS, but only Technical Admins are able to send/receive messages on this    "channel".
+ Syntax: TECHAT <message>
+ Example: TECHAT What do you think of the new routing map?
+
+NACHAT
+ - Similar to CHATOPS (and TECHAT), but only Network Admins are able to send/recieve messages.
+ Syntax: NACHAT <message>
+ Example: NACHAT Linking a new server in a couple minutes...
+
+KNOCK
+ - For channels which are invite only, you can "knock" on the channel to request an invite.
+ Syntax: KNOCK <channel> <message>
+ Example: KNOCK #secret_chan I'm an op, let me in!
+
+CREDITS
+ - Credits for Unreal IRCD.
+ Syntax: CREDITS
+
+LICENSE
+ - GPL information.
+ Syntax: LICENSE
+
+SVSJOIN
+ - Forces a user to join a channel. Can only be used by a U:Lined server.
+ Syntax: SVSJOIN <nick> <channel>
+ Example: SVSJOIN codemastr #jail
+
+SAJOIN
+ - Forces a user to join a channel. Can only be used by a Services Admin.
+ Syntax: SAJOIN <nick> <channel>
+ Example: SAJOIN Stskeeps #OperHelp
+
+SVSPART
+ - Forces a user to leave a channel. Can only be used by a U:Lined server.
+ Syntax: SVSPART <nick> <channel>
+ Example: SVSPART codemastr #jail
+
+SAPART
+ - Forces a user to leave a channel. Can only be used by a Services Admin.
+ Syntax: SAPART <nick> <channel>
+ Example: SAPART Stskeeps #OperHelp
+
+SETHOST
+ - Changes the hostname of yourself. Only available to IRCops.
+ Syntax: SETHOST <host>
+ Example: SETHOST coder.tspre.org
+
+SETIDENT
+ - Changes the ident of yourself. Only available to IRCops.
+ Syntax: SETIDENT <ident>
+ Example: SETIDENT coder
+
+SETNAME
+ - Changes the "IRC Name" (or "Real Name") of yourself. Available to everyone.
+ Syntax: SETNAME <name>
+ Example: SETNAME Unreal Coding Team Member
+
+CHGHOST
+ - Changes the hostname of a user currently on the IRC network. Only available to IRCops.
+ Syntax: CHGHOST <nick> <host>
+ Example: CHGHOST codemastr coder.tspre.org
+
+CHGIDENT
+ - Changes the ident of a user currently on the IRC network. Only available to IRCops.
+ Syntax: CHGIDENT <nick> <ident>
+ Example: CHGIDENT codemastr coder
+
+CHGNAME
+ - Changes the "IRC Name" (or "Real Name") of a user currently on the IRC network. Only    available to IRCops.
+ Syntax: CHGNAME <nick> <name>
+ Example: CHGNAME codemastr Unreal Coding Team Member
+

doc/compiling_win32.txt

@@ -1,43 +0,0 @@
-==[ 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 got problems with NOSPOOF fix your client (bot?) instead (you should
-PONG back to the initial PING at connect).
-
-==[ HOW TO COMPILE UNREALIRCD WITHOUT SSL AT WINDOWS ]==
-First of all you need Microsoft Visual C++, compiling with cygwin
-is not supported.
-
-== "old" VC++ 6.0 ==
-1. You need the Platform SDK (PSDK)
-   Grab it at: http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ ->
-   core sdk -> install this sdk.
-   Note that this can take some time to download because it's >200Mb
-   (450mb installed) [!].
-2. To compile:
-   start -> programs -> platform sdk blabla -> open build env. -> (choose os) ->
-   set blabla build env (debug). This will launch a DOS window.
-3. 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
-4. Copy the src\win32\tre.dll to your UnrealIrcd main dir.
-5. Done!
-
-== VC++ 7.x (.NET) ==
-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!
-
-==[ HOW TO COMPILE UNREALIRCD WITH SSL AT WINDOWS ]==
-Ouch, that's much work ;).
-You need to compile openssl yourself.
-Then have a look at makefile.win32 for instruction on how
-to enable / specify path / etc...
-DO NOT ask us for help with compiling openssl!
-
-==[ AND ZIP LINKS SUPPORT? ]==
-See makefile.win32 for instructions.

doc/example.settings

@@ -1,53 +0,0 @@
-/*
- * Example set {} block
-*/
-
-set {
-	/*
- 	 * This is the mail users will get shown when k-lined
-	*/
-	kline-address		 "mail.to.mail.to";
-	/*
-	 * What modes will users get when connecting to this server
-	*/
-	modes-on-connect 	 "+ix";
-	/* What channels users will autojoin */
-	auto-join		 "0";
-	/* What channels opers will autojoin on connect*/
-	oper-auto-join		 "0";
-	dns {
-		/* What IP has our DNS server got? */
-		nameserver 127.0.0.1;
-		/* How long time will we wait for each attempt? */
-		timeout	2s;
-		/* How many attempts will we do */
-		retries 2s;
-	};
-	options {
-		enable-opermotd;
-		enable-chatops;
-		hide-ulines;
-//		webtv-support;
-		identd-check;
-	};
-	
-	/*
-	 * How many channels each user can join
-	*/
-	maxchannelsperuser 10;
-	/* 
-	 * This is a new thing in Unreal3.2.
-	 * You _need_ to make three numbers up, bigger than 100000
-	 * These MUST be the SAME on EVERY server in your NETWORK
-	 * If people discover these keys, it is easier for them to crack
-	 * the +x algoritm.
-	*/
-	cloak-keys
-	{
-		0;
-		0;
-		0;
-	};
-	
-};
-

doc/faq

@@ -0,0 +1,144 @@
+[ $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://www.unrealircd.com
+
+   Versions may be spewed out regulary due to new features and bugs.. 
+
+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.ircsystems.net #unrealircd
+
+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-2000

doc/features.txt

@@ -0,0 +1,109 @@
+
+RPL_PROTOCTL (RPL_ISUPPORT):
+ version: 2.1+ (new version: 3.1+)
+  
+ This sends a numeric during client signon that lists various features that
+ Unreal supports.  This allows client and script writers to know what features
+ they can use, and various parameters about the irc server.  The numeric
+ used is '005' to try and maintain some semblance of compatibility with
+ DALnet which has a similar feature.  The 005 numeric may be split across
+ multiple lines if the length exceeds 512 characters.
+
+ The format is:
+  :servername 005 target feature1 feature2... :are supported by this server.
+  :servername 005 target feature200... :are supported by this server.
+
+ features are either a word describing the feature eg: 'SILENCE', or a word
+ describing the feature and an equals and a list of parameters.  
+ eg: SILENCE=15 (says that we support silence, and we support up to 15 of
+ them per user), or FOO=12,3 (says we support FOO with parameters 12 and 3)
+ for example ircu2.10.08 lists:
+
+ :test.undernet.org 005 test SILENCE=15 WHOX WALLCHOPS USERIP CPRIVMSG 
+   CNOTICE MODES=6 MAXCHANNELS=10 MAXBANS=30 NICKLEN=9 TOPICLEN=160
+   KICKLEN=160
+ 
+-------------------------------------------------------------------------
+UnrealIRCd Supports:
+
+:unreal.server 005 nick MAP KNOCK SAFELIST HCN WATCH=%i SILENCE=%i MODES=%i
+                        MAXCHANNELS=%i MAXBANS=%i NICKLEN=%i TOPICLEN=%i
+                        KICKLEN=%i CHANTYPES=# PREFIX=%s :are supported by this server
+
+Feature "MAP"
+-------------
+
+ /map shows the servers as the server percieves them, who's connected
+ to who in a pretty display, with number of users attached to each server
+
+Numerics used:
+
+RPL_MAP (006)
+RPL_MAPEND (007)
+
+Feature "KNOCK"
+---------------
+
+Command: /KNOCK #Channel :<Reason>
+
+This command will only work if you are not a member of the channel and the
++K (No knocks) mode is not on, and the channel is not +i (and you are not
+banned). This will send a notice to ops in the channel, about that the user
+"knocked".
+
+Feature "SAFELIST"
+------------------
+
+
+This note means that the user will not get disconnected when doing a /list,
+as some IRC networks do
+
+Feature "HCN"
+-------------
+
+This is a special feature that you activate using /protoctl +HCN,
+that will cause +c notices when being oper, being in the Hybrid IRCd style
+
+Feature "WATCH"
+---------------
+
+Parameters: How many watch entries are possible
+
+This will ensure the server is able to do the DALnet WATCH command
+
+
+Feature "SILENCE"
+-----------------
+ Parameters: How many silence entries you can have
+ Version: unknown, ircu2.9.32 at least.
+
+ Silence is a server side ignore.  You can /silence +hostmask or
+ /silence +nick, to add someone to your silence list, or use /silence
+ -hostmask to remove it.  /silence will list your 'silence list'.
+ you can /silence nick, to see someone elses silence list (useful for
+ helping someone).  Silence is preferably used as a last resort as it
+ tends to use server CPU time.
+
+ Syntax:
+  SILENCE +hostmask
+  SILENCE +nick
+  SILENCE -hostmask
+  SILENCE -nick
+  SILENCE nick
+
+ reply:
+  RPL_SILELIST      217
+  RPL_ENDOFSILELIST 218
+
+
+Feature/Modifier "MODES"
+------------------------
+Parameters: How many modes with parameters you can use in one /mode buffer
+
+
+Feature/Modifier "MAXCHANNELS"
+------------------------------
+Parameters: How many channels a normal user can join (opers may have
+            unlimited)
+
+Feature/Modifier "MAXBANS"

doc/irc.1

@@ -0,0 +1,82 @@
+.\" $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

@@ -0,0 +1,140 @@
+.\" $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

@@ -0,0 +1,47 @@
+[ $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

@@ -0,0 +1,294 @@
+  [ $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

@@ -1,102 +0,0 @@
-Numeric 005 Documentation (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
-(As of Unreal3.2-beta11)
-
-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.
-
-Token         Value           Default Value                Description
-------------------------------------------------------------------------------------------------
-MAP           none            none                         Informs the client that the /map 
-                                                           command is present.
-
-KNOCK         none            none                         Informs the client that the /knock
-                                                           command is present.
-
-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.
-
-MAXBANS       number          60                           The maximum number of bans that
-                                                           may be placed for a channel.
-
-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.
- 
-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,k,lfL,                    Specifies how each channel mode is
-                              psmntirRcOAQKVHGCuzN         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    ~,cqr                        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.

doc/technical/base64.txt

@@ -1,11 +0,0 @@
-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

@@ -1,130 +0,0 @@
-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).

doc/technical/token.txt

@@ -1,122 +0,0 @@
-Token List (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
-(As of Unreal3.2-beta11)
-
-Command        Token 
-------------------------------------------------------------------------------------------------
-PRIVMSG        !
-WHO            \
-WHOIS          #
-WHOWAS         $
-USER           %
-NICK           &
-SERVER         '
-LIST           (
-TOPIC          )
-INVITE         *
-VERSION        +
-QUIT           ,
-SQUIT          -
-KILL           .
-INFO           /
-LINKS          0
-SUMMON         1
-STATS          2
-USERS          3
-HELP           4
-HELPOP         4
-ERROR          5
-AWAY           6
-CONNECT        7
-PING           8
-PONG           9
-OPER           ;
-PASS           <
-WALLOPS        =
-TIME           >
-NAMES          ?
-ADMIN          @
-NOTICE         B
-JOIN           C
-PART           D
-LUSERS         E
-MOTD           F
-MODE           G
-KICK           H
-USERHOST       J
-ISON           K
-REHASH         O
-RESTART        P
-CLOSE          Q
-DIE            R
-HASH           S
-DNS            T
-SILENCE        U
-AKILL          V
-KLINE          W
-UNKLINE        X
-RAKILL         Y
-GNOTICE        Z
-GOPER          [
-GLOBOPS        ]
-LOCOPS         ^
-PROTOCTL       _
-WATCH          `
-TRACE          b
-SQLINE         c
-UNSQLINE       d
-SVSNICK        e
-SVSNOOP        f
-SVSKILL        h
-SVSMODE        n
-SAMODE         o
-CHATOPS        p
-ZLINE          q
-UNZLINE        r
-RULES          t
-MAP            u
-SVS2MODE       v
-DALINFO        w
-ADCHAT         x
-MKPASSWD       y
-ADDLINE        z
-GLINE          }
-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
-ADDMODE        AQ
-ADDOMODE       AR
-SVSMODE        AS
-SMO            AU
-OPERMOTD       AV
-TSCTL          AW
-SAJOIN         AX
-SAPART         AY
-CHGIDENT       AZ
-SWHOIS         BA
-SVSO           BB
-SVSFLINE       BC
-TKL            BD
-VHOST          BE
-BOTMOTD        BF
-HTM            BH
-SHUN           BL
-SVSJOIN        BR
-SVSPART        BT
-SJOIN          ~
-UMODE2         |
-
-
-
-
-

doc/technical/vl.txt

@@ -1,32 +0,0 @@
-VL Information (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
-(As of Unreal3.2-beta11)
-
-Protocol       Version
-------------------------------------------------------------------------------------------------
-2303           3.2-Selene
-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
-E              Extended channel modes supported

doc/unrealircd.conf

@@ -0,0 +1,233 @@
+/*
+ * UnrealIRCd Config File - Example for irc.fyremoon.net
+*/
+
+// Information about me
+me {
+	// My IRC server name
+	name "irc.fyremoon.net";
+        // My infoline
+	info "Forever is gonna start tonight";
+	// My numeric
+	numeric 13;
+};
+
+// Who is my admin?
+
+admin {
+        /* You can put as many lines as you want here */
+	"Carsten Munk";
+	"Stskeeps";
+	"stskeeps@tspre.org";	
+};
+
+/* We use class names now :)*/
+class clients
+{
+	/* How often to ping the user */
+	pingfreq 90;
+	/* How many clients allowed in class*/
+	maxclients 900;
+	/* Maximum SendQueue */
+	sendq 100000;
+};
+
+class servers
+{
+	pingfreq 90;
+	maxclients 1;
+	sendq 1000000;
+};
+
+/* The old I:lines */
+allow {
+	/* username mask*/
+	user *;
+	/* ip mask */
+	ip *; 
+	/* hostmask */
+	hostname *;
+	/* what class to put them in */
+	class clients;
+ 	// Leave out password to make it passwordless
+ 	/* Password to require */
+        password "moocowsrule";
+};
+
+/* /oper <login> (oper <login>)*/
+oper stskeeps {
+	/* What class to put oper in upon opering */
+	class clients;
+	/* What userhost masks to allow the IRCop to come from */
+	from {
+		userhost *@the.elite-hacker.cx;
+		userhost *@*.image.dk;
+	};
+	/* Password to require */
+	password "moocow";
+	/* We use named flags now :) */
+	flags
+	{
+		netadmin;
+		global;
+	};
+};
+
+/* P:lines, we listen here on IP 127.0.0.1 port 6667 */
+listen *:6601
+{
+  options
+  {
+       ssl;
+       serversonly;
+  };
+};
+
+listen *:8067;
+listen *:6600;
+
+link irc.hs-bremen.de /* servername */
+{
+	username	*; /* usermask */
+	hostname	194.94.24.40; /* hostmask */
+	bind-ip		*; /* What IP to bind to when connecting */
+	port		7151; /* What port to connect to, if any */
+	hub *;   /* Is this a hub and what servermasks may it bring in */
+	
+	// 	leaf *;
+	//	leaf-depth 2;
+	password-connect "tdx6667";
+	password-recieve "tdx6667";
+	/* for later: class-connect, class-recieve */
+	class		servers;
+	// rsa-auth "path.to.public.key";
+	options {
+		autoconnect;
+		ssl;
+		zip;
+	};
+};
+
+/* As many as you like */
+ulines {
+	services.roxnet.org;
+	stats.roxnet.org;
+};
+
+drpass {
+	restart 	"time-to-restart"; /* Password to use for /restart */
+	die 		"killme"; /* Password to use for /die */
+};
+
+/*
+ * The old T:lines. We however also can use this as auto-join per .domain
+*/
+tld {
+	mask *@*.fr;
+	motd "ircd.motd.fr";
+	rules "ircd.rules.fr";
+};	
+
+/* The old nick Q:lines :) */
+ban nick { 
+       mask "*C*h*a*n*S*e*r*v*";
+       reason "Reserved for Services";
+};
+/* The old Z:lines */
+ban ip { mask 195.86.232.81; reason "Delinked server"; };
+
+/* The old server Q:lines */
+ban server {
+	mask eris.berkeley.edu;
+	reason "Get out of here.";
+};
+
+/* The wonderful K:lines */
+ban user { mask *tirc@*.saturn.bbn.com; reason "Idiot"; };
+
+/* Bans Realnames, the old n:lines */
+ban realname {
+	mask "Swat Team";
+	reason "mIRKFORCE";
+};
+
+ban realname {
+	mask "sub7server";
+	reason "sub7";
+};
+
+
+/* Do not ban Stskeeps 
+ * The old E:lines
+*/
+except ban {
+	mask *stskeeps@212.*;
+};
+
+/* savage-r.*
+ * the old e: lines 
+ */
+except socks {
+	mask 216.73.27.177;	
+};
+
+/* Old vhost.conf */
+vhost {
+	vhost		i.hate.microsefrs.com;
+	userhost	*@*.image.dk;
+	login		stskeeps;
+	password	techie;
+};
+
+/* You can include other configuration files */
+// include "klines.conf";
+
+// Network configuration
+set {
+	network-name 		"ROXnet";
+	default-server 		"irc.roxnet.org";
+	services-name 		"services.roxnet.org";
+	stats-name		"stats.roxnet.org";
+	help-channel		"#ROXnet";	
+	hiddenhost-prefix    	"rox";
+	prefix_quit		"no";
+	/* on-oper host */
+	hosts {
+		local		"locop.roxnet.org";
+		global		"ircop.roxnet.org";
+		coadmin		"coadmin.roxnet.org";
+		admin   	"admin.roxnet.org";
+		servicesadmin	"csops.roxnet.org";
+		techadmin	"techadmin.roxnet.org";
+		netadmin	"netadmin.roxnet.org";
+		host-on-oper-up	"no";
+	};
+};	
+
+/* Server specific configuration */
+
+set {
+	kline-address		 "stskeeps@roxnet.org";
+	modes-on-connect 	 "+xwG";
+	oper-auto-join		 "#opers";
+	dns {
+		nameserver 127.0.0.1;
+		timeout	2s;
+		retries 2s;
+	};
+	options {
+		enable-opermotd;
+		enable-chatops;
+		hide-ulines;
+		webtv-support;
+		identd-check;
+	};
+	
+	socks {
+		ban-message "Insecure SOCKS server";
+		quit-message "Insecure SOCKS server";
+		ban-time "4d";
+	};
+	maxchannelsperuser 10;
+	
+};

dynconf

@@ -0,0 +1,21 @@
+                    [ $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.roxnet.org, #unrealircd
+My nick is mostly Stskeeps or Techie (or Nightwalker if i had a bad night:P)
+
+--Stskeeps

extras/burst.c

@@ -136,10 +136,7 @@ int create_client(const char *hostname, const int hostport) {
   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);

extras/channeldumper.c

@@ -1,128 +0,0 @@
-/*
- *   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

@@ -1,151 +0,0 @@
-/*
- * 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;
-
-#ifndef DYNAMIC_LINKING
-ModuleHeader defizzer_Header
-#else
-#define defizzer_Header Mod_Header
-ModuleHeader Mod_Header
-#endif
-  = {
-	"defizzer",	/* Name of module */
-	"$Id$", /* Version */
-	"de-Fizzer", /* Short description of module */
-	"3.2-b8-1",
-	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(ModuleInfo *modinfo)
-#else
-int    defizzer_Init(ModuleInfo *modinfo)
-#endif
-{
-	bcopy(modinfo,&DefizzerModInfo,modinfo->size);
-	LocConnect = HookAddEx(DefizzerModInfo.handle, HOOKTYPE_PRE_LOCAL_CONNECT, h_defizzer_connect);
-	return MOD_SUCCESS;
-}
-
-/* Is first run when server is 100% ready */
-#ifdef DYNAMIC_LINKING
-DLLFUNC int	Mod_Load(int module_load)
-#else
-int    defizzer_Load(int module_load)
-#endif
-{
-}
-
-
-/* Called when module is unloaded */
-#ifdef DYNAMIC_LINKING
-DLLFUNC int	Mod_Unload(int module_unload)
-#else
-int	defizzer_Unload(int module_unload)
-#endif
-{
-	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,43 +1 @@
-
-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

@@ -1,157 +0,0 @@
-/*
- *   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/tsp/Makefile

@@ -0,0 +1,12 @@
+all: client server
+
+client:
+	gcc -o tsp-client tsp-client.c sscript.c
+
+server:
+	gcc -o tsp-server-run tsp-server-run.c
+	gcc -o tsp-skin socker.c
+
+clean:
+	rm -f *~
+	rm -f tsp-server-run tsp-client tsp-skin

extras/tsp/README

@@ -0,0 +1,26 @@
+
+how to use tsp-client:
+
+first make it "make"
+
+then run it like this:
+$ ./tsp-client <tsp server> <port>
+
+do this a couple of times
+if the answers come within 1 second count its right
+then take the most common time difference count and do in UnrealIRCd like
+this:
+
+/quote tsctl offset + <difference count>
+
+then your server is time synched
+
+current tsp servers online:
+
+server           port
+-----------------------------
+irc.flirt.org    6100
+
+
+if you want to make your own TSP server (must be a box using NTP)
+run ./tsp-server, it will then start running on port 6100

extras/tsp/README.sscript

@@ -0,0 +1,40 @@
+
+
+                    Socket Script C library
+                    -----------------------
+
+Home page:
+http://www.linsupport.com
+
+This is a simple library that provides usefull functions for C 
+networking applications. It's based on the Socket Script scripting
+language, but meant for C programmers. These functions are really
+shortcuts to C functions, meant to make their use simple.
+
+This can create a static lib: libsscript.a
+
+To compile:
+
+make
+
+Then to install it:
+
+make install
+
+
+(C) Copyright 1998-2000 Patrick Lambert <drow@post.com>
+
+This library is under the LGPL license which means:
+
+1- You can copy and use this program freely.
+
+2- You may not claim that you wrote it.
+
+3- If you want to include parts of this software in your own product,
+you can do so if that product stays under free software and if all
+copyright notices in source and documentation, as well as the no warranty
+comment, remains.
+
+4- This program is distributed without ANY WARRANTY, without even
+the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
+PURPOSE.

extras/tsp/socker.c

@@ -0,0 +1,149 @@
+/*
+	SOCKER Socket redirector  version 0.1
+	Patrick Doyle  Oct 1998
+	Based on tserver by Michael Johnson and Erik Troan
+
+	Puts a normal stdin & stdout based program up on a port
+	as a server process.  Each connection spawns a new copy
+	of the program.
+
+	Please notify me of any changes to this code tha you
+	subsequently redistribute.  I can be contacted at
+	patrick@minotaursoftware.com.
+
+	Also, please leave my name and those of Michael Johnson
+	and Erik Troan at the top of this file.
+*/
+
+#include <stdlib.h>
+#include <stdio.h>
+#include <string.h>
+#include <unistd.h>
+#include <signal.h>
+#include <netinet/in.h>
+#include <sys/socket.h>
+#include <arpa/inet.h>
+#include <sys/types.h>
+#include <sys/wait.h>
+
+#define ZOMBIE  /* Causes zombies to be collected.  Only works under Linux. */
+
+#define debug printf
+#undef debug
+void debug(char *format, ...){}
+
+int sock = -1;
+
+void die(char *msg){
+	perror(msg);
+	exit(1);
+}
+
+void handle_sig(int signum){
+	if(signum == SIGCHLD){
+		/* Collect exit statuses.  Prevent zombies. */
+		int status;
+		while(0 < waitpid(-1, &status, WNOHANG));
+	}else{
+		fprintf(stderr, "\nSocker exiting normally.\n");
+		close(sock);
+		exit(0);
+	}
+}
+
+#define asizeof(x) (sizeof(x)/sizeof(x[0]))
+
+void setup_sig_handler(){
+	int sa_num;
+	static int sigs[] = {
+		SIGHUP, SIGINT, SIGQUIT, SIGXCPU, SIGXFSZ, SIGTERM
+#	ifdef ZOMBIE
+		, SIGCHLD
+#	endif
+	};
+	static struct sigaction sig_actions[asizeof(sigs)];
+	debug("Starting setup_sig_handler\n");
+	memset(sig_actions, 0, sizeof(sig_actions));
+	sig_actions[0].sa_handler = handle_sig;
+	sigemptyset(&(sig_actions[0].sa_mask));
+	for(sa_num=1; sa_num < asizeof(sigs); sa_num++){
+		memcpy(sig_actions+sa_num, sig_actions, sizeof(sig_actions[0]));
+	}
+	for(sa_num=0; sa_num < asizeof(sigs); sa_num++){
+		if(sigaction(sigs[sa_num],  sig_actions+sa_num, NULL))
+			die("sigaction");
+	}
+#	ifdef ZOMBIE
+	siginterrupt(SIGCHLD, 0); /* Don't let SIGCHLD interrupt socket calls */
+#	endif
+	debug("Ending setup_sig_handler\n");
+}
+
+int main(int argc, char *argv[]) {
+	struct sockaddr_in address;
+	int conn, i, portnum;
+	size_t addrLength = sizeof(struct sockaddr_in);
+
+	fprintf(stderr, "SOCKER  Socket Redirector  Patrick Doyle  Oct 1998\n");
+
+	if (argc < 3 || !(portnum = atoi(argv[1]))){
+		fprintf(stderr, "Usage: socker {port_num} {command}\n");
+		fprintf(stderr, "Waits for TCP connections on the given port, and then\n");
+		fprintf(stderr, "spawns a new process executing {command} for each connection.\n");
+		fprintf(stderr, "Exit status: 0=caught signal and exited; 1=error\n");
+		exit(1);
+	}
+
+	if ((sock = socket(PF_INET, SOCK_STREAM, 0)) < 0)
+		die("socket");
+
+	debug("Calling setup_sig_handler\n");
+	setup_sig_handler();
+
+	/* Let the kernel reuse the socket address. This lets us run
+	   twice in a row, without waiting for the (ip, port) tuple
+	   to time out. */
+	i = 1;
+	setsockopt(sock, SOL_SOCKET, SO_REUSEADDR, (void*)&i, i); 
+
+	address.sin_family = AF_INET;
+	address.sin_port = htons(portnum);
+	memset(&address.sin_addr, 0, sizeof(address.sin_addr));
+
+	if (bind(sock, (struct sockaddr *) &address, sizeof(address)))
+		die("bind");
+
+	if (listen(sock, 5))
+		die("listen");
+
+	while ((conn = accept(sock, (struct sockaddr *) &address, &addrLength)) >= 0) {
+		if(fork()){ /* Parent; loop back to accept another */
+			close(conn);
+		}else{ /* Child; exec given command line */
+			close(sock);
+			/* Redirect stdin & stdout to socket */
+			if(0 != dup2(conn, 0) || 1 != dup2(conn, 1))
+				die("dup2 redirection");
+			/* Turn off buffering */
+			/* Note: this seems to have no effect beyond execvp */
+			setbuf(stdin, 0);
+			setbuf(stdout, 0);
+			setbuf(stderr, 0);
+			/* Execute command */
+			execvp(argv[2], argv+2);
+			/* Error if we get here */
+			fprintf(stderr, "execvp failed.  Please make sure that '%s' refers to a valid program.\n", argv[2]);
+			_exit(1)/*
+				man fork says _exit should be called to prevent parent from
+				being corrupted.
+			*/;
+		}
+	}
+
+	if (conn < 0) 
+		die("accept");
+	
+	/* Shouldn't get here */
+	close(sock);
+	return 2;
+}

extras/tsp/sscript-lib.doc

@@ -0,0 +1,115 @@
+Socket Script Library 2.0
+-------------------------
+
+Here are the functions and errno code numbers returned by some of SScript's
+functions:
+
+errno:
+SSCRIPT_SOCKET_FAILED             10
+SSCRIPT_BIND_FAILED               11
+SSCRIPT_GETSOCKETNAME_FAILED      12
+SSCRIPT_FLAGS_FAILED              13
+SSCRIPT_CONNECT_FAILED            20
+SSCRIPT_UDPSEND_FAILED            31
+SSCRIPT_UDPRECEIVE_FAILED         32
+SSCRIPT_READ_FAILED               33
+
+The following are the SScript functions available in this library.
+They return either a string, an int or void. If an error occurs, it returns
+NULL (in case of a string) or -1 (in case of an int) and sets errno to
+the right error code (see above). Note that since each connection is
+associated with a socket number (sockfd), it is possible to make
+multiple connections.
+
+- char *sscript_lindex(char *input_string, int word_number);
+Get <word_number> from <input_string>. Returns the requested word.
+
+- char *sscript_lrange(char *input_string, int starting_at);
+Return everything after <starting_at> in <input_string>.
+
+- int sscript_connect(char *server, int port, char *virtual);
+Connect to <server> at port <port>, binding to virtual address
+<virtual>. If no binding is required, use NULL. Returns the socket
+number.
+
+- int sscript_server(int port);
+Initialize a server socket. Returns the socket number.
+
+- int sscript_wait_clients(int sockfd, int port, int forking);
+Listen to port <port> and wait for clients. This function is a
+blocking function. It will stay there untill it gets a client, and when
+it does, it will create a child and return its associated socket number.
+The child will go in the background if <forking> is set to 1
+(required for multithreading). This returns the child' sockfd.
+
+- char *sscript_get_remote_ip();
+This function returns the IP that connected to a server-oriented program.
+
+- void sscript_disconnect(int sockfd);
+Diconnects the connection pointed by <sockfd>.
+
+- void sscript_dump(int sockfd, char *filename);
+Dumps the content of <filename> to the connection pointed by <sockfd>.
+
+- void sscript_ping(char *hostname);
+Sends a TCP ping (echo to port 7) to <hostname>. This is a blocking
+function and only returns if the ping worked.
+
+- int sscript_test(char *hostname, int port);
+This tests if port <port> from <hostname> is open. Returns 0 if it is.
+
+- char *sscript_version();
+Returns the current library version.
+
+- char *sscript_read(int sockfd, int chop);
+Read from the connection pointed by <sockfd> and clear the last
+char if <chop> is set to 1.
+
+- void sscript_write(int sockfd, char *string);
+Write <string> to the connection pointed by <sockfd>.
+
+- int sscript_udp_send(char *hostname, int port, char *msg);
+Send an UDP packet to <hostname> at port <port> containing the message <msg>
+
+- char *sscript_udp_listen(int port);
+Listen for UDP packets on port <port>. Available to root only.
+
+- char *sscript_icmp_detect();
+Listen for ICMP messages and return the type (see ICMP.types) and the IP
+that sent one. Available to root only.
+
+- char *sscript_resolve_host(char *hostname);
+Resolve <hostname> into an IP.
+
+- char *sscript_resolve_ip(char *ip);
+Resolve <ip> into an hostname.
+
+- char *sscript_get_localhost();
+Get the local hostname.
+
+- void sscript_binary_send(int sockfd, char *filename);
+This function sends a binary file.
+
+- void sscript_binary_get(int sockfd);
+This function receives a binary file.
+
+- char *sscript_login_to_passwd(char *login)
+This function converts a login name to its crypted password.
+
+- char *sscript_uid_to_login(long uid)
+This function finds the login name for the UID provided.
+
+- int sscript_sokstat(char *option, int sockfd)
+This will give the settings for the currently open socket sockfd. Option
+is what you want the setting of and can be sendbuf, recvbuf, error or type.
+
+- char *sscript_time_read(int sockfd, int time);
+This function reads from sockfd for time secs, and then returns what it
+read, or "timeout".
+
+- void sscript_redir(int sockfd1, int sockfd2);
+This function will redirect packets from sockfd1 to sockfd2, and the
+other way around.
+
+- void sscript_nodelay(int sockfd);
+Set the socket in non-blocking mode.

extras/tsp/sscript.c

@@ -0,0 +1,509 @@
+/*
+* SScript - See the sscript.doc
+* (C) 1998 Drow <drow@wildstar.net>
+* http://devplanet.fastethernet.net
+*/
+
+#include "sscript.h"
+#include <string.h>
+#include <sys/types.h>
+#include <sys/socket.h>
+#include <sys/time.h>
+#include <netinet/in.h>
+#include <net/if.h>
+#include <strings.h>
+#include <sys/file.h>
+#include <signal.h>
+#include <unistd.h>
+#include <netdb.h>
+#include <arpa/inet.h>
+#ifndef FNDELAY
+#define FNDELAY O_NONBLOCK
+#endif
+#ifdef POSIX
+#include <pwd.h>
+#include <sys/utsname.h>
+#endif
+
+char global_var[9][1024]; /* need to find why gcc outputs warns without this */
+char remoteIP[30];
+
+char *sscript_lindex(char *input_string, int word_number)
+{
+ char *tokens[1024];
+ static char tmpstring[1024];
+ int i;
+ strncpy(tmpstring,input_string,1024);
+ (char *)tokens[i=0] = (char *)strtok(tmpstring, " ");
+ while (((char *)tokens[++i] = (char *)strtok(NULL, " ")));
+ tokens[i] = NULL;
+ return(tokens[word_number]);
+}
+
+int sscript_connect(char *server, int port, char *virtual)
+{
+ struct sockaddr_in address;
+ struct sockaddr_in la;
+ int len, sockfd;
+ sockfd = socket(AF_INET, SOCK_STREAM, 0);
+ if(sockfd<1) 
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return -1;
+ }
+ address.sin_family = AF_INET;
+ address.sin_addr.s_addr = inet_addr(server);
+ address.sin_port = htons(port);
+ len = sizeof(address);
+ if(virtual!=NULL)
+ {
+  la.sin_family = AF_INET;
+  la.sin_addr.s_addr = inet_addr(virtual);
+  la.sin_port = 0;
+  bind(sockfd, (struct sockaddr *)&la, sizeof(la));
+ }
+ if(connect(sockfd, (struct sockaddr *)&address, len)<0)
+ {
+  errno = SSCRIPT_CONNECT_FAILED;
+  return -1;
+ }
+ return sockfd;
+}
+
+int sscript_server(int port)
+{
+ int sockfd2, listen_len;
+ struct sockaddr_in listen_addr;
+ sockfd2 = socket(AF_INET, SOCK_STREAM, 0);
+ if(sockfd2<1)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return -1;
+ }
+ listen_addr.sin_family = AF_INET;
+ listen_addr.sin_addr.s_addr = htonl(INADDR_ANY);
+ listen_addr.sin_port = htons(port);
+ listen_len = sizeof(listen_addr); 
+ if(bind(sockfd2, (struct sockaddr *)&listen_addr, listen_len))
+ {
+  errno = SSCRIPT_BIND_FAILED;
+  return -1;
+ }
+ return sockfd2;
+}
+
+int sscript_wait_clients(int sockfd2, int port, int forking)
+{
+ int sockfd=(int)NULL,len,from_len,pid;
+ struct sockaddr_in address;
+ struct sockaddr_in from_addr;
+ struct sockaddr_in listen_addr;
+ listen_addr.sin_family = AF_INET;
+ listen_addr.sin_addr.s_addr = htonl(INADDR_ANY);
+ listen_addr.sin_port = htons(port);
+ len = sizeof(address);
+ listen(sockfd2, 5);
+ for(;;)
+ {
+  if(forking) if(sockfd!=(int)NULL) close(sockfd);
+  sockfd = accept(sockfd2, (struct sockaddr *)&address, &len);
+  if(forking) if((pid=fork())) break;
+ }
+ from_len=sizeof(from_addr);
+ memset(&from_addr, 0, sizeof(from_addr));
+ if(getpeername(sockfd, (struct sockaddr *)&from_addr,&from_len) < 0)
+ {
+  strcpy(remoteIP,"unknown");
+ }
+ else
+ {
+  strcpy(remoteIP,inet_ntoa(from_addr.sin_addr));
+ }
+ return sockfd;
+}
+
+char *sscript_get_remote_ip()
+{
+ return remoteIP;
+}
+
+void sscript_disconnect(int sockfd)
+{
+ shutdown(sockfd,2);
+ close(sockfd);
+}
+
+void sscript_dump(int sockfd, char *filename)
+{
+ char temp[1024]="";
+ FILE *fpa;
+ fpa=fopen(filename,"r");
+ if(fpa==NULL) return;
+ while(fgets(temp,1024,fpa)!=NULL)
+  write(sockfd, temp, strlen(temp));
+ fclose(fpa);
+}
+
+void sscript_ping(char *hostname)
+{
+ struct sockaddr_in other_addr;
+ int sockfd, result;
+ char temp[255];
+ sockfd=socket(AF_INET, SOCK_STREAM, 0);
+ if(sockfd<0)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return;
+ }
+ other_addr.sin_family = AF_INET;
+ other_addr.sin_addr.s_addr = inet_addr(hostname);
+ other_addr.sin_port = htons(7);
+ connect(sockfd, (struct sockaddr*) &other_addr,sizeof(other_addr));
+ result=write(sockfd,"ping\n",strlen("ping\n"));
+ result=read(sockfd,temp,result);
+ close(sockfd);
+}
+
+int sscript_test(char *hostname, int port)
+{
+ int sockfd;
+ struct sockaddr_in other_addr;
+ if((sockfd=socket(AF_INET, SOCK_STREAM, 0))<0)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return -1;
+ }
+ other_addr.sin_family = AF_INET;
+ other_addr.sin_addr.s_addr = inet_addr(hostname);
+ other_addr.sin_port = htons(port);
+ if(connect(sockfd, (struct sockaddr*)&other_addr,sizeof(other_addr))==-1)
+ {
+  errno = SSCRIPT_CONNECT_FAILED;
+  close(sockfd);
+  return -1;
+ }
+ close(sockfd);
+ return 0;
+}
+
+char *sscript_version()
+{
+ return ABOUT;
+}
+
+char *sscript_read(int sockfd, int chop)
+{
+ int i, result;
+ char inchar;
+ char string[1024];
+ bzero(string,1024);
+ strcpy(string,"");
+ for(i=0;(result=read(sockfd,&inchar,1))!='\0';i++)
+ {
+  string[i]=inchar;
+  if(inchar=='\n') break;
+ }
+ if (chop) string[i-1]=' ';
+ strcpy(global_var[0],string);
+ return global_var[0];
+}
+
+void sscript_write(int sockfd, char *string)
+{
+ write(sockfd, string, strlen(string));
+}
+
+int sscript_compare(char *case1, char *case2)
+{
+ return (strcmp(case1,case2));
+}
+
+char *sscript_lrange(char *input_string, int starting_at)
+{
+ char *tokens[555];
+ static char tmpstring[512]="";
+ int i;
+ char out_string[512]="";
+ strcpy(out_string,"");
+ if(input_string==NULL) {
+  strcpy(out_string," ");
+  strcat(out_string,NULL);
+  strcpy(global_var[1],out_string);
+  return global_var[1]; }
+ strcpy(tmpstring,input_string);
+ (char *)tokens[i=0] = (char *)strtok(tmpstring, " ");
+ while(((char *)tokens[++i] = (char *)strtok(NULL, " ")));
+ tokens[i] = NULL;
+ i++;
+ if(i<starting_at) return (int)NULL;
+ while(tokens[starting_at] != NULL)
+ {
+  strcat(out_string,tokens[starting_at]);
+  strcat(out_string, " ");
+  starting_at++;
+ }
+ strcpy(global_var[2],out_string);
+ return global_var[2];
+}
+
+int sscript_udp_send(char *hostname, int port, char *msg)
+{
+ int udpsock;
+ struct sockaddr_in udpaddr;
+ udpsock = socket(AF_INET, SOCK_DGRAM, 0);
+ if(udpsock<0)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return -1;
+ }
+ udpaddr.sin_family = AF_INET;
+ udpaddr.sin_port = htons(port);
+ udpaddr.sin_addr.s_addr = inet_addr(hostname);
+ if(sendto(udpsock,msg,sizeof(msg),0,(struct sockaddr *)&udpaddr,sizeof(udpaddr))<0)
+ {
+  errno = SSCRIPT_UDPSEND_FAILED;
+  return -1;
+ }
+ return 0;
+}
+
+char *sscript_udp_listen(int port)
+{
+ int udpsock,len;
+ struct sockaddr_in udpaddr, from;
+ char msg[255];
+ udpsock = socket(AF_INET, SOCK_DGRAM, 0);
+ if(udpsock<0)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return (char *)NULL;
+ }
+ udpaddr.sin_family = AF_INET;
+ udpaddr.sin_addr.s_addr = INADDR_ANY;
+ udpaddr.sin_port = htons(port);
+ if(bind(udpsock,(struct sockaddr *)&udpaddr,sizeof(udpaddr))<0)
+ {
+  errno = SSCRIPT_BIND_FAILED;
+  close(udpsock);
+  return (char *)NULL;
+ }
+ len = sizeof(from);
+ if(recvfrom(udpsock,msg,sizeof(msg),0,(struct sockaddr *)&from,&len)<0)
+ {
+  errno = SSCRIPT_UDPRECEIVE_FAILED;
+  close(udpsock);
+  return (char *)NULL;
+ }
+ close(udpsock);
+ strcpy(global_var[3],msg);
+ return global_var[3];
+}
+
+char *sscript_icmp_detect()
+{
+ int icmpsock,len,result,type;
+ struct sockaddr_in icmpaddr;
+ char readbuf[1024]="";
+ char msg[255];
+ if((icmpsock=socket(AF_INET, SOCK_RAW, IPPROTO_ICMP))<0)
+ {
+  errno = SSCRIPT_SOCKET_FAILED;
+  return (char *)NULL;
+ }
+ icmpaddr.sin_family = AF_INET;
+ icmpaddr.sin_addr.s_addr = INADDR_ANY;
+ icmpaddr.sin_port = 0;
+ if(bind(icmpsock,(struct sockaddr *)&icmpaddr,sizeof(icmpaddr))<0)
+ {
+  errno = SSCRIPT_BIND_FAILED;
+  close(icmpsock);
+  return (char *)NULL;
+ }
+ len=sizeof(icmpaddr);
+ if(getsockname(icmpsock,(struct sockaddr *)&icmpaddr,&len)<0)
+ {
+  errno = SSCRIPT_GETSOCKETNAME_FAILED;
+  close(icmpsock);
+  return (char *)NULL;
+ }
+ if((result=read(icmpsock,readbuf,sizeof(readbuf)))<0)
+ {
+  errno = SSCRIPT_READ_FAILED;
+  close(icmpsock);
+  return (char *)NULL;
+ }
+ type=readbuf[20] & 0xff;
+ sprintf(msg,"%d %d.%d.%d.%d ",type,readbuf[12]&0xff,readbuf[13]&0xff,readbuf[14]&0xff,readbuf[15]&0xff);
+ close(icmpsock);
+ strcpy(global_var[4],msg);
+ return global_var[4];
+}
+
+char *sscript_resolve_host(char *hostname)
+{
+ struct hostent *hp;
+ struct sockaddr_in from;
+ char result[255];
+ memset(&from, 0, sizeof(struct sockaddr_in));
+ from.sin_family = AF_INET;
+ hp=gethostbyname(hostname);
+ if(hp==NULL) strcpy(result,"unknown");
+ else
+ {
+  memcpy(&from.sin_addr,hp->h_addr,hp->h_length);
+  strcpy(result,inet_ntoa(from.sin_addr));
+ }
+ strcpy(global_var[5],result);
+ return global_var[5];
+}
+
+char *sscript_resolve_ip(char *ip)
+{
+ struct hostent *hp;
+ struct sockaddr_in from;
+ char result[255];
+ from.sin_family = AF_INET;
+ from.sin_addr.s_addr = inet_addr(ip);
+ hp=gethostbyaddr((char *)&from.sin_addr, sizeof(struct in_addr),from.sin_family);
+ if(hp==NULL) strcpy(result,"unknown");
+ else strcpy(result,(char *)hp->h_name);;
+ strcpy(global_var[6],result);
+ return global_var[6];
+}
+
+char *sscript_get_localhost()
+{
+ char result[255];
+ gethostname(result,sizeof(result));
+ strcpy(global_var[7],result);
+ return global_var[7];
+}
+
+void sscript_binary_send(int sockfd, char *string)
+{
+ char temp4[255], temp2[255];
+ int cnt;
+ FILE *fpa;
+ sprintf(temp4,"uuencode %s %s > %s/.temp.uue 2>/dev/null",string,string,TMP_DIR);
+ system(temp4);
+ sprintf(temp2,"%s/.temp.uue",TMP_DIR);
+ fpa=fopen(temp2,"r");
+ if(fpa==NULL || fileno(fpa)<0) return;
+ else {
+  while((cnt = read(fileno(fpa), temp4, 250))>0)
+  write(sockfd, temp4, cnt);
+  if(fpa!=NULL) fclose(fpa);
+  sprintf(temp4,"rm -f %s/.temp.uue",TMP_DIR);
+  system(temp4);
+ }
+}
+
+void sscript_binary_get(int sockfd)
+{
+ char temp2[255], temp4[255], inchar, inall[1024];
+ FILE *fpa;
+ int i;
+ sprintf(temp2,"%s/.temp.uue",TMP_DIR);
+ fpa=fopen(temp2,"w");
+ if(fpa==NULL || fileno(fpa)<0) return;
+ while(strcasecmp(inall,"end\n"))
+ {
+  bzero(inall, 1024);
+  for(i=0;read(sockfd,&inchar,1)!='\0';i++)
+  {
+   inall[i]=inchar;
+   if(inchar=='\n') break;
+  }
+  fputs(inall,fpa);
+ }
+ if(fpa!=NULL) fclose(fpa);
+ sprintf(temp4,"uudecode %s/.temp.uue",TMP_DIR);
+ system(temp4);
+ sprintf(temp4,"rm -f %s/.temp.uue",TMP_DIR);
+ system(temp4);
+}
+
+char *sscript_login_to_passwd(char *login)
+{
+#ifdef POSIX
+ struct passwd *pw;
+ pw = getpwnam(login);
+ if(pw!=NULL) return pw->pw_passwd;
+#endif
+ return (char *)NULL;
+}
+
+char *sscript_uid_to_login(long my_uid)
+{ 
+#ifdef POSIX
+ struct passwd *pw;
+ pw = getpwuid(my_uid);
+ if(pw!=NULL) return pw->pw_name;
+#endif
+ return (char *)NULL;
+}
+
+int sscript_sokstat(char *option, int sockfd)
+{  
+ int optlen=sizeof(int),optval=1;
+ if(!strcasecmp(option,"sendbuf")) getsockopt(sockfd, SOL_SOCKET, SO_SNDBUF, (char *)&optval, &optlen);
+ else if(!strcasecmp(option,"recvbuf")) getsockopt(sockfd, SOL_SOCKET, SO_RCVBUF, (char *)&optval, &optlen);
+ else if(!strcasecmp(option,"error")) getsockopt(sockfd, SOL_SOCKET, SO_ERROR, (char *)&optval, &optlen);
+ else if(!strcasecmp(option,"type")) getsockopt(sockfd, SOL_SOCKET, SO_TYPE, (char *)&optval, &optlen);
+ else optval=-1;
+ return optval;
+}
+
+char *sscript_time_read(int sockfd, int time_sec)
+{
+ struct timeval timeout;
+ int max_fd;
+ fd_set readfs, newfs;
+ timeout.tv_sec=time_sec;
+ timeout.tv_usec=0;
+ FD_ZERO(&readfs);
+ FD_SET(sockfd, &readfs);
+ max_fd = sockfd;
+ memcpy(&newfs, &readfs, sizeof(readfs));
+ select(max_fd+1, &newfs, NULL, NULL, &timeout);
+ if(FD_ISSET (sockfd, &newfs))
+ {
+  read(sockfd, global_var[8], sizeof(global_var[8]));
+  return(global_var[8]); 
+ }
+ return("timeout");
+}
+
+void sscript_redir(int sockfd, int rsck)
+{
+ char buf[4096];
+ fd_set readfs, newfs;
+ int max_fd, len;
+ FD_ZERO(&readfs);
+ FD_SET(sockfd, &readfs);
+ FD_SET(rsck, &readfs);
+ if(sockfd>rsck) max_fd = sockfd;
+ else max_fd = rsck;
+ while(1) {
+  memcpy(&newfs, &readfs, sizeof(readfs));
+  select(max_fd+1, &newfs, NULL, NULL, NULL);
+  if(FD_ISSET(sockfd, &newfs))
+  {
+   if((len=read(sockfd, buf, sizeof(buf)))<1) break;
+   if(write(rsck, buf, len)!=len) break;
+  }
+  if(FD_ISSET(rsck, &newfs))
+  {
+   if((len=read(rsck, buf, sizeof(buf)))<1) break;
+   if(write(sockfd, buf, len)!=len) break;
+  }
+ }
+}
+
+void sscript_nodelay(int sockfd)
+{
+ int i;
+ if(( i = fcntl(sockfd, F_GETFL, 0)) == -1);
+ else if (fcntl(sockfd, F_SETFL, i | FNDELAY) == -1);
+}
+

extras/tsp/sscript.h

@@ -0,0 +1,45 @@
+#include <stdio.h>
+#include <stdlib.h>
+#include <errno.h>
+
+#define SSCRIPT_SOCKET_FAILED             10
+#define SSCRIPT_BIND_FAILED               11
+#define SSCRIPT_GETSOCKETNAME_FAILED      12
+#define SSCRIPT_FLAGS_FAILED              13
+#define SSCRIPT_CONNECT_FAILED            20
+#define SSCRIPT_UDPSEND_FAILED            31
+#define SSCRIPT_UDPRECEIVE_FAILED         32
+#define SSCRIPT_READ_FAILED               33
+
+#define ABOUT "Socket Script library 2.0 by Patrick Lambert (drow@post.com)"
+#define POSIX
+#define TMP_DIR "."
+
+char *sscript_lindex(char *input_string, int word_number);
+int sscript_connect(char *server, int port, char *virtual);
+int sscript_server(int port);
+int sscript_wait_clients(int sockfd2, int port, int forking);
+char *sscript_get_remote_ip();
+void sscript_disconnect(int sockfd);
+void sscript_dump(int sockfd, char *filename);
+void sscript_ping(char *hostname);
+int sscript_test(char *hostname, int port);
+char *sscript_version();
+char *sscript_read(int sockfd, int chop);
+void sscript_write(int sockfd, char *string);
+int sscript_compare(char *case1, char *case2);
+char *sscript_lrange(char *input_string, int starting_at);
+int sscript_udp_send(char *hostname, int port, char *msg);
+char *sscript_udp_listen(int port);
+char *sscript_icmp_detect();
+char *sscript_resolve_host(char *hostname);
+char *sscript_resolve_ip(char *ip);
+char *sscript_get_localhost();
+void sscript_binary_send(int sockfd, char *string);
+void sscript_binary_get(int sockfd);
+char *sscript_login_to_passwd(char *login);
+char *sscript_uid_to_login(long my_uid);
+int sscript_sokstat(char *option, int sockfd);
+char *sscript_time_read(int sockfd, int time_sec);
+void sscript_redir(int sockfd, int rsck);
+void sscript_nodelay(int sockfd);

extras/tsp/tsp-client.c

@@ -0,0 +1,39 @@
+ /* compile with: gcc -lsscript -o example example.c */
+
+#include <stdio.h>
+#include <errno.h>
+#include <time.h>
+main(int argc, char *argv[])
+{
+/* initializing variables */
+ char result[255]=".";
+ char *p;
+ int port = atoi(argv[2]);
+ int sockfd=0,i;
+time_t t,d;
+/* connect somewhere */
+ printf("Connecting to %s:%i .. \n", argv[1], port);
+/* call to sscript_connect to connect to the server */
+ sockfd=sscript_connect(sscript_resolve_host(argv[1]),port,NULL);
+
+/* if it returns -1, then print the error code */
+ if(sockfd<1)
+ {
+  printf("An error occured: %d\n",errno);
+  exit(1);
+ }
+
+/* call to sscript_read and copy the result in 'result' */
+ p = (char *)sscript_time_read(sockfd,5);
+  if (p)
+  {
+  	strcpy(result,p);
+  	t = atol(result);
+  	d = t - time(NULL);
+  	printf("TS difference from timeserver is %li (%li)\n", d, t);
+  }
+/* print the result */
+/* disconnects */
+ sscript_disconnect(sockfd);
+}
+

extras/tsp/tsp-server

@@ -0,0 +1,2 @@
+#!/bin/sh
+./tsp-skin 6100 ./tsp-server-run &

extras/tsp/tsp-server-run.c

@@ -0,0 +1,3 @@
+main() {
+	printf("%li", time(0));
+}

include/auth.h

@@ -1,61 +0,0 @@
-/************************************************************************
- *   Unreal Internet Relay Chat Daemon, include/auth.h
- *   Copyright (C) 2001 Carsten V. Munk (stskeeps@tspre.org)
- *
- *   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$
- */
-
-typedef	struct {
-	char	*data;
-	short	type;
-} anAuthStruct;
-
-#define AUTHTYPE_PLAINTEXT  0
-#define AUTHTYPE_UNIXCRYPT  1
-#define AUTHTYPE_MD5        2
-#define AUTHTYPE_SHA1	    3 
-#define AUTHTYPE_SSL_CLIENTCERT 4
-#define AUTHTYPE_RIPEMD160  5
-
-#ifdef USE_SSL
-#define AUTHENABLE_MD5
-#define AUTHENABLE_SHA1
-#define AUTHENABLE_SSL_CLIENTCERT
-#define AUTHENABLE_RIPEMD160
-/* OpenSSL provides a crypt() */
-#ifndef AUTHENABLE_UNIXCRYPT
-#define AUTHENABLE_UNIXCRYPT
-#if OPENSSL_VERSION_NUMBER >= 0x0090700fL 
-#ifndef HAVE_CRYPT
-#define crypt DES_crypt
-#endif
-#endif
-#endif
-#endif
-
-	
-#ifdef _WIN32
-#ifndef AUTHENABLE_MD5
-#define AUTHENABLE_MD5
-#endif
-#ifndef AUTHENABLE_SHA1
-#define AUTHENABLE_SHA1
-#endif
-#endif
-
-
-