bleh

-Stskeeps
===================================

.CHANGES.NEW

@@ -1,20 +1,19 @@
+Welcome to the UnrealIRCd configuration program. This program
+will help you compile your IRC server by asking you questions
+regarding your system and how you want the ircd to function.
 
- _   _                      _ ___________  _____     _
-| | | |                    | |_   _| ___ \/  __ \   | |
-| | | |_ __  _ __ ___  __ _| | | | | |_/ /| /  \/ __| |
-| | | | '_ \| '__/ _ \/  _ | | | | |    / | |    /  _ |
-| |_| | | | | | |  __/ (_| | |_| |_| |\ \ | \__/\ (_| |
- \___/|_| |_|_|  \___|\__,_|_|\___/\_| \_| \____/\__,_|
+If you need help setting up your server, mail
+supporters@lists.unrealircd.org or ask on IRC:
+/server irc.ircsystems.net, /join #unreal-support
 
-                               Configuration Program
-                                for Unreal3.2.10.7
-                                    
-This program will help you to compile your IRC server, and ask you
-questions regarding the compile-time settings of it during the process. 
-regarding the setup of it, during the process.
+Regardless, please read Unreal.nfo first along with all documentation
+and FAQ's in doc/. If you do not do this, we will NOT help you!
+ 
+If the code is changed in any way, or the version string is modified,
+we will _NOT_ support the product. (Unless of course you got explicit
+permission from one of the UnrealIRCd coders.)
 
-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
+Finally, unofficial UnrealIRCd/32 builds (if it doesn't say "genuine"
+in the display) are _NOT_ supported.
 
+- Luke (luke@unrealircd.com)

.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,164 +1,17 @@
-Unreal3.2.10.7 Release Notes
-=============================
 
-==[ UNREALIRCD 3.2.X IS DEPRECATED ]==
-You are currently viewing the release notes of UnrealIRCd 3.2.10.7.
-UnrealIRCd 3.2.* will no longer be supported after December 31, 2016.
-You should upgrade to UnrealIRCd 4 before that date.
-See https://www.unrealircd.org/docs/UnrealIRCd_3.2.x_deprecated
+Unreal3.1.6-Noon Release Notes
+===================================
 
-==[ GENERAL INFORMATION ]==
-- If you are upgrading on *NIX, then make sure you run 'make clean' and
-  './Config' first, before running 'make'.
-- The official UnrealIRCd 3.2.x documentation is available online at
-  https://www.vulnscan.org/UnrealIRCd/unreal32docs.html
-  FAQ: https://www.vulnscan.org/UnrealIRCd/faq/
-  Read them before asking for help.
-- Report bugs at https://bugs.unrealircd.org/
-- The purpose of the sections below (NEW, CHANGED, MINOR, etc) is to be a
-  SUMMARY of the changes in this release. See the file 'Changes' for a
-  complete list of all changes.
+* Initial release preparation, no bugs fixed yet!
 
-==[ .7 RELEASE ]==
-The following issue was fixed in 3.2.10.7:
-- Fix SASL EXTERNAL security issue
+* If you are upgrading from Unreal3.1.4-Meadows, please read
+  doc/RELEASE-NOTES.3.1.5 as well.
 
-==[ .6 RELEASE ]==
-The following has been addressed in 3.2.10.6:
-- Add notes regarding deprecation of 3.2.x series
-- Build with latest OpenSSL to fix crash issue (Windows)
-- Don't show vcredist dialog if installed (Windows installer)
+* If you are upgrading from an even earlier version (before 3.1.4),
+  please read the doc/RELEASE-NOTES.3.1.4 file as well. There
+  were numerous important/significant changes between 3.1.4 and
+  earlier versions.
 
-==[ .5 RELEASE ]==
-The following issues have been fixed in 3.2.10.5:
-- Crash when SASL is enabled (set::sasl-server)
-- A compile problem with LibreSSL
+* Finally, read Unreal.nfo as usual AND THE DOCS in doc/.
 
-==[ .4 RELEASE ]==
-Two major issues were fixed:
-- Compile problems when using clang instead of gcc (such as on FreeBSD & OS X)
-- For services who allow you to log in by account name but still allow you to
-  use a different nick: when you're logged in you are now considered
-  registered as far as mode +M and +R are concerned.
-  Tech: whenever services set SVID and it's not * and does not start with a
-  number, then we consider this user to be 'logged in'.
-  Whenever a user is set +r (s)he is also considered 'logged in'.
-  This way it's compatible with both older and new services and doesn't
-  (or shouldn't) introduce security issues with older services using
-  servicetimestamp for nick tracking or other means.
-Additionally:
-- curl-ca-bundle.crt has been updated to use latest certificates
-- The Windows libraries (OpenSSL, curl, ..) have been updated.
-
-==[ .3 RELEASE ]==
-The following issues have been fixed in 3.2.10.3:
-- Crash when SASL is enabled and ping-cookie is disabled
-- Compile issue with remote include
-- OS X compile problems
-- ./unreal backtrace not always working well
-Changes:
-- For silenced users we now only check the current nick!user@host
-- Server to server links now use latest TLS (eg: v1.2) instead of SSLv3
-New:
-- Added set::spamfilter::stop-on-first-match (default yes). You can change
-  this to 'no' to have UnrealIRCd continue processing all spamfilters even
-  after the first match. The spamfilter with the 'gravest action' wins
-  (eg: gzline wins from block).
-
-==[ .2 RELEASE ]==
-The following major issues were present in 3.2.10 & 3.2.10.1 and have
-been fixed in this version:
-- A remote crash issue when compiled with SSL (NULL pointer dereference)
-- A second issue that can potentially lead to a crash (read-after-free)
-
-In addition to these 3.2.10.x fixes there were also some other bugs fixed,
-mostly in the area of server linking and flood hardening.
-
-The external libraries of the Windows version have been updated (openssl,
-c-ares, zlib). The bundled c-ares source (for *NIX) has been updated too.
-
-==[ .1 RELEASE ]==
-The following bugs in version 3.2.10 were fixed in this 3.2.10.1 release:
-- Windows only: outgoing connects from Windows caused severe linking issues,
-  including killing of (ghost) users on the Windows server.
-- An issue where user modes were stripped from remote clients, this caused
-  a problem for Anope BotServ bots.
-- A compile problem on OpenBSD.
-- '/REHASH -global' did not rehash all servers.
-- Some documentation updates.
-
-==[ 3.2.10 RELEASE ]==
-Below is a summary of all changes with respect to 3.2.9:
-
-==[ NEW ]==
-- Improved socket engine. This brings some performance improvements and
-  also makes it easier to configure a system to hold more than 1024
-  clients (no more editing of header files on Linux!).
-- ESVID support: services can communicate the account name of the user
-  back to the IRCd. This only works on ESVID-capable services:
-  - Extban ~a:<accountname>: matches users who are logged in to services
-    with that account name.
-  - Show account name in /WHOIS
-- CAP support: this enables clients to enable certain features more easily.
-  Can be disabled through set::options::disable-cap.
-- Now that STARTTLS is advertised in CAP it is likely to be used more often.
-- away-notify: informs clients of AWAY state changes of users on the same
-  channels, for clients that support this.
-- account-notify: similar to away-notify, inform clients of changes in the
-  login status and account name used by other clients on the same channels.
-- SASL support. To use this, and if your services support this, you point
-  set::sasl-server to your services server.
-- Server-side MLOCK support: the IRCd will prevent channel mode changes
-  depending on the MLOCK setting in services. Requires special support
-  from services for this feature.
-- User Mode +I (IRCOp only): hide idle time
-- auth-method 'sslclientcertfp': authenticate users using an SSL client
-  certificate by the SHA256 fingerprint of that certificate.
-  The documentation has a new section (3.19) called 'Authentication Types'
-  which contains an (improved) example of how to use SSL client certificate
-  authentication instead of regular passwords.
-- oper::require-modes: an optional setting, which can be used to require
-  users to have certain user modes (such as 'z') before they can /OPER up.
-- allow/deny channel: you can now optionally specify a class here as an
-  extra filter.
-- doc/example.es.conf: Spanish translation of example configuration file.
-- There have also been some behavior changes, which can be considered NEW,
-  see next section (CHANGED).
-
-==[ CHANGED ]==
-- Anti-spoof protection (ping cookies) can now be enabled/disabled at
-  run-time through set::ping-cookie [yes|no]. The default is 'yes' (enabled).
-- A quit with 'Ping timeout' now shows the number of seconds since the ping.
-- Print out a warning if we can't write to a log file.
-- Refuse to boot if we can't write to ANY log file.
-- Windows: if an SSL certificate exists, then uncheck the 'generate SSL
-  certificate' checkbox by default.
-- *NIX with SSL: We now ask in ./Config if you want to generate an SSL
-  certificate. The certificate is then copied when you run 'make install'.
-
-==[ MAJOR BUGS FIXED ]==
-- Windows SSL crash (this issue was already fixed in 3.2.9-SSL-fix)
-- Other than that, none?
-
-==[ MINOR BUGS FIXED ]==
-- Various compile problems, in particular with remote includes enabled.
-- Windows: the installer sometimes insisted that the Visual C++ 2008
-  redistributable package was not installed, when it actually was there.
-- Windows: MOTD file date/time was always showing up as 1/1/1970.
-- And more... see Changelog
-
-==[ REMOVED / DROPPED ]==
-- Windows 9X is no longer supported
-- The networks/ directory has been removed
-
-==[ KNOWN ISSUES ]==
-- Regexes: Be careful with backreferences (\1, etc), certain regexes can
-  slow the IRCd down considerably and even bring it to a near-halt.
-  In the spamfilter user target it's usually safe though.
-  Slow spamfilter detection can help prevent the slowdown/freeze, but
-  might not work in worst-case scenario's.
-- Regexes: Possessive quantifiers such as, for example, "++" (not to be
-  confused with "+") are not safe to use, they can easily freeze the IRCd.
-
-==[ ADDITIONAL INFO ]==
-- See Changelog for more details
+- Luke (luke@unrealircd.com)

.SICI

@@ -4,12 +4,14 @@
 | some kind of Certification Authority (CA), so your users can check that |
 | they are really connected to the real server, so they feel secure?      |
 |                                                                         |
-| There is an initiative at CACert.org - They offer SSL Certificates      |
-| for use with your IRCd for free, so your users can be sure that they    |
-| can trust you and your server.                                          |
-|                                                                         |
-| To get a free signed certificate please visit http://www.CACert.org     |
-|                                                _________________________|
+| An initiative has 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 OpenIRC CA - They offer you to sign           |
+| SSL certificates for use with your IRCd for free,                       |
+| so your users can be sure that they can trust you and your server.      |     
+| To get a signed certificate from them please visit the website  	  |
+| http://www.openirc-ca.eu.org						  |
 | 	                                       	| 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

.hgeol

@@ -1,16 +0,0 @@
-[repository]
-native = LF
-
-[patterns]
-.RELEASE.NOTES = native
-README = native
-Unreal.nfo = native
-makefile.win32 = native
-Changes = native
-**.c = native
-**.h = native
-**.conf = native
-**.html = native
-**.txt = native
-**.bat = native
-**.iss = native

.hgignore

@@ -1,35 +0,0 @@
-syntax: regexp
-
-# particular targets
-^ircdcron/ircdchk$
-^ircdcron/ircd\.cron$
-^src/ircd$
-^src/include$
-^src/version\.c$
-^unreal$
-^server\.(cert|key|req)\.pem$
-
-# extras archives and builds
-^extras/[^/]*\.(bak|tar)$
-^extras/[^/]*\d/
-^extras/(c-ares|regexp)/
-
-# running unrealircd from the source directory
-^ircd\.(log|pid|tune)$
-^ssl\.rnd$
-
-# General
-\.(o|so|orig|rej)$
-~$
-(^|/)core(\.\d+)?$
-
-# autotools
-^aclocal\.m4$
-^autom4te\.cache/
-^config\.(status|log)$
-
-# not quite autotools
-^config\.settings$
-^include/setup\.h$
-^Makefile$
-^src/modules/Makefile$

Changes

@@ -1,7 +1,881 @@
-If you are reading this, then this means you have checked out the Mercurial
-repository. The change log is now generated from the Mercurial version
-history.
+/*                              
+ * UnrealIRCd Changes File - (C) Carsten Munk 1999-2002 &
+ *                               The UnrealIRCd Team
+ *                              
+ * $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.
+ *                              
+ */                             
+                                
+[ Unreal4.0 ]
+- Fixed a _serious_ bug in SERVER command, reported by Valen, Forrester,
+  M0rpheus, JK, and Hiten.
 
-Simply run the following command to generate this 'Changes' file:
-./createchangelog
-- COMMENT (#4251).
+[ Unreal3.1.3 ]
+-----------------------------------------------------------
+Initial release, based on 3.1.1 code and lots of 3.2-beta
+functions that are actually sane
+-----------------------------------------------------------
+resolv.h line 76
+#if ((__GNU_LIBRARY__ == 6) && (__GLIBC__ >=2) && (__GLIBC_MINOR__ >= 2))
+#define res_init __res_init
+#endif
+Fixes compile error w/ later glibc
+--Luke
+===================================
+
+parse.c line 404
+removed if (lifesux)
+--Luke
+===================================
+
+s_bsd.c
+first instance of HighscoreFD
+removed the define
+removed rhighest_fd as well
+removed all instances of HighscoreFD()
+changed rhighest_fd + 1 to MAXCONNECTION
+(100% cpu fix from 3.1.1)
+--Luke
+===================================
+
+channel.c
+Took m_sjoin from 3.2
+removed lp2
+changed Member *lp to Link *lp;
+Changed other stuff (document later?)
+--Luke
+===================================
+
+s_serv.c
+replaced m_server_estab with one from u32june12
+--Luke
+===================================
+
+Fixed missing : on line 419 s_err.c (numeric 379)
+--Luke
+===================================
+
+stole all m_chg* and m_set* functions from u32june12
+in s_unreal.c
+--Luke
+===================================
+
+stole sdesc from latest beta in s_unreal.c
+--Luke
+===================================
+
+line 1683 in s_serv.c
+added me to /info
+--Luke
+===================================
+
+line 1342 res.c
+added line sts foolishly deleted that broke win32 resolver
+--Luke
+===================================
+
+line 2161 in channel.c
+fixed mode segfault bug
+--Luke
+===================================
+
+line 152, fixed #endif error
+aln.c
+--Luke
+===================================
+
+-------------------------------------------------------------
+Beta2ish
+-------------------------------------------------------------
+line 341 ircd.c
+win32 hates SIGQUIT, #ifndef it out.
+--Zogg
+===================================
+
+line 1298 s_bsd.c
+set_blocking() won't compile under msvc.  
+Not important, #ifndef'd out for win32
+--Zogg
+===================================
+
+line 234 in Makefile.dist
+fixed perms on ssl certs
+--Luke
+===================================
+
+Added Zogg's win32 makefile that actually works.
+--Luke
+===================================
+
+------------------------------------------------------------
+Beta3ish
+------------------------------------------------------------
+Changed line 179 in ssl.c to
+set_blocking(cptr->fd, NULL);
+otherwise random segfaults on ssl connect occur
+--Luke
+===================================
+
+Changed line 223 in ssl.c to
+strcat(buf, (char *) my_itoa(bits));
+otherwise got warning on compile in bsd
+--Luke
+===================================
+
+Put in rest of patch for mode propagation bug
+*whack*
+--Luke
+===================================
+
+--------------------------------------------------------------
+Beta4
+--------------------------------------------------------------
+
+Stole StripColors from 3.2-beta, resolves memory
+leak in 3.1.3
+--Luke
+===================================
+
+Rearranged doc/ slightly (moved some more stuff to
+History
+--Luke
+===================================
+
+s_user.c line 1946 - (char *)StripColors as per
+new StripColors function from 3.2-beta
+--Luke
+===================================
+
+stole add_exbanid and add_banid from devel
+(other stuff was just weird)
+--Luke
+===================================
+
+line 4748 in s_user.c for cases i and o added fix (svsmode)
+line 4651 too (svs2mode)
+for svsmode bug (thanks codemastr)
+--Luke
+===================================
+
+line 829, 1035 in s_kline.c gline bug resolved
+(again codemastr)
+--Luke
+===================================
+
+line 1583 res.c fixed dns l, only opers!
+(again codemastr)
+--Luke
+===================================
+
+Modified ./Config to play nice with BSD
+(and yes, God forbid, SunOS 5.x *shudder*)
+--Luke
+===================================
+
+added -lsocket when compiling fdmaxcounter
+in sunos 5.x, may produce crack induced result
+but at least it compiles now
+--Luke
+===================================
+
+145, list.c added passwd fix
+deled cptr->passwd; above (line 135ish)
+--Luke
+===================================
+
+*** 3.1.3 Released ***
+
+[ Unreal 3.1.4 ]
+--------------------------------------------------
+The fixes and backports continue. Strange how much
+time maintaining Unreal can eat up...
+
+Beta1
+--------------------------------------------------
+
+Removed tech admin.
+This feature is useless bloat. If you want it back
+do NOT complain to any of the Unreal coders, feel
+free to reimplement it yourself. Do note, however,
+that if you modify the code in any way, shape, or
+form you immediately give up your ability to
+receive any type of support from us.
+--Luke
+===================================
+
+Line 703 in ircd.c fixed...breaks
+gcc3 compatibility (thanks to shellz.net's
+NuC for reporting)
+--Luke
+===================================
+
+Fixed issue in s_user.c where +H opers
+could be identified by normal users in
+a trivial manner (thanks to Magnet from
+epiknet)
+--Luke
+===================================
+
+s_user.c fixes
+basically, /whois doesn't display snotice
+if you're +W and do it to yourself
+/who the same
+and "is a secure connection" is no longer
+bold (it was lame)
+--Luke
+===================================
+
+s_serv.c fixes
+fixed map bug that allowed you to trivially
+find a hidden U lined server (hopefully)
+--Luke
+===================================
+
+rmed zip.c (not used at all.)
+and zip.h and anything related to zip
+--Luke
+===================================
+
+E lines now match glines, zlines, shuns
+(if you say yes in config)
+--Luke
+===================================
+
+map bug still exists (earlier fix made it
+worse)...removed.
+--Luke
+===================================
+
+/adchat bug that sends it to coadmins twice
+(coadmins are actually server admins as far
+as the ircd is concerned for most purposes, no
+need to send to both UMODES)
+--Luke
+===================================
+
+rewrote m_kick almost entirely (it sucked)
+--Luke
+===================================
+
+newdns.c removed - another useless file
+--Luke
+===================================
+
+------------------------------------------------
+Beta2 Released
+------------------------------------------------
+
+ripped cloak.c from 3.2, and added Config
+options as needed.
+--Luke
+===================================
+
+Fixed 3 svsnoops bugs, so it appears to be
+actually working now...
+--Luke
+===================================
+
++S users no longer show channels in /whois
+--Luke
+===================================
+
+Added a gzline command. I use it with bopm on
+my network all the time, and am getting
+sick of readding it after each new release.
+Additionally, I think it's a useful command
+for anyone to have.
+--Luke
+===================================
+
+Revamped operoverride stuff so it's consistent
+and somewhat sane. (also made NetAdmin.Chat
+NetAdminChat to keep with other forms)
+--Luke
+===================================
+
+Fixed m_kick more
+--Luke
+===================================
+
+Made "is a bot.." not bold
+--Luke
+===================================
+
+Fixed a bug with \r\n being mistakenly parsed
+wrong. Thanks to John_z
+--Luke
+===================================
+
+Added temp patch to m_kline to stop segfault
+--Luke
+===================================
+
+------------------------------------------------
+Beta3 Released
+------------------------------------------------
+
+Backported check_pings with loop.do_ban_check from 3.2
+--Stskeeps
+===================================
+
+Added nice fix to HCN so that BOPM works natively
+(it would still be wise to mod bopm yourself
+and have it scan all clients by using +F, as I've
+done, but whatever.)
+--Luke
+===================================
+
+Moved cloak key definitions to .network file
+--Luke
+===================================
+
+omfg, a patch that resolved some really interesting
+problems with really long parameter modes has been
+applied. (this in itself is a great reason to
+upgrade)
+--Luke
+===================================
+
+Moved exempt_all option to unrealircd.conf, no longer
+a #define in settings.h & ./Config option.
+--Luke
+===================================
+
+Made stop code error more stupid-people friendly
+--Luke
+===================================
+
+Added code that shows nick changes on entire net
+when umode +j (JUNK). Also, went through channel.c
+and made all snotices look "nicer"
+--Luke
+===================================
+
+Moved cloak keys to unrealircd.conf, since the
+.network files are public domain (in general).
+Go lynch Stskeeps if you don't like it.
+--Luke
+===================================
+
+Actually added sample lines to unrealircd.conf
+for EXEMPT_ALL and CLOAK_KEY_n. Also, changed
+version number on both that and the .network
+file, as both have changed since 3.1.3.
+--Luke
+===================================
+
+Useful /who patch incorporated, thanks to
+larne
+--Luke
+===================================
+
+Rewrote all of /who, screw everyone's patches
+mine are better!
+--Luke
+===================================
+
+More /who madness! I've added an h flag, similar
+to the o flag that you can append on the end
+for opers, so for instance say you /who *bob* h
+it will display real hosts instead of masked ones
+in the replies.
+--Luke
+===================================
+
+Oper invisibility is no longer enabled by default
+but is a provided option in ./Config
+--Luke
+===================================
+
+Changed information flag shown in /version. R now
+appears if invisibility is compiled in (even if
+disabled in unrealircd.conf)
+--Luke
+===================================
+
+rmed Config.c (broken, severely) and networks.ndx
+--Luke
+===================================
+
+Added win32-compile-guide in doc/ for people wanting
+to compile their own version for windows.
+--Luke
+===================================
+
+Once again we global when anyone that's not a local
+oper opers. I like this, if you don't email me and
+maybe I'll add a conf option for it.
+--Luke
+===================================
+
+Deprecated /akill and /rakill. Please stop using
+these commands. They're old and will be removed in
+future releases. For now they simply add/remove a
+permanent gline, which is essentially what an akill
+is anyway (yes, I know they disappear when you rehash)
+--Luke
+===================================
+
+Rewrote m_oper, massive mods to most set* and chg* functions
+--Luke
+===================================
+
+Reintroduced original patch in channel.c with mode overflow
+(saves char * for each function call)
+-- Luke
+===================================
+
+Fixed a seriously stupid bug introduced by myself with SAMODE
+globops. (Thanks to Zerwas)
+--Luke
+===================================
+
+Added additional operoverride capabilities (namely
+ability to view banlists, exemptlists, etc.)
+--Luke
+===================================
+
+Played with I line password bug for a while
+--Luke
+===================================
+
+Fixed (maybe?) an implementation with MAXBANLENGTH
+--Luke
+===================================
+
+Thanks a TON to JK, applied patch he developed to
+resolve desynch problem with mode +,-p/s.
+--Luke
+===================================
+
+Fixed I line segfault bug...lots of fun. Thanks again
+to JK for helping :)
+--Luke
+===================================
+
+---------------------------------------------
+Beta4 Released
+---------------------------------------------
+
+Incorporated STATS_ONLY_OPER patch thanks to
+psycho
+--Luke
+===================================
+
+Added JK /map patch to resolve hidden U lines
+being trivially found.
+--Luke
+===================================
+
+Fixed clients able to connect on server-only port
+bug. (thanks to worf for reporting)
+--Luke
+===================================
+
+Resolved halfops + operoverride issues
+--Luke
+===================================
+
+Fixed problem where normal users could view topics of
++s/+p channels. (removed /topic functionality for
+non channel members altogether. Channel topics can
+still be obtained via /list)
+--Luke
+===================================
+
+Finally fixed *all* mode problems that are known
+at this time. Long parameters no longer create
+desynchs, everything is happy! Fear.
+--Luke
+===================================
+
+Thanks to Zerwas, added numeric 489 for SECUREONLYCHAN
+so +z channels no longer respond with you're banned.
+--Luke
+===================================
+
+Revamped operoverride again to better handle mode walks
+--Luke
+===================================
+
+Fixed a SERIOUS security problem with c/n line passwords
+Thanks a bunch to node357 for reporting!
+--Luke
+===================================
+
+----------------------------------------------
+Beta5 Released
+----------------------------------------------
+
+Fixed bug with mirc where +a/+q were misinterpreted as modes
+without nick parameters.
+--Luke
+===================================
+
+Implemented actual prefixes for +q and +a (~ and &)
+--Luke
+===================================
+
+Modified is_chan_op and is_chanprot functions to better
+respect hierarchy (chanowner is chanprot as well as chanop)
+chanprot is chanop.
+--Luke
+===================================
+
+Fixed m_gline and m_gzline bugs. (Thanks to nighthawk for
+noticing)
+--Luke
+===================================
+
+Fixed sjoin bug with ban propagation
+--Luke
+===================================
+
+Fixed m_who bug with normal users using masks
+--Luke
+===================================
+
+Rearranged structs in struct.h to be more memory efficient
+(saved 4 bytes in User, in preparation for new operoverride
+system.)
+--Luke
+===================================
+
+Decided channel owners can deown themsleves, implemented
+as such
+--Luke
+===================================
+
+Revised operoverride system further, now default prompting
+before permitting opers to walk channel modes.
+--Luke
+===================================
+
+Scratch previous revision, redid override system altogether.
+Now done via /invite. Sts' response to those of you that
+don't like it: "fuck them"
+--Luke
+===================================
+
+Fixed lowercase host errors with cloaking (sts' patch)
+--Luke
+===================================
+
+do_mode_char fixes (mostly from sts)
+--Luke
+===================================
+
+SJ3 fixes from codemastr for possible desynch
+--Luke
+===================================
+
+Fixed prefix problem as per nighthawk
+--Luke
+===================================
+
+Temp removed +q/+a prefixes to give client coders
+chance to implement PREFIX= sanely
+--Luke
+===================================
+
+Added a nice little win32 fix to cloak.c to stop snprintf
+from breaking things all over the place
+--Luke
+===================================
+
+Fixed win32 settings.h for the few who actually recompile
+their own win32 version.
+--Luke
+===================================
+
+Minor issue with +I and new invite system resolved.
+We should remove +I altogether...
+--Luke
+===================================
+
+Rmed a bunch of files in doc/ redid some other documentation.
+--Luke
+===================================
+
+Finally redid /credits thanks to sts :P
+--Luke
+===================================
+
+Fixed OPEROVERRIDE_VERIFY Bug
+--Luke
+===================================
+
+*** Unreal3.1.4 Released ***
+
+[ Unreal 3.1.5 ]
+
+------------------------------------------
+We begin this release with a stupid
+bug fix. Yes, I severely broke userhost.
+I'm sorry.
+------------------------------------------
+
+Beta1
+----------------------------
+
+Fixed userhost displaying * all the time
+--Luke
+===================================
+
+Fixed broken m_invite, thanks to codemastr
+--Luke
+===================================
+
+Fixed halfop kick priv bug thanks to JK
+--Luke
+===================================
+
+Added Oo flags in version response if
+OPEROVERRIDE is enabled, and OPEROVERRIDE_VERIFY
+enabled.
+--Luke
+===================================
+
+Removed LEAST_IDLE, served no useful purpose
+really.
+--Luke
+===================================
+
+Fixed grammatical error thanks to MorPheus
+--Luke
+===================================
+
+Fixed m_invite, really. I tested it this time :)
+--Luke
+===================================
+
+Changed +A/+O bans to act more sanely
+--Luke
+===================================
+
+Fixed cloaking fun for hosts w/out . (from codemastr)
+--Luke
+===================================
+
+Copied fixes to /helpop from 3.2 reported by FrostByghte
+--Luke
+===================================
+
+Applied weird sts patch for dynamic allocation of nick
+field in topics
+--Luke
+===================================
+
+Fixed broken /who
+--Luke
+===================================
+
+Fixed bug with /whois and +I
+--Luke
+===================================
+
+Fixed exempt propagation bug
+--Luke
+===================================
+
+------------------------------------------------------
+Beta2 Released
+------------------------------------------------------
+
+Fixed m_who bug displaying channels
+when it isn't supposed to, thanks to frozen
+--Luke
+===================================
+
+Fixed issue with server IP addresses being
+shown to normal +s lusers (thanks to MrAllthat)
+--Luke
+===================================
+
+Added prefixes for channel owner/protected to
+/who and /whois (& and ~). They probably should never
+have been removed. Still to be implemented
+are actual prefixes in /names.
+--Luke
+===================================
+
+Small m_who bug with opers fixed.
+--Luke
+===================================
+
+Implemented awesome new feature for operoverride, per
+codemastr. You now need the letter "v" in your O line
+in order to be able to override!
+--Luke
+===================================
+
+------------------------------------------------------
+Beta3 Released
+------------------------------------------------------
+
+Fixed problem with topics screwing up services
+--Luke
+===================================
+
+Fixed semantics with operoverride_verify and +s/+p
+channels.
+--Luke
+===================================
+
+Kill me. Really. Still trying to fix services fun...
+--Luke
+===================================
+
+Given up for now on fixing the services "problem."
+(it isn't really a problem, afaik, it's just annoying.)
+Anyone that has ideas about what causes it, or how
+it can be fixed email luke@unrealircd.com.
+The problem is that IRC Services 5 starts sending out
+notices about being "unable to set modes for #channel"
+blah blah. There isn't any indication of anything actually
+being bounced, so we're not sure why it happens.
+--Luke
+===================================
+
+*** Unreal 3.1.5 Released ***
+
+[ Unreal 3.1.5.1 ]
+--------------------------------------------------
+Had I only known what I was getting myself into...
+--------------------------------------------------
+
+Fixed a "bug" too stupid to be listed here. No, I
+didn't introduce it, and apparently it has existed
+since pre-3.0. *shudder*
+--Luke
+===================================
+
+Fixed bug with "empty" channels showing up in list with
+60 something odd thousand users in it. (found by codemastr)
+--Luke
+===================================
+
+Fixed compilation error when NO_OPEROVERRIDE is defined,
+reported by Joe.
+--Luke
+===================================
+
+Ummm, yea, you want to upgrade. There's a, um, bug that
+probably isn't a good thing
+--Luke
+===================================
+
+*** Unreal 3.1.5.1 Released ***
+
+[ Unreal 3.1.6 ]
+--------------------------------------------------
+No comment.
+--------------------------------------------------
+
+Initial release prep, changing version numbers in cvs
+(again).
+===================================
+
+Fixed /botserv bug, reported by SciFi
+--Luke
+===================================
+
+Unbroke +A channels and bans. :-/
+--Luke
+===================================
+
+Removed +I. Don't you dare even think about whining.
+--Luke
+===================================
+
+Added chmode +R, requires umode +r to speak.
+--Luke
+===================================
+
+Deleted extra, unused oflag...wmaster.
+--Luke
+===================================
+
+Added a max of 500:500 to +f
+--Luke
+===================================
+
+Removed USE_LONGMODE.
+--Luke
+===================================
+
+Added modes S, M to common.h.
+--Luke
+===================================
+
+Added end of stats messages in /gline, /gzline, /shun
+--Luke
+===================================
+
+Fixed bug in channel mode +L
+--Luke
+===================================
+
+Fixed -o+b user *!*@blah.com halfop stuff.
+--Luke
+===================================
+
+Fixed bug where HCN would display exit client notices twice.
+--Luke
+===================================
+
+Modified it so people with override flag in O line can
+dechanown, dechanprot people.
+--Luke
+===================================
+
+Small m_topic bug resolved
+--Luke
+===================================
+
+Backported m_message fix from 3.2, fixed by Syzop, reported by Ashkrynt
+-Stskeeps
+===================================
+
+*** Unreal3.1.6 released ***
+
+[ Unreal 3.1.7 ]
+--------------------------------------------------
+...
+--------------------------------------------------
+
+Initial release prep, changing version numbers in cvs
+(again).
+--Luke
+===================================
+
+Fixed double snotice exit bug (probably)
+--Luke
+===================================
+
+Fixed stats being visible to users even after defining
+STATS_ONLYOPER in config.h
+--Luke
+===================================
+
+Applied Syzop's fix for operoverride crash.
+--Luke
+===================================
+
+Ported Syzop's fix for PRIVMSG/NOTICE bug.
+--Luke
+===================================

Donation

@@ -1,18 +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 users 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: http://unrealircd.com/donate.php
+Send donations to:
+------------------
+UnrealIRCd Project
+C/O Carsten Munk
+P.O.Box 52
+7400 Herning
+Denmark
 
-If you don't want to use PayPal, or you want to donate something other than money,
-contact Syzop (syzop@unrealircd.com).
+(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). 
 
-All those who donate at least a certain minimum amount will have their name
-and/or company listed in /CREDITS.
-Additionally, all donators will be listed on the website (regardless of the amount).
-Please check the website for details.
+-- Stskeeps
 
-Thank you for your support,
-The UnrealIRCd Team
+[ $Id$ ]

INSTALL

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

INSTALL.REMOTEINC

@@ -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@ @TRE_LIBS@ @CARES_LIBS@
-CRYPTOLIB=@CRYPTOLIB@
+XCFLAGS=
+IRCDLIBS=
+CRYPTOLIB=
 OPENSSLINCLUDES=
-
-XCFLAGS=@TRE_CFLAGS@ @CARES_CFLAGS@ @CFLAGS@
 #
 # use the following on MIPS:
 #CFLAGS= -systype bsd43 -DSYSTYPE_BSD43 -I$(INCLUDEDIR)
@@ -92,69 +88,84 @@ 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. You may override
-# the system FD_SETSIZE by setting the FD_SETSIZE Makefile variable to
-# -DFD_SETSIZE=<some number>.
-FD_SETSIZE=@FD_SETSIZE@
+# 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=
 
 # 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}'
+		'MANDIR=${MANDIR}' 'RM=${RM}' 'CP=${CP}' 'TOUCH=${TOUCH}' \
+		'RES=${RES}' 'SHELL=${SHELL}' 'STRTOUL=${STRTOUL}' \
+		'CRYPTOLIB=${CRYPTOLIB}' 'REGEX=${REGEX}' \
+		'CRYPTOINCLUDES=${CRYPTOINCLUDES}'
 
-custommodule:
-	@if test -z "${MODULEFILE}"; then echo "Please set MODULEFILE when calling \`\`make custommodule''. For example, \`\`make custommodule MODULEFILE=callerid''." >&2; exit 1; fi
-	+cd src; ${MAKE} ${MAKEARGS} MODULEFILE=${MODULEFILE} 'EXLIBS=${EXLIBS}' custommodule
-
-server: Makefile
-build: Makefile
+server:
+build:
 	-@if [ ! -f include/setup.h ] ; then \
 		echo "Hmm...doesn't look like you've run Config..."; \
 		echo "Doing so now."; \
 		sh Config; \
 	fi
-	@+for i in $(SUBDIRS); do \
+	@for i in $(SUBDIRS); do \
 		echo "Building $$i";\
 		( 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|'
@@ -167,20 +178,23 @@ build: Makefile
 
 clean:
 	$(RM) -f *~ \#* core *.orig include/*.orig
-	@+for i in $(SUBDIRS); do \
+	@for i in $(SUBDIRS); do \
 		echo "Cleaning $$i";\
 		( cd $$i; ${MAKE} ${MAKEARGS} clean; ) \
 	done
 	-@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/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 *
@@ -199,62 +213,26 @@ stamp: makedist
 	echo "" >> include/stamp.h
 
 depend:
-	@+for i in $(SUBDIRS); do \
+	@for i in $(SUBDIRS); do \
 		echo "Making dependencies in $$i";\
 		( cd $$i; ${MAKE} ${MAKEARGS} depend; ) \
 	done
 
 install: all
-	$(INSTALL) -m 0700 -d $(IRCDDIR)
-	$(INSTALL) -m 0700 src/ircd $(BINDIR) 2>/dev/null || { $(INSTALL) -m 0700 -d "$$(dirname '$(BINDIR)')"; $(INSTALL) -m 0700 src/ircd $(BINDIR); }
-	$(INSTALL) -m 0700 -d $(IRCDDIR)/doc
-	$(INSTALL) -m 0600 doc/Authors doc/example.conf 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 spamfilter.conf dccallow.conf $(IRCDDIR)
-	$(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
-	$(INSTALL) -m 0700 -d $(IRCDDIR)/ircdcron
-	$(INSTALL) -m 0600 ircdcron/ircd.cron $(IRCDDIR)/ircdcron
-	$(INSTALL) -m 0700 ircdcron/ircdchk $(IRCDDIR)/ircdcron
-	-@if [ ! -f "$(IRCDDIR)/curl-ca-bundle.crt" ] ; then \
-		$(INSTALL) -m 0700 curl-ca-bundle.crt $(IRCDDIR) ; \
-	fi
-	-@if [ server.cert.pem -nt "$(IRCDDIR)/server.cert.pem" ] ; then \
-		$(INSTALL) -m 0600 server.req.pem $(IRCDDIR) ; \
-		$(INSTALL) -m 0600 server.key.pem $(IRCDDIR) ; \
-		$(INSTALL) -m 0600 server.cert.pem $(IRCDDIR) ; \
-	fi
+	@echo "Now install by hand; make install is broken."
 
 pem:	src/ssl.cnf
 	@echo "Generating certificate request .. "
-	$(OPENSSLPATH) req -new \
-              -config src/ssl.cnf -sha256 -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 3650 -sha256 -in server.req.pem \
+	$(OPENSSLPATH) req -x509 -days 365 -in server.req.pem \
                -key server.key.pem -out server.cert.pem
 	@echo "Generating fingerprint .."
-	$(OPENSSLPATH) x509 -subject -dates -sha256 -fingerprint -noout \
+	$(OPENSSLPATH) x509 -subject -dates -fingerprint -noout \
 		-in server.cert.pem
+
 	@echo "Setting o-rwx & g-rwx for files... "
 	chmod o-rwx server.req.pem server.key.pem server.cert.pem
 	chmod g-rwx server.req.pem server.key.pem server.cert.pem
-	@echo "Done!. If you want to encrypt the private key, run"
-	@echo "make encpem"
-
-encpem: server.key.pem
-	@echo "Encrypting server key .."
-	$(OPENSSLPATH) rsa -in server.key.pem -out server.key.c.pem -des3
-	-@if [ -f server.key.c.pem ] ; then \
-		echo "Replacing unencrypted with encrypted .." ; \
-		cp server.key.c.pem server.key.pem ; \
-		rm -f server.key.c.pem ; \
-	fi
-
-Makefile: config.status Makefile.in
-	./config.status
+	@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.

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".

Unreal.nfo

@@ -1,77 +1,59 @@
 ===============================================
-=            UnrealIRCd v3.2.10.7             =
+=            UnrealIRCd v3.1.6                =
 ===============================================
- This release was brought to you by:
+ Was brought to you by:
+  * Stskeeps  <stskeeps@unrealircd.com>
+  * codemastr <codemastr@unrealircd.com>
+  * Luke      <luke@unrealircd.com>
 
-  Head coder:
-  ============
-  * Syzop
-
-  Coders:
-  ========
-  * binki
-
-  Contributors:
-  =============
-  * Heero
-  * nenolod
-  * Adam
-  * warg
-  * Stealth
-  * WolfSage
-  * katsklaw
-  * darkex
-  * fspijkerman
-  * fbi
-  * Apocalypse
-
-  Previous coders:
-  ================
-  * Stskeeps
-  * codemastr
-  * Many more..
-
-  Internet Presence:
-  * http://www.unrealircd.com/
+ Precenses on the Internet:
+  * http://www.unrealircd.com
  
- UnrealIRCd Bugtracker (Where to report bugs, make suggestions, and submit patches)
- ===================================================================================
- http://bugs.unrealircd.org/
+ CVS:
+To get anonymous access: (read only)
+"cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot login"
 
- To get support
- ================
- Before asking others for help you MUST:
- * read the docs (doc/unreal32docs.html or online: http://unrealircd.com/unreal32docs.html)
- * check the FAQ (http://vulnscan.org/UnrealIrcd/faq/)
+press enter when asked for password
 
- Means of support:
- * IRC: /server irc.unrealircd.com 6667 - /join #unreal-support
-   [Note: Follow the bot's instructions in order to get voice.
-          Please be patient after asking questions, we may be busy
-          or we're away. Don't repeat questions, we will have heard
-	  you first time.
-	  READ THE TOPIC before you ask anything. We give support
-	  on a free basis. We are volunteering to help you, but we
-	  are humans like you. We sometimes just need some peace.]
- * Forum: http://forums.unrealircd.com/
+and to get latest stable:
+"cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r stable -d Unreal-stable unreal"
 
- Development version
- ====================
- To access the latest development version of UnrealIRCd you need to use mercurial (hg).
- Note that because you are accessing a development version it may not compile, the
- server may crash, or other problems can occur since the code is likely to be only
- lightly tested (or not at all). On the other hand, using the development version may
- help you to get rid of that single nasty bug that is haunting you, plus if you test
- it and give us feedback (report bugs) then you actually help us with developing Unreal.
+latest beta:
+"cvs -d :pserver:anonymous@cvs.ircsystems.net:/home/cmunk/ircsystems/cvsroot checkout -r beta -d Unreal-beta unreal"
 
- The command to grab the development version is:
- hg clone http://hg.unrealircd.org/unreal
+  * To get support
+  ================
+    * IRC: /server irc.ircsystems.net 6667 - /join #unreal-support
+      [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
 
- If you get something like 'hg: command not found' then you need to install mercurial.
- Most *NIX systems have such a 'mercurial' package, but if you don't, or you are on
- Windows or Mac OS X, then see http://mercurial.selenic.com/
+    * If you experince any wierdnesses (that doesnt crash the server)
+      please mail unreal-dev@lists.sourceforge.net with any clues on what
+      you did, what you experinced etc.
 
- Want to discuss, chat, etc?
- =============================
- * IRC: /server irc.unrealircd.com 6667 - /join #chat
-   (NOT for support! If you want support then use #unreal-support instead!)
+  * Got a suggestion?
+  ===================
+    * Mail it to unreal-dev@lists.sourceforge.net :) or catch one from
+      the Unreal team online on IRC:)
+
+ 

aliases/aliases.conf

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

aliases/anope.conf

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

aliases/atheme.conf

@@ -1,26 +0,0 @@
-/* Atheme Aliases */
-
-alias nickserv { type services; };
-alias ns { target nickserv; type services; };
-alias chanserv { type services; };
-alias cs { target chanserv; type services; };
-alias memoserv { type services; spamfilter yes; };
-alias ms { target memoserv; type services; spamfilter yes; };
-alias operserv { type services; };
-alias os { target operserv; type services; };
-alias helpserv { type services; };
-alias botserv { type services; };
-alias bs { target botserv; type services; };
-alias hostserv { type services; };
-alias hs { target hostserv; type services; };
-alias saslserv { type services; };
-alias sss { target saslserv; type services; };
-alias gameserv { type services; };
-alias gms { target gameserv; type services; };
-alias groupserv { type services; };
-alias grs { target groupserv; type services; };
-alias alis { type services; };
-alias ls { target alis; type services; };
-
-include "aliases/aliases.conf";
-

aliases/auspice.conf

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

aliases/cygnus.conf

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

aliases/epona.conf

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

aliases/generic.conf

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

aliases/genericstats.conf

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

aliases/ircservices.conf

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

aliases/operstats.conf

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

autoconf/Makefile

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

autoconf/m4/unreal.m4

@@ -1,253 +0,0 @@
-#serial 1
-
-dnl Macro: unreal_CHECK_TYPE_SIZES
-dnl originally called 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], [], [Define if rlim_t is long long])
-fi
-])
-
-AC_DEFUN([CHECK_LIBCURL],
-[
-	AC_ARG_ENABLE(libcurl,
-	[AC_HELP_STRING([--enable-libcurl=DIR],[enable libcurl (remote include) support])],
-	[enable_curl=$enableval],
-	[enable_curl=no])
-
-	AS_IF([test "x$enable_curl" != "xno"],
-	[
-		dnl sane, default directory for Operating System-managed libcURL
-		dnl (when --enable-libcurl is passed without any arguments). On
-		dnl systems with stuff in /usr/local, /usr/local/bin should already
-		dnl be in PATH. On sane systems, this will invoke the curl-config
-		dnl installed by the package manager.
-		CURLCONFIG="curl-config"
-		AS_IF([test "x$enable_curl" != "xyes"],
-			[CURLCONFIG="$enable_curl/bin/curl-config"])
-
-		AC_MSG_CHECKING([$CURLCONFIG])
-		AS_IF([$CURLCONFIG --version 2>/dev/null >/dev/null],
-			[AC_MSG_RESULT([yes])],
-			[AC_MSG_RESULT([no])
-				AC_MSG_FAILURE([Could not find curl-config, try editing --enable-libcurl])])
-
-		CURLCFLAG="`$CURLCONFIG --cflags`"
-		CURLLIBS="`$CURLCONFIG --libs`"
-
-		dnl This test must be this way because of #3981
-		AS_IF([$CURLCONFIG --features | grep -q -e AsynchDNS],
-			[CURLUSESCARES="1"],
-			[CURLUSESCARES="0"])
-		AS_IF([test "$CURLUSESCARES" = "0"],
-			[AC_MSG_WARN([cURL seems compiled without c-ares support. Your IRCd will possibly stall when REHASHing!])])
-
-		dnl sanity warnings
-		AS_IF([test -z "${CURLLIBS}"],
-			[AC_MSG_WARN([CURLLIBS is empty, that probably means that I could not find $enable_curl/bin/curl-config])])
-
-		dnl Ok this is ugly, basically we need to strip the version of c-ares that curl uses
-		dnl because we want to use our own version (which is hopefully fully binary
-		dnl compatible with the curl one as well).
-		dnl Therefore we need to strip the cares libs in a weird way...
-		dnl If anyone can come up with something better and still portable (no awk!?)
-		dnl then let us know. -- Syzop
-		dnl
-		dnl It is dangerous to mix and match cURL with potentially ABI-incompatible versions of
-		dnl c-ares, just use --with-system-cares.
-		dnl Thus, make sure to use --with-system-cares when using system-cURL. If the user
-		dnl wants bundled c-ares + system libcURL, then we should filter out c-ares
-		dnl flags. _Only_ in that case should we mess with the flags. -- ohnobinki
-
-		AS_IF([test "x$with_system_cares" = "xno" && test "x$HOME/curl" != "x$enable_curl" && test "x/usr/share/unreal-curl" != "x$enable_curl" && test "$CURLUSESCARES" != "0" ],
-		[
-			AC_MSG_ERROR([[
-
-  You have decided to build unrealIRCd with libcURL (remote includes) support.
-  However, you have disabled system-installed c-ares support (--with-system-cares).
-  Because UnrealIRCd will use a bundled copy of c-ares which may be incompatible
-  with the system-installed libcURL, this is a bad idea which may result in error
-  messages looking like:
-
-  	\`\`[error] unrealircd.conf:9: include: error downloading '(http://example.net/ex.conf)': Could not resolve host: example.net (Successful completion)''
-
-  Or UnrealIRCd might even crash.
-
-  Please build UnrealIRCd with --with-system-cares when enabling --enable-libcurl
-]])
-		])
-
-		AS_IF([test "x`echo $CURLLIBS |grep ares`" != x && test "x$with_system_cares" = "xno"],
-		[
-			dnl Attempt one: Linux sed
-			[XCURLLIBS="`echo "$CURLLIBS"|sed -r 's/[^ ]*ares[^ ]*//g' 2>/dev/null`"]
-			AS_IF([test "x$XCURLLIBS" = "x"],
-			[
-				dnl Attempt two: FreeBSD (and others?) sed
-				[XCURLLIBS="`echo "$CURLLIBS"|sed -E 's/[^ ]*ares[^ ]*//g' 2>/dev/null`"]
-				AS_IF([test x"$XCURLLIBS" = x],
-				[
-					AC_MSG_ERROR([sed appears to be broken. It is needed for a remote includes compile hack.])
-				])
-			])
-			CURLLIBS="$XCURLLIBS"
-
-			IRCDLIBS_CURL_CARES="$CARES_LIBS"
-			CFLAGS_CURL_CARES="$CARES_CFLAGS"
-		])
-		
-		dnl Make sure that linking against cURL works rather than letting the user
-		dnl find out after compiling most of his program. ~ohnobinki
-		IRCDLIBS="$IRCDLIBS $CURLLIBS"
-		CFLAGS="$CFLAGS $CURLCFLAG"
-		AC_DEFINE([USE_LIBCURL], [], [Define if you have libcurl installed to get remote includes and MOTD support])
-
-		AC_MSG_CHECKING([curl_easy_init() in $CURLLIBS])
-		LIBS_SAVEDA="$LIBS"
-		CFLAGS_SAVEDA="$CFLAGS"
-
-		LIBS="$IRCDLIBS $IRCDLIBS_CURL_CARES"
-		CFLAGS="$CFLAGS $CFLAGS_CURL_CARES"
-		AC_LINK_IFELSE(
-		    [
-			AC_LANG_PROGRAM(
-			    [[#include <curl/curl.h>]],
-			    [[CURL *curl = curl_easy_init();]])
-			],
-		    [AC_MSG_RESULT([yes])],
-		    [AC_MSG_RESULT([no])
-			AC_MSG_FAILURE([You asked for libcURL (remote includes) support, but it can't be found at $enable_curl])
-		])
-		LIBS="$LIBS_SAVEDA"
-		CFLAGS="$CFLAGS_SAVEDA"
-
-		URL="url.o"
-		AC_SUBST(URL)
-	]) dnl AS_IF(enable_curl) 
-])
-
-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/sfw /usr/local /usr])],
-	[],
-	[enable_ssl=no])
-AS_IF([test $enable_ssl != "no"],
-	[ 
-	AC_MSG_CHECKING([for openssl])
-	for dir in $enable_ssl /usr/local/ssl /usr/lib/ssl /usr/ssl /usr/pkg /usr/sfw /usr/local /usr; do
-		ssldir="$dir"
-		if test -f "$dir/include/openssl/ssl.h"; then
-			AC_MSG_RESULT([found in $ssldir/include/openssl])
-			found_ssl="yes";
-			if test ! "$ssldir" = "/usr" ; then
-				CFLAGS="$CFLAGS -I$ssldir/include";
-			fi
-			break
-		fi
-		if test -f "$dir/include/ssl.h"; then
-			AC_MSG_RESULT([found in $ssldir/include])
-			found_ssl="yes";
-			if test ! "$ssldir" = "/usr" ; then
-				CFLAGS="$CFLAGS -I$ssldir/include";
-			fi
-			break
-		fi
-	done
-	if test x_$found_ssl != x_yes; then
-		AC_MSG_RESULT(not found)
-		echo ""
-		echo "Apparently you do not have both the openssl binary and openssl development libraries installed."
-		echo "You have two options:"
-		echo "a) Install the needed binaries and libraries"
-		echo "   and run ./Config"
-		echo "OR"
-		echo "b) If you don't need SSL..."
-		echo "   Run ./Config and say 'no' when asked about SSL"
-		echo "   (or pass --disable-ssl to ./configure)"
-		echo ""
-		exit 1
-	else
-		CRYPTOLIB="-lssl -lcrypto";
-		if test ! "$ssldir" = "/usr" ; then
-			LDFLAGS="$LDFLAGS -L$ssldir/lib";
-		fi
-		AC_DEFINE([USE_SSL], [], [Define if you want to allow SSL connections])
-	fi
-	])
-])
-
-AC_DEFUN([CHECK_ZLIB],
-[
-AC_ARG_ENABLE([ziplinks],
-	[AC_HELP_STRING([--enable-ziplinks=DIR],[enable ziplinks. will check /usr/local /usr /usr/pkg. Note that SSL does its own compression, so you won't need this for SSL links.])],
-	[],
-	[enable_ziplinks=no])
-AS_IF([test $enable_ziplinks != "no"],
-	[
-	AC_MSG_CHECKING([for zlib])
-	for dir in $enable_ziplinks /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 -I$zlibdir/include";
-			fi
-			AC_DEFINE([ZIP_LINKS], [], [Define if you have zlib and want zip links support.])
-		break
-		fi
-	done
-	if test x_$found_zlib != x_yes; then
-		AC_MSG_RESULT([not found])
-		echo ""
-		echo "Apparently you do not have the zlib development library installed."
-		echo "You have two options:"
-		echo "a) Install the zlib development library"
-		echo "   and run ./Config"
-		echo "OR"
-		echo "b) If you don't need compressed links..."
-		echo "   Run ./Config and say 'no' when asked about ziplinks support"
-		echo ""
-		exit 1
-	else
-		IRCDLIBS="$IRCDLIBS -lz"
-		if test "$zlibdir" != "/usr" ; then
-			LDFLAGS="$LDFLAGS -L$zlibdir/lib"
-		fi
-		HAVE_ZLIB=yes
-	fi
-	AC_SUBST([HAVE_ZLIB])
-	])
-])

autogen.sh

@@ -1,9 +0,0 @@
-#!/bin/bash
-
-cd "$(dirname "${0}")"
-
-ACLOCAL_AMFLAGS=(-I autoconf/m4)
-
-aclocal "${ACLOCAL_AMFLAGS[@]}"
-autoconf
-autoheader

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"; };

configure.ac

@@ -1,690 +0,0 @@
-dnl Process this file with autoconf to produce a configure script.
-
-dnl When updating the version, remember to update the following files
-dnl appropriately:
-dnl
-dnl include/win32/setup.h
-dnl src/win32/unrealinst.iss
-dnl docs/unreal32docs*.html
-dnl Unreal.nfo
-dnl .CHANGES.NEW
-dnl src/version.c.SH
-
-AC_INIT([unrealircd], [3.2.10.7], [http://bugs.unrealircd.org/], [], [http://unrealircd.org/])
-AC_CONFIG_SRCDIR([src/ircd.c])
-AC_CONFIG_HEADER([include/setup.h])
-AC_CONFIG_AUX_DIR([autoconf])
-AC_CONFIG_MACRO_DIR([autoconf/m4])
-
-if test "x$enable_dynamic_linking" = "x"; then
-	echo "Please use ./Config instead of ./configure"
-	exit 1
-fi
-
-dnl Calculate the versions. Perhaps the use of expr is a little too extravagant
-# Generation version number (e.g.: 3 for Unreal3*)
-UNREAL_VERSION_GENERATION=["`expr $PACKAGE_VERSION : '\([^.]*\)\.[^.]*\.[^.-_]*'`"]
-AC_DEFINE_UNQUOTED([UNREAL_VERSION_GENERATION], [$UNREAL_VERSION_GENERATION], [Generation version number (e.g.: 3 for Unreal3*)])
-
-# Major version number (e.g.: 2 for Unreal3.2*)
-UNREAL_VERSION_MAJOR=["`expr $PACKAGE_VERSION : '[0-9]*\.\([0-9]*\)\.[0-9]*'`"]
-AC_DEFINE_UNQUOTED([UNREAL_VERSION_MAJOR], [$UNREAL_VERSION_MAJOR], [Major version number (e.g.: 2 for Unreal3.2*)])
-
-# Minor version number (e.g.: 1 for Unreal3.2.1)
-UNREAL_VERSION_MINOR=["`expr $PACKAGE_VERSION : '[0-9]*\.[0-9]*\.\([0-9]*\)'`"]
-AC_DEFINE_UNQUOTED([UNREAL_VERSION_MINOR], [$UNREAL_VERSION_MINOR], [Minor version number (e.g.: 1 for Unreal3.2.1)])
-
-# The version suffix such as a beta marker or release candidate
-# marker. (e.g.: -rc2 for unrealircd-3.2.9-rc2). This macro is a
-# string instead of an integer because it contains arbitrary data.
-UNREAL_VERSION_SUFFIX=["`expr $PACKAGE_VERSION : '[0-9]*\.[0-9]*\.[0-9]*\(.*\)'`"]
-AC_DEFINE_UNQUOTED([UNREAL_VERSION_SUFFIX], ["$UNREAL_VERSION_SUFFIX"], [Version suffix such as a beta marker or release candidate marker. (e.g.: -rc2 for unrealircd-3.2.9-rc2)])
-
-AC_PROG_CC
-if test "$ac_cv_prog_gcc" = "yes"; then
-CFLAGS="$CFLAGS -funsigned-char"
-AC_CACHE_CHECK(if gcc has a working -pipe, ac_cv_pipe, [
-	save_cflags="$CFLAGS"
-	CFLAGS="$CFLAGS -pipe"
-	AC_TRY_COMPILE(,, ac_cv_pipe="yes", ac_cv_pipe="no")
-	CFLAGS="$save_cflags"
-])
-if test "$ac_cv_pipe" = "yes"; then
-CFLAGS="-pipe $CFLAGS"
-fi
-fi
-
-dnl (the gcc flag detection trick is taken from xemacs/Vin Shelton)
-
-dnl UnrealIRCd might not be strict-aliasing safe at this time
-case "`$CC -v --help 2>&1`" in
-	*-fstrict-aliasing* ) CFLAGS="$CFLAGS -fno-strict-aliasing" ;;
-esac
-
-dnl Pointer signedness warnings are really a pain and 99.9% of the time
-dnl they are of absolutely no use whatsoever. IMO the person who decided
-dnl to enable this without -Wall should be shot on sight.
-case "`$CC -v --help 2>&1`" in
-	*-Wpointer-sign* ) CFLAGS="$CFLAGS -Wno-pointer-sign" ;;
-esac
-
-AC_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], [], [Define if you have crypt])
-		IRCDLIBS="$IRCDLIBS-ldescrypt "
-		MKPASSWDLIBS="-ldescrypt"],
-	[AC_CHECK_LIB(crypt, crypt,
-		[AC_DEFINE([HAVE_CRYPT], [], [Define if you 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_CHECK_LIB(crypto, RAND_egd,
-		AC_DEFINE(HAVE_RAND_EGD, 1, [Define if the libcrypto has RAND_egd]))
-
-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 -Wl,-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="-std=gnu89 -bundle -flat_namespace -undefined suppress"
-		;;
-		HP-UX*[)]
-		ac_cv_pic="-fPIC"
-		;;
-	esac
-else
-case `uname -s` in
-	SunOS*[)]
-	ac_cv_pic="-KPIC -DPIC -G"
-	;;
-esac
-fi
-])
-AC_CACHE_CHECK(if your system prepends an underscore on symbols,ac_cv_underscore,[
-cat >uscore.c << __EOF__
-int main() {
-	return 0;
-}
-__EOF__
-$CC -o uscore $CFLAGS uscore.c 1>&5
-if test -z "`strings -a uscore |grep '^_main$'`"; then
-ac_cv_underscore=no
-else
-ac_cv_underscore=yes
-fi
-rm -f uscore uscore.c
-])
-dnl libtool has built-in tests that determine proper underscorage
-if test "$ac_cv_underscore" = "yes"; then
-	AC_DEFINE([UNDERSCORE], [], [Define if your system prepends an underscore to symbols])
-fi
-
-MODULEFLAGS=$ac_cv_pic
-dnl DYNAMIC_LINKING is not meant to be defined in include/setup.h, it's 
-dnl defined in the Makefiles using -D. Having it defined globally will
-dnl only cause braindamage and symbol collisions :-D.
-dnl AC_DEFINE([DYNAMIC_LINKING], [], [Link dynamically as opposed to statically. (Dynamic linking is the only supported method of linking atm)])
-])
-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_ERROR([Your system does not support IPv6 so it will not be enabled])
-	else
-		AC_DEFINE([INET6], [], [Define if you want IPv6 enabled])
-		dnl in6addr_any detection code taken from ratbox
-		AC_MSG_CHECKING([for struct in6addr_any])
-		AC_COMPILE_IFELSE(
-			[AC_LANG_PROGRAM(
-				[[#define IN_AUTOCONF
-				#include <sys/types.h>
-				#include <sys/socket.h>
-				#include <netinet/in.h>]],
-				[[struct in6_addr a = in6addr_any;]]
-			)],
-			[AC_MSG_RESULT(yes)],
-				[
-				AC_MSG_RESULT([no])
-				AC_DEFINE([NO_IN6ADDR_ANY], [1], [Define to 1 if your system has no in6addr_any.])
-				]
-			)
-	fi
-	LIBS="$save_libs"
-])
-
-AC_CHECK_HEADER(sys/param.h,
-	AC_DEFINE([PARAMH], [], [Define if you have the <sys/param.h> header file.]))
-AC_CHECK_HEADER(stdlib.h,
-	AC_DEFINE([STDLIBH], [], [Define if you have the <stdlib.h> header file.]))
-AC_CHECK_HEADER(stddef.h,
-	AC_DEFINE([STDDEFH], [], [Define if you have the <stddef.h> header file.]))
-AC_CHECK_HEADER(sys/syslog.h,
-	AC_DEFINE([SYSSYSLOGH], [], [Define if you have the <sys/syslog.h> header file.]))
-AC_CHECK_HEADER(unistd.h,
-	AC_DEFINE([UNISTDH], [], [Define if you have the <unistd.h> header file.]))
-AC_CHECK_HEADER(string.h,
-	AC_DEFINE([STRINGH], [], [Define if you have the <string.h> header file.]))
-AC_CHECK_HEADER(strings.h,
-	AC_DEFINE([STRINGSH], [], [Define if you have the <strings.h> header file.]))
-AC_CHECK_HEADER(malloc.h,
-	AC_DEFINE([MALLOCH], [<malloc.h>], [Define to <malloc.h> you need malloc.h.]))
-AC_CHECK_HEADER(sys/rusage.h,
-	AC_DEFINE([RUSAGEH], [], [Define if you have the <sys/rusage.h> header file.]))
-AC_CHECK_HEADER(glob.h,
-	AC_DEFINE([GLOBH], [], [Define if you have the <glob.h> header file.]))
-AC_CHECK_HEADERS([stdint.h inttypes.h])
-dnl Checks for typedefs, structures, and compiler characteristics.
-AC_C_CONST
-AC_C_INLINE
-
-AC_TYPE_MODE_T
-AC_TYPE_SIZE_T
-AC_TYPE_INTPTR_T
-
-AC_HEADER_TIME
-AC_STRUCT_TM
-AC_TYPE_UID_T
-unreal_CHECK_TYPE_SIZES
-
-dnl in the future, it would be nice to avoid AC_TRY_RUN to allow
-dnl better support for crosscompiling.
-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], [], [Define if you have O_NONBLOCK])
-elif test "$ac_cv_nonblocking" = "O_NDELAY"; then
-	AC_DEFINE([NBLOCK_BSD], [], [Define if you have O_NDELAY])
-elif test "$ac_cv_nonblocking" = "FIONBIO"; then
-	AC_DEFINE([NBLOCK_SYSV], [], [Define if you have FIONBIO])
-fi
-LIBS="$save_libs"
-dnl Checks for library functions.
-AC_PROG_GCC_TRADITIONAL
-AC_FUNC_SETPGRP
-AC_FUNC_SETVBUF_REVERSED
-AC_FUNC_ALLOCA
-AC_CHECK_FUNCS(snprintf,
-	AC_DEFINE([HAVE_SNPRINTF], [], [Define if you have snprintf]))
-AC_CHECK_FUNCS(vsnprintf,
-	AC_DEFINE([HAVE_VSNPRINTF], [], [Define if you have vsnprintf]))
-AC_CHECK_FUNCS(strlcpy,
-	AC_DEFINE([HAVE_STRLCPY], [], [Define if you have strlcpy. Otherwise, an internal implementation will be used!]))
-AC_CHECK_FUNCS(strlcat,
-	AC_DEFINE([HAVE_STRLCAT], [], [Define if you have strlcat]))
-AC_CHECK_FUNCS(strlncat,
-	AC_DEFINE([HAVE_STRLNCAT], [], [Define if you have strlncat]))
-AC_CHECK_FUNCS(inet_pton,
-	AC_DEFINE([HAVE_INET_PTON], [], [Define if you have inet_pton]))
-AC_CHECK_FUNCS(inet_ntop,
-	AC_DEFINE([HAVE_INET_NTOP], [], [Define if you have inet_ntop]))
-dnl Check if it supports C99 style variable length arrays
-AC_CACHE_CHECK([if C99 variable length arrays are supported], [ac_cv_varlen_arrays], [
-AC_TRY_COMPILE(,[
-int main() {
-int i = 5;
-int a[i];
-a[0] = 1;
-return 0;
-}], ac_cv_varlen_arrays=yes, ac_cv_varlen_arrays=no)
-])
-if test "$ac_cv_varlen_arrays" = "yes" ; then
-	AC_DEFINE([HAVE_C99_VARLEN_ARRAY], [], [Define if you have a compiler with C99 variable length array support])
-fi
-
-dnl This check doesn't need to be in ./configure, we can
-dnl write the sourcecode to actually handle the return value
-dnl of setrlimit if necessary... -- ohnobinki
-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], [], [Define if you can set the core size to unlimited])
-fi
-AC_FUNC_VPRINTF
-AC_CHECK_FUNCS([gettimeofday],
-	[AC_DEFINE([GETTIMEOFDAY], [], [Define if you have gettimeofday])],
-	[AC_CHECK_FUNCS([lrand48],
-		[AC_DEFINE([LRADN48], [], [Define if you have lrand48])])])
-AC_CHECK_FUNCS([getrusage],
-	[AC_DEFINE([GETRUSAGE_2], [], [Define if you have getrusage])],
-	[AC_CHECK_FUNCS([times],
-		[AC_DEFINE([TIMES_2], [], [Define if you have times])])])
-AC_CHECK_FUNCS([setproctitle],
-	[AC_DEFINE([HAVE_SETPROCTITLE], [], [Define if you have setproctitle])],
-	[AC_CHECK_LIB([util],
-		[setproctitle],
-		[AC_DEFINE([HAVE_SETPROCTITLE], [], [Define if you have setproctitle])
-		IRCDLIBS="$IRCDLIBS-lutil"],
-		[
-		AC_EGREP_HEADER([#define.*PS_STRINGS.*],[sys/exec.h],
-			[AC_DEFINE([HAVE_PSSTRINGS],[], [Define if you have PS_STRINGS])],
-			[AC_CHECK_FUNCS([pstat],
-				[AC_DEFINE([HAVE_PSTAT], [], [Define if you 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], [], [Define if you have POSIX signals])
-elif test "$ac_cv_sigtype" = "BSD"; then
-	AC_DEFINE([BSD_RELIABLE_SIGNALS], [], [Define if you have BSD signals])
-else
-	AC_DEFINE([SYSV_UNRELIABLE_SIGNALS], [], [Define if you have SYSV signals])
-fi 
-AC_CHECK_FUNCS(strtoken,,AC_DEFINE([NEED_STRTOKEN], [], [Define if you need the strtoken function.]))
-AC_CHECK_FUNCS(strtok,,AC_DEFINE([NEED_STRTOK], [], [Define if you need the strtok function.]))
-AC_CHECK_FUNCS(strerror,,AC_DEFINE([NEED_STRERROR], [], [Define if you need the strerror function.]))
-AC_CHECK_FUNCS(index,,AC_DEFINE([NOINDEX], [], [Define if you do not have the index function.]))
-AC_CHECK_FUNCS(strtoul,,STRTOUL="strtoul.o")
-AC_CHECK_FUNCS(bcopy,,AC_DEFINE([NEED_BCOPY], [], [Define if you don't have bcopy]))
-AC_CHECK_FUNCS(bcmp,,AC_DEFINE([NEED_BCMP], [], [Define if you don't have bcmp]))
-AC_CHECK_FUNCS(bzero,,AC_DEFINE([NEED_BZERO], [], [Define if you need bzero]))
-AC_CHECK_FUNCS(strcasecmp,AC_DEFINE([GOT_STRCASECMP], [], [Define if you have strcasecmp]))
-save_libs="$LIBS"
-LIBS="$LIBS $SOCKLIB $INETLIB"
-AC_CHECK_FUNCS(inet_addr,,AC_DEFINE([NEED_INET_ADDR], [], [Define if you need inet_addr]))
-AC_CHECK_FUNCS(inet_ntoa,,AC_DEFINE([NEED_INET_NTOA], [], [Define if you need inet_ntoa]))
-AC_CHECK_FUNCS(inet_netof,,AC_DEFINE([NEED_INET_NETOF], [], [Define if you need inet_netof]))
-LIBS="$save_libs"
-AC_CHECK_FUNCS(syslog,AC_DEFINE([HAVE_SYSLOG], [], [Define if you have syslog]))
-AC_SUBST(STRTOUL)
-AC_SUBST(CRYPTOLIB)
-AC_SUBST(MODULEFLAGS)
-AC_ARG_WITH(listen, [AS_HELP_STRING([--with-listen=backlog],[Specify the listen backlog value])],
-	[AC_DEFINE_UNQUOTED([LISTEN_SIZE], [$withval], [Set to the listen backlog size you want])],
-	[AC_DEFINE([LISTEN_SIZE], [5], [Set to the listen backlog size you want])])
-AC_ARG_WITH(nick-history, [AS_HELP_STRING([--with-nick-history=length],[Specify the length of the nickname history])],
-	[AC_DEFINE_UNQUOTED([NICKNAMEHISTORYLENGTH], [$withval], [Set to the nickname history length you want])],
-	[AC_DEFINE([NICKNAMEHISTORYLENGTH], [2000], [Set to the nickname history length you want])])
-AC_ARG_WITH([sendq], [AS_HELP_STRING([--with-sendq=maxsendq],[Specify the max sendq for the server])],
-	[AC_DEFINE_UNQUOTED([MAXSENDQLENGTH], [$withval], [Set to the max sendq you want])],
-	[AC_DEFINE([MAXSENDQLENGTH], [3000000], [Set to the max sendq you want])])
-AC_ARG_WITH(bufferpool, [AS_HELP_STRING([--with-bufferpool=size],[Specify the size of the buffer pool])],
-	[AC_DEFINE_UNQUOTED([BUFFERPOOL],[($withval * MAXSENDQLENGTH)], [Set to the bufferpool size you want])],
-	[AC_DEFINE([BUFFERPOOL],[(18 * MAXSENDQLENGTH)], [Set to the bufferpool size you want])])
-AC_ARG_WITH(permissions, [AS_HELP_STRING([--with-permissions=permissions], [Specify the default permissions for
-configuration files])],
-	dnl We have an apparently out-of-place 0 here because of a MacOSX bug and because
-	dnl we assume that a user thinks that `chmod 0600 blah' is the same as `chmod 600 blah'
-	dnl (#3189)
-	[AC_DEFINE_UNQUOTED([DEFAULT_PERMISSIONS], [0$withval], [The default permissions for configuration files. Set to 0 to prevent unrealircd from calling chmod() on the files.])],
-	[AC_DEFINE([DEFAULT_PERMISSIONS], [0600], [The default permissions for configuration files. Set to 0 to prevent unrealircd from calling chmod() on the files.])]) 
-AC_ARG_WITH(dpath, [AS_HELP_STRING([--with-dpath=path],[Specify the path where configuration files are stored])],
-	[AC_DEFINE_UNQUOTED([DPATH], ["$withval"], [Define the location of the configuration files])
-		IRCDDIR="$withval"],
-	[AC_DEFINE_UNQUOTED([DPATH], ["`pwd`"], [Define the location of the configuration files])
-		IRCDDIR="`pwd`"])
-
-AC_ARG_WITH(fd-setsize, [AS_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], [Set to the max connections you want])
-
-dnl It would be nice if this could just respect --bindir like every other
-dnl program does someday... -- ohnobinki
-AC_ARG_WITH(spath, [AS_HELP_STRING([--with-spath],[Specify the location of the executable])],
-	[AC_DEFINE_UNQUOTED([SPATH], ["$withval"], [Define the location of the executable])
-		BINDIR="$withval"],
-	[AC_DEFINE_UNQUOTED([SPATH], ["`pwd`/src/ircd"], [Define the location of the executable])
-		BINDIR="`pwd`/src/ircd"])
-
-AC_ARG_ENABLE([prefixaq],
-	[AS_HELP_STRING([--disable-prefixaq],[Enable chanadmin (+a) and chanowner (+q) prefixes])],
-	[],
-	[enable_prefixaq=yes])
-AS_IF([test $enable_prefixaq = "yes"],
-	[AC_DEFINE([PREFIX_AQ], [], [Define if you want +a/+q prefixes])])
-
-AC_ARG_WITH(showlistmodes,
-	[AS_HELP_STRING([--with-showlistmodes], [Specify whether modes are shown in /list])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([LIST_SHOW_MODES], [], [Define if you want modes shown in /list])])])
-AC_ARG_WITH(topicisnuhost, [AS_HELP_STRING([--with-topicisnuhost], [Display nick!user@host as the topic setter])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([TOPIC_NICK_IS_NUHOST], [], [Define if you want nick!user@host shown for the topic setter])])])
-AC_ARG_WITH(shunnotices, [AS_HELP_STRING([--with-shunnotices], [Notify a user when he/she is no longer shunned])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([SHUN_NOTICES], [], [Define if you want users to be notified when their shun is removed])])])
-AC_ARG_WITH(no-operoverride, [AS_HELP_STRING([--with-no-operoverride], [Disable OperOverride])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([NO_OPEROVERRIDE], [], [Define if you want OperOverride disabled])])])
-AC_ARG_WITH(disableusermod, [AS_HELP_STRING([--with-disableusermod], [Disable /set* and /chg*])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([DISABLE_USERMOD], [], [Define if you want to disable /set* and /chg*])])])
-AC_ARG_WITH(operoverride-verify, [AS_HELP_STRING([--with-operoverride-verify], [Require opers to invite themselves to +s/+p channels])],
-	[AS_IF([test $withval = "yes"],
-		[AC_DEFINE([OPEROVERRIDE_VERIFY], [], [Define if you want opers to have to use /invite to join +s/+p channels])])])
-AC_ARG_WITH(disable-extendedban-stacking, [AS_HELP_STRING([--with-disable-extendedban-stacking], [Disable extended ban stacking])],
-       [AS_IF([test $withval = "yes"],
-       		[AC_DEFINE([DISABLE_STACKED_EXTBANS], [], [Define to disable extended ban stacking (~q:~c:\#chan, etc)])])])
-AC_ARG_WITH(system-tre, [AS_HELP_STRING([--with-system-tre], [Use the system tre package instead of bundled, discovered using pkg-config])], [], [with_system_tre=no])
-AC_ARG_WITH(system-cares, [AS_HELP_STRING([--with-system-cares], [Use the system c-ares (at least version 1.6.0) package instead of bundled c-ares, discovered using pkg-config])], [], [with_system_cares=no])
-CHECK_SSL
-CHECK_ZLIB
-AC_ARG_ENABLE(dynamic-linking, [AS_HELP_STRING([--disable-dynamic-linking], [Make the IRCd statically link with shared objects rather than dynamically (noone knows if disabling dynamic linking actually does anything or not)])],
-	[enable_dynamic_linking=$enableval], [enable_dynamic_linking="yes"])
-AS_IF([test $enable_dynamic_linking = "yes"],
-	[AC_ENABLE_DYN],
-	[AC_DEFINE([STATIC_LINKING], [], [Link... statically(?) (defining this macro will probably cause the build tofail)])])
-
-AC_ARG_ENABLE([inet6], [AS_HELP_STRING([--enable-inet6], [Make the IRCd support IPv6])],
-	[AS_IF([test $enableval = "yes"],
-		[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_COMPILE_IFELSE([
-#include <sys/types.h>
-#include <sys/time.h>
-int main() {
-#if FD_SETSIZE < $ac_fd
-#error FD_SETSIZE is smaller than $ac_fd
-#endif
-exit(0);
-}
-], AC_MSG_RESULT([yes]), [
-# must be passed on the commandline to avoid a ``warning, you redefined something''
-FD_SETSIZE="-DFD_SETSIZE=$ac_fd"
-AC_MSG_RESULT(no)
-])
-AC_SUBST([FD_SETSIZE])
-
-case `uname -s` in
-	*SunOS*|*solaris*)
-		AC_DEFINE([_SOLARIS], [], [Define if you are compiling unrealircd on Sun's (or Oracle's?) Solaris])
-		IRCDLIBS="$IRCDLIBS -lresolv "
-		;;
-esac
-
-dnl c-ares needs PATH_SEPARATOR set or it will
-dnl fail on certain solaris boxes. We might as
-dnl well set it here.
-export PATH_SEPARATOR
-
-AS_IF([test "x$with_system_tre" = "xno"],[
-dnl REMEMBER TO CHANGE WITH A NEW TRE RELEASE!
-tre_version="0.8.0"
-AC_MSG_RESULT(extracting TRE regex library)
-cur_dir=`pwd`
-cd extras
-dnl remove old tre directory to force a recompile...
-dnl and remove its installation prefix just to clean things up.
-rm -rf tre-$tre_version rege[]xp
-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 || exit 1
-AC_MSG_RESULT(compiling TRE regex library)
-$ac_cv_prog_MAKER || exit 1
-AC_MSG_RESULT(installing TRE regex library)
-$ac_cv_prog_MAKER install || exit 1
-TRE_CFLAGS="-I$cur_dir/extras/regexp/include"
-AC_SUBST(TRE_CFLAGS)
-
-TRE_LIBS=
-dnl See c-ares's compilation section for more info on this hack.
-dnl ensure that we're linking against the bundled version of tre
-dnl (we only reach this code if linking against the bundled version is desired).
-AS_IF([test -n "$ac_cv_path_PKGCONFIG"],
-       [TRE_LIBS="`$ac_cv_path_PKGCONFIG --static --libs tre.pc | sed -e ['s,-L\([^ ]*regex[^ ]*lib\)\( .*\)-ltre,\1/libtre.a \2,']`"])
-dnl For when pkg-config isn't available -- or for when pkg-config
-dnl doesn't see the tre.pc file somehow... (#3982)
-AS_IF([test -z "$TRE_LIBS"],
-       [TRE_LIBS="../extras/regexp/lib/libtre.a"])
-AC_SUBST(TRE_LIBS)
-cd $cur_dir
-],[
-dnl use pkgconfig for tre:
-PKG_CHECK_MODULES([TRE], tre >= 0.7.5)
-])
-
-AS_IF([test "x$with_system_cares" = "xno"],[
-dnl REMEMBER TO CHANGE WITH A NEW C-ARES RELEASE!
-dnl NOTE: when changing this here, ALSO change it in ./curlinstall
-dnl       and in the comment in this file around line 400!
-cares_version="1.10.0"
-AC_MSG_RESULT(extracting c-ares resolver library)
-cur_dir=`pwd`
-cd extras
-dnl remove old c-ares directory to force a recompile...
-rm -rf c-ares-$cares_version c-ares
-if test "x$ac_cv_path_GUNZIP" = "x" ; then
-	tar xfz c-ares.tar.gz
-else
-	cp c-ares.tar.gz c-ares.tar.gz.bak
-	gunzip -f c-ares.tar.gz
-	cp c-ares.tar.gz.bak c-ares.tar.gz
-	tar xf c-ares.tar
-fi
-AC_MSG_RESULT(configuring c-ares library)
-cd c-ares-$cares_version
-./configure --prefix=$cur_dir/extras/c-ares --disable-shared || exit 1
-AC_MSG_RESULT(compiling c-ares resolver library)
-$ac_cv_prog_MAKER || exit 1
-AC_MSG_RESULT(installing c-ares resolver library)
-$ac_cv_prog_MAKER install || exit 1
-CARES_CFLAGS="-I$cur_dir/extras/c-ares/include"
-AC_SUBST(CARES_CFLAGS)
-CARES_LIBS="-L../extras/c-ares/lib"
-
-dnl Set default library parameters for when pkg-config is not available
-dnl Ugly cd'ing out of extras/c-ares-xxx ;)
-dnl Note: must be a full path, not relative path.
-cd ../..
-CARESLIBSALT="`pwd`/extras/c-ares/lib/libcares.a"
-cd -
-case `uname -s` in
-	*FreeBSD*)
-		CARESLIBSALT="$CARESLIBSALT"
-		;;
-	*Linux*)
-		CARESLIBSALT="$CARESLIBSALT -lrt"
-		;;
-	*SunOS*)
-		CARESLIBSALT="$CARESLIBSALT -lrt"
-		;;
-esac
-
-dnl Use pkg-config for c-ares libraries, and if not available use defaults
-dnl from above. Also, if pkg-config returns an empty result (ex: on fbsd
-dnl or older versions it might be missing --static) then also use defaults.
-if test "x$ac_cv_path_PKGCONFIG" = "x" ; then
-	CARES_LIBS="$CARES_LIBS $CARESLIBSALT"
-else
-	CARES_LIBSPRE="$CARES_LIBS"
-	dnl the sed expression forces an absolute path to the .a file to be generated
-	dnl because this is what libtool would do. If this wasn't done and /usr/lib*/libcares.so
-	dnl exists, then unrealircd would still try to link against the system c-ares.
-	dnl The [] quotation is needed because the sed expression has [] in it.
-	[CARES_LIBS="$CARES_LIBS `$ac_cv_path_PKGCONFIG --static --libs libcares.pc | sed -e 's,-L\([^ ]\+lib\) -lcares,\1/libcares.a,'`"]
-	if test "$CARES_LIBS" = "$CARES_LIBSPRE " ; then
-		CARES_LIBS="$CARES_LIBS $CARESLIBSALT"
-	fi
-fi
-AC_SUBST(CARES_LIBS)
-cd $cur_dir
-],[
-dnl use pkg-config for system c-ares:
-PKG_CHECK_MODULES([CARES], libcares >= 1.6.0)
-])
-
-CHECK_LIBCURL
-
-AC_CONFIG_FILES([Makefile
-	src/modules/Makefile
-	unreal
-	ircdcron/ircdchk
-	ircdcron/ircd.cron])
-AC_OUTPUT
-chmod 0700 unreal
-chmod 0700 ircdcron/ircdchk

createchangelog

@@ -1,11 +0,0 @@
-#!/bin/sh
-# This will generate a Changelog similar to our original style.
-# New are: the name of the author, the date, and the short hash
-# We still filter translated doc changes as to not polute the
-# changelog too much.
-
-hg log -r a673dd0f7b37: --style changelog --template '[{date|shortdate}] {author} ({node|short}):\n- {desc}\n\n' \
--b default -X 'doc/unreal32docs.*.html' -X 'doc/help.*.conf' -X 'doc/example.*.conf' -X 'include/version.h'|\
-sed 's/^- - /- /g' >Changes
-
-echo "Done. File 'Changes' now contains the full version history"

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,85 +0,0 @@
-#!/bin/sh
-URL="http://www.unrealircd.com/files/curl-latest.tar.gz"
-OUTF="curl-latest.tar.gz"
-OUTD="curl-latest"
-ARESPATH="`pwd`/extras/c-ares"
-CARESVERSION="1.10.0"
-if [ ! -f "Unreal.nfo" ]; then
-	echo "Please run this program from your UnrealIRCd directory"
-	echo "(usually $HOME/Unreal3.2 or something like that)"
-	exit 1
-fi
-
-wget --version 1>/dev/null 2>&1
-if [ "$?" = 0 ]; then
-	FETCHER="wget"
-else
-	fetch --version 1>/dev/null 2>&1
-	if [ "$?" = 0 ]; then
-		FETCHER="fetch"
-	else
-		lynx --version 1>/dev/null 2>&1
-		if [ "$?" = 0 ]; then
-			FETCHER="lynx"
-		else
-			echo "ERROR: unable to find wget/fetch/lynx, please install at least one of these programs"
-			exit 1
-		fi
-	fi
-fi
-
-if [ ! -d tmp ]; then
-	mkdir tmp || exit 1
-fi
-
-cd tmp || exit 1
-
-rm -f "$OUTF"
-
-if [ "$FETCHER" = "wget" ]; then
-	wget -O "$OUTF" "$URL"
-elif [ "$FETCHER" = "lynx" ]; then
-	lynx -dump "$URL" >"$OUTF"
-elif [ "$FETCHER" = "fetch" ]; then
-	cd tmp #todo: find out the cmd line parameter ;)
-	fetch "$URL"
-fi
-
-if [ "$?" != 0 ]; then
-	echo "ERROR: Something went wrong while trying to download $URL"
-	exit 1
-fi
-
-rm -rf "$OUTD" # remove old directory prior to extracting
-tar xzf "$OUTF" || exit 1
-
-
-if [ "`eval echo -n 'a'`" = "-n a" ] ; then
-        c="\c"
-else
-        n="-n"
-fi
-
-if [ ! -d "$ARESPATH/lib" ]; then
-	echo "c-ares has not been build yet, let's do that now..."
-	cd ../extras/
-	tar xzf c-ares.tar.gz || exit 1
-	cd c-ares-$CARESVERSION || exit 1
-	./configure --prefix=$ARESPATH || exit 1
-	(make && make install) || exit 1
-	cd ../../tmp/
-	echo "c-ares built."
-	echo ""
-fi
-
-# We assume curl has been packaged in a way it will extract to "$OUTD"/
-cd "$OUTD" || exit 1
-
-echo "Building and installing libcurl"
-CPPFLAGS="-I$ARESPATH/include" ./configure --prefix=$HOME/curl --disable-shared \
- --disable-thread --enable-ares=$ARESPATH --disable-ipv6 $SSLFLAG
-cp -R $ARESPATH/lib ares
-make && make install
-
-#cp $ARESPATH/lib/libcares.a $HOME/curl/lib
-# that isn't needed anymore as the lib is already in unreal...

dccallow.conf

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

doc/Authors

@@ -118,14 +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 - December 2008
-Dominick Meglio <codemastr@unrealircd.com> / June 1999 - August 2005
-David Flynn / March 2000 - June 2000
-McSkaf / June 2001 - September 2001
-Finny Merrill <griever@unrealircd.com> / November 2001 - December 2002
-Bram Matthys <syzop@unrealircd.com> / January 2002 - date
-This list is incomplete, type /INFO on IRC to find the updated list.
+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.
@@ -145,4 +139,4 @@ Eric P. Scott <eps@toaster.sfsu.edu>
 Dan Goodwin <fornax@wpi.wpi.edu>
 Noah Friedman <friedman@ai.mit.edu>
 
-[ $Id$ ]
+[ $Id$ ]

doc/Crule.readme

@@ -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/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/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/RELEASE.NOTES-3.1.4

@@ -0,0 +1,39 @@
+
+Unreal3.1.4-Meadows Release Notes
+===================================
+
+* This is yet another significant upgrade over the last version. Most notable
+  compatibility wise is the backporting of the new host cloaking from 3.2.
+  As a result of this, we strongly recommend that you convert all of your servers
+  to 3.1.4 and avoid running a network with mixed versions. They'll link fine
+  and operate okay, but the differences in cloaking will make it easier for
+  individuals to evade bans by simply switching servers.
+
+* Before this version if a 3.2 server with IPv6 enabled was linked to the
+  network, and a client connected using IPv6, it caused 3.1.x servers to segfault,
+  as the cloaking routine was unable to deal with IPv6 format addresses. This is
+  also corrected in this version
+
+* Other serious bugs involving the mode system have been resolved. These problems
+  include problems that could potentially generate a desynch on the network. This is
+  yet another reason you should use all 3.1.4 servers.
+
+* The OperOverride system is completely redone. You must now invite yourself (as an
+  oper) into a channel in order to walk any modes on join.
+
+* Please Note: There have been a couple of configuration file changes! This is
+  IMPORTANT. Your IRCd WILL NOT START if you don't change the cloak key values found
+  in unrealircd.conf. Additionally, it would be prudent to note that there is a
+  new directive in unrealircd.conf, exempt_all, which permits exempt lines in
+  ircd.conf to match glines in addition to klines. It defaults to 1. Finally, both
+  version numbers in the .network file and unrealircd.conf have been changed. In
+  unrealircd.conf, because of the 4 new directives. In the .network file because
+  we removed techadmin, and the host directive for it. We will NOT bring techadmin
+  back. If you don't like it, readd it yourself, and be sure to note that we won't
+  provide support for modified versions of Unreal. 
+
+* The rest of the changes can be found (obviously) in the Changes file.
+
+* Finally, read Unreal.nfo as usual AND THE DOCS in doc/.
+
+- Luke (luke@unrealircd.com)

doc/RELEASE.NOTES-3.1.5

@@ -0,0 +1,25 @@
+
+Unreal3.1.5-Valek Release Notes
+===================================
+
+* IMPORTANT: OperOverride has been modified. In order to be
+  able to override anything as an oper, you MUST have the letter
+  "v" in your O line flags!
+
+* This release is mostly a bug fix release. It resolves the
+  following issues as well as some others:
+    - Bug with /invite not propagating
+    - Bug with channel exempts being added multiple times
+    - Bug with channel exempts multiplying on synch (to resolve
+      this bug entirely *all* your servers must run 3.1.5)
+    - Bug with /userhost always displaying *
+    - Others (read the Changes file in .)
+
+* If you are upgrading from an earlier version (before 3.1.4),
+  please read the doc/RELEASE-NOTES.3.1.4 file as well. There
+  were numerous important/significant changes between 3.1.4 and
+  earlier versions.
+
+* Finally, read Unreal.nfo as usual AND THE DOCS in doc/.
+
+- Luke (luke@unrealircd.com)

doc/coding-guidelines

@@ -1,141 +0,0 @@
-Rules about patches & modifications to UnrealIRCd
-
-1. When making a change, always add a small description in Changes, in the
-   BOTTOM. Don't forget to mention the bug# and credit the reporter (if any).
-
-2. If new files are made, it must contain proper copyright headers.
-
-3. If you want to submit patches (f.e. if you don't have CVS write access)
-   then submit them to http://bugs.unrealircd.org/ (shortly called bugs*)
-   using "cvs diff -u > patchname". A submission must contain description of
-   what it does, etc.
-
-4. Each bug or feature should have a bug# so people can have a discussion
-   about it. This has a few implications (read!!):
-   * People must report bugs/feature requests to bugs* and not on
-     IRC, e-mail, etc.
-   * That means other people can see the bug# and comment on it. This means
-     discussion is easy to read back for each issue and not spread between
-     several IRC logs.
-     Furthermore, by using the bugtracker instead of directly committing,
-     people could point out that there might be a better way to do things
-     than you originally thought, or it might be that other devs don't like
-     it at all.
-   * If a head coder has 'acknowledged' or 'confirmed' the bug or stated in
-     a comment that it's OK to implement, then a dev may take the issue.
-     The dev should change the status to 'assigned' and work on it, then
-     commit and change it to 'resolved', set 'fixed in version' to next
-     release, and add a comment pasting the relevant Changelog item and the
-     releaseid (.XYZ).
-     Of course other guidelines, like #7 and #8 still apply.
-
-5. Do not commit changes that do not have an associated bug# and have not
-   had any discussion.
-   Small/tiny bugfixes that do not change any functionality, are very
-   unlikely to break anything and definitely don't require any prior
-   discussion may be exempted.
-
-6. Regarding reidenting, restructuring or other code cleanups: please
-   discuss before doing so. The other devs might not agree with you on the
-   particular cleanup you have in mind which would result in another
-   clean-up-the-cleanup commit.
-   You may, however reindent and clean up individual sections when you are
-   working on fixing a particular bug# or implementing a new feature. In fact
-   you're encouraged to do so if the code is confusing without it. However,
-   obey the style of Unreal's code (mostly outlined in this document)
-   and do not introduce yet another (new) style. Also, be careful with doing
-   any cleanup: if you're unsure in any way about the use of something,
-   or something that looks redundant on first sight, then look more
-   carefully... it might indeed be useless and/or redundant, but it might
-   also be a subtle thing that can create great bugs when 'cleaned up'.
-
-7. Prior to a release: be very careful with any restructuring of a subsystem
-   or doing any major commits that may break things. Stuff like this can be
-   perfectly fine if there are many months to go, but are not good to do a
-   month before release. The head coder may impose additional restrictions
-   during such a period.
-
-8. During the Release Candidate stage (from RC1 until the final release)
-   only the head coder may commit directly, all others should ask and
-   present their patch before committing. Yes, even if you are changing only
-   1 line of code or text.
-
-9. UnrealIRCd should compile on all supported operating systems and
-   platforms, using GCC 3 or higher on *NIX, and Visual Studio 2008 or
-   higher on Windows. This means you cannot blindly use all C99 extensions.
-
-10. Coders should test their code before committing.
-
-11. /*  
-     * These kind of comments
-     */
- 
-   NOT
- 
-   // These kind of comments
-
-12. 	if (something == 1) 
-   	{
-		moo; /* comment */
-		/* This does what what what */
-		cow(go(moo));
-	}
-	
-	NOT 
-	
-	if (something == 1) {
-	}
-	
-13. Do not touch version.c.SH or version.h, unless you are a head coder
-    if you need a credit in, contact us
-   
-14. Protocol changes must be discussed before making patches for it.
-
-15. We do NOT rip people off. If we use other people's code, it MUST be
-    properly credited.
-
-16. We generally use tabsize 4 and 8. In any case, use tabs and NOT spaces.
-    Some code is old and horrible and has a mix of tabs and spaces used for
-    spacing, that's something we do not want to have ;)
-
-17. Be careful about overflows. As you know a line from a user can never be longer
-    than 511 (510?) characters, sometimes you can use this knowledge to your
-    advantage. Whenever it's not safe or when you don't know what input size you
-    can expect, use strlcpy instead of strcpy. Do not ever use strncpy, this is
-    older, slower, and does not add proper zero termination.
-    For the same reason, use snprintf if really needed. Note though, that using
-    ircsprintf with a bigger buffer (eg: 1024 bytes) is MUCH faster, so preferably
-    use that instead of snprintf. The same can be true for strcpy vs strlcpy in
-    some circumstances as well.
-
-18. Speed.  When optimizing or writing code, keep in mind that readability and
-    stability comes FIRST, and after that comes speed. So we'd rather prefer some
-    readable code (even if difficult) over some odd highly optimized routine which
-    nobody understands, is difficult to extend, and might have several bugs.
-    As mentioned earlier: use ircsprintf, not sprintf (this is because ircsprintf
-    is optimized for simple strings like the ones we use).
-    Prefer ircsprintf with a bigger buffer over the use of snprintf, since
-    ircsprintf is much faster.
-
-19. Initialize your structs and use the proper memory calls.
-    In UnrealIRCd we use MyMalloc, MyMallocEx and MyFree (so not malloc/free).
-    MyMalloc usually maps to malloc, and MyMallocEx is a malloc plus filling
-    the memory area (eg: the struct) with zero's (a la calloc).
-    Use of MyMallocEx is suggested. In general you should not be using MyMalloc.
-    "But MyMalloc is faster!" you might say. This is true, but using MyMallocEx
-    has very little speed impact and enormous benefits: people tend to forget
-    to set certain fields in the struct to NULL, or much more common: when
-    someone later on (eg: 1 year later) adds a field to a struct, there could
-    be several places he/she needs to update to make sure x->something is NULL
-    after allocating a new struct. Bad idea.
-    Little speed impact, huge stability benefits, easy decision ;).
-
-20. Comment your code! This should speak for itself...
-    Put comments wherever you think they are needed, to aid any further coders
-    with reading your code.. and, in fact, it will aid yourself as well if you
-    would look back at your code 2 years later.
-    If there's some obscure pitfall, do mention it! Don't just "hope" a next
-    author will see it like you did.
-
-21. Use enums whenever possible, rather than #define constants. Besides making
-    things more clean, it also aids debugging.

doc/commands.txt

@@ -0,0 +1,329 @@
+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
+
+NACHAT
+ - Similar to CHATOPS, 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,118 +0,0 @@
-==[ GENERAL GUIDELINES ]==
-First of all you need Microsoft Visual C++ (see below), compiling with
-cygwin is not supported.
-
-Compatible compilers:
-cygwin      NOT supported. Will not work. Should be no reason to use this anyway
-            as cygwin is an emulation layer. It's obviously much better to run
-            native (Windows) code on Windows.
-msvc  6.x   Microsoft Visual Studio 6 does not work, this compiler is too old.
-msvc  7.x   Microsoft Visual Studio 7.x (.NET), works.
-msvc  8.x   Microsoft Visual Studio 8.x (.NET 2005), including the free kit, works.
-msvc  9.x   Microsoft Visual Studio 9.x (.NET 2008), is used for official compile.
-mssdk       Microsoft Windows SDK for Windows 7
-
-If you don't have the paid version of Microsoft Visual Studio 7.x, then you can
-use the FREE development kit available for Windows 7 explained below:
-1. Download the 'MS SDK for Windows 7 and .NET Framework 3.5 SP1' at:
-   http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505&displaylang=en
-      
-2. NOTE: Whenever you need to compile something we say 'Start the Visual Studio
-   .NET Command Prompt' below, but you - a person using the free version - will
-   actually have to start the CMD Shell instead (check out the
-   Start Menu under Microsoft Windows SDK v7.0). Users on x64 environment will have
-   to change their environment to x86 by typing 'SETENV /x86'.    
-
-3. Download http://www.vulnscan.org/tmp/dlltool.exe and put the file somewhere
-   in your path (eg: put it in c:\windows\system32).
-
-==[ EXTERNAL LIBRARIES ]==
-Fetch the external libraries (c-ares, tre, openssl, zlib, curl) from:
-http://www.vulnscan.org/unrealwin32dev/
-
-==[ COMPILING ]==
-1. Start the Visual Studio .NET Command Prompt
-2. Go to your UnrealIRCd dir (like: cd \dev\unreal3.2)
-3. Have a look at 'makefile.win32' to look at what parameters you need to
-   use, this depends on what libraries you want to link in and their location.
-4. Two options, use either one (B is preferred), and read step 5 too:
-   A. Edit makefile.win32 directly to reflect your configuration and run
-      'nmake -f makefile.win32'
-   B. Don't edit makefile.win32 but instead create a one-line command (which
-      you can put in a batch file), like this (all on one line!):
-      nmake -f makefile.win32 USE_ZIPLINKS=1 ZLIB_INC_DIR="c:\dev\zlib"
-      ZLIB_LIB_DIR="c:\dev\zlib\dll32" USE_SSL=1
-      OPENSSL_INC_DIR="c:\openssl\include" OPENSSL_LIB_DIR="c:\openssl\lib"
-      USE_REMOTEINC=1 LIBCURL_INC_DIR="c:\dev\curl-ssl\include"
-      LIBCURL_LIB_DIR="c:\dev\curl-ssl\lib\dll-release"
-      CARES_LIB_DIR="C:\dev\c-ares\vc\cares\dll-release"
-      CARES_INC_DIR="C:\dev\c-ares" CARESLIB="cares.lib"
-      TRE_LIB_DIR="C:\dev\tre\win32\release" TRE_INC_DIR="C:\dev\tre"
-      TRELIB="tre.lib"
-5. You are likely to encounter an error like
-   M_OPER.obj : error LNK2019: unresolved external symbol _sendto_snomask_global
-   referenced in function _m_oper
-   (the exact name and symbol will differ!!)
-   In that case you need to generate a symbols file:
-   nmake -f makefile.win32 SYMBOLFILE
-   And after that simply re-run your nmake -f makefile.win32 [options]
-   command, the same command you ran before the error occured.
-   You should not get any unresolved external symbol error again.
-   If you still do, then something is wrong.
-6. Your compile is now done, you can package unreal if you have InnoSetup,
-   in that case check out src\win32\unrealinst.iss
-   Otherwise, manually copy over the necessary files (and the dll files
-   from the external libraries).
-
-==[ Compiling modules ]==
-1. Put your module (the .c file) in src\modules (eg: c:\dev\unreal3.2\src\modules).
-2. Start the Visual Studio .NET Command Prompt
-3. Go to your UnrealIRCd dir (like: cd \dev\unreal3.2).
-4. Compile the module with:
-   nmake -f makefile.win32 <YOUR OPTIONS> custommodule MODULEFILE=<name>
-   <name> is the name of the module WITHOUT the .c suffix, so if your
-   module has the filename 'm_crappymod.c', then you use:
-   nmake -f makefile.win32 <YOUR OPTIONS> custommodule MODULEFILE=m_crappymod
-   Note that <YOUR OPTIONS> is the whole lot of options explained in
-   previous section under 4B. If you use method 4A then there aren't any.
-   Note 2: If you get any symbol file errors, see the section 'SYMBOL FILES'
-5. Done. A .dll file should have been created.
-
-If you compiled with the same Visual Studio version that we use to compile
-the official UnrealIRCd version, and use the same Unreal3.2.X.tar.gz as the
-official version (and not CVS!), then your module is fully binary compatible
-and you can put it on your website (or ours) so users can use them.
-If you do anything else, this won't work.
-So, again, it will NOT work properly, if:
-1. You use a different UnrealIRCd source (like CVS, or a previous version).
-2. You use another compiler... this might still work but may require an
-   additional .DLL file to be put in your UnrealIRCd directory (MSVxxxxxx.DLL).
-3. You compile with different options, such as compiling with SSL but trying
-   to load the module on non-SSL.
-   NOTE: unless your module uses SSL-specific code, you should compile
-         without SSL as it will run on both SSL and non-SSL UnrealIRCd's.
-
-==[ SYMBOL FILES ]==
-If you get something like this:
-
-  Creating library L_COMMANDS.lib and object L_COMMANDS.exp
-M_OPER.obj : error LNK2019: unresolved external symbol _sendto_snomask_global re
-ferenced in function _m_oper
-
-(note: the exact name of the symbol will vary!)
-
-Then you will have to rebuild the wircd.def symbol file. You do this by
-downloading http://www.vulnscan.org/tmp/dlltool.exe and putting the file somewhere
-in your path (eg: c:\winnt\system32).
-Then, to compile you do this:
-nmake -f makefile.win32 [your other options here]
-nmake -f makefile.win32 SYMBOLFILE
-nmake -f makefile.win32 [your other options here]
-
-So basically you just run 'nmake -f makefile.win32 SYMBOLFILE' and then restart
-compiling again.
-
-==[ COMPILING ZLIB/SSL/CURL YOURSELF ]==
-This is off-topic and not explained here.
-Again, use the stuff from the win32 development pack unless you have a good
-reason to do otherwise.

doc/example.de.conf

@@ -1,786 +0,0 @@
-/*
- * example.conf von Daniel Hawton AKA Osiris (osiris@unrealircd.org).
- * $Id$
- * 
- * Arbeitet mit Unreal3.2.x
- * 
- * Dies hier ist die neue example.conf. Sie ähnelt irgendwie ein wenig C++ und sie
- * soll sie jedenfalls einmal erläutert werden. Es ist ein wenig schwer, erstmals
- * damit umzugehen, aber mit ein Wenig Übung und sorgfältigem Lesen sollte das zu 
- * verstehen sein.
- *
- * Diese Datei ist einfach in das Hauptverzeichnis des UnrealIRCD zu kopieren und in
- * 'unrealircd.conf' umzubenennen.
- * 
- * ZU BEACHTEN: Sämtliche Zeilen außer der mit einer '{' zu Beginn werden mit dem Zeichen
- * ';' beendet, auch die Zeile mit '}'. (Beliebter Syntaxfehler!)
- * Kommentar Zeilen werden vom IRCd ignoriert.
- *
- * BITTE LESE die doc/unreal32docs.html! Sie ist auch online erhältlich bei:
- * www.vulnscan.org/UnrealIrcd/unreal32docs.html
- * Diese Datei enthält zahlreiche ergänzende Informationen über jeden Block, Variablen usw.
- * Übersetzung durch stylus740@smart-irc.de (bei irc.smart-irc.net)
- */
-
-/* Kommentar Typen */
-#Kommentar Typ 1 (Shell Typ)
-// Kommentar Typ 2(C++ Stil)
-/* Kommentar Typ 3 (C Stil) */
-#Solche Zeilen vom Typ 1, 2 oder 3 werden vom ircd ignoriert.
-
-/*
- * UnrealIRCd arbeitet mit Modulen, die geladen werden, wenn sie benötigt werden.
- * Man benötigt mindestens das commands Modul und ein cloaking Modul.
- */
-
-/* FÜR *NIX (Unix, Linux, Xenix etc.), sind diese 2 Zeilen auszukommentieren: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* FÜR Windows sind diese 2 Zeilen auszukommentieren: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Man kann über eine 'include' Anweisung auch weitere Konfigurationsdateien einfügen.
- * help.conf enthält sämtliche /helpop Texte. Die badwords.*.conf filtert alle badword
- * Einträge für den Modus +G...
- * Die spamfilter.conf enthält einige wirksame Regeln für aktuelle Trojaner.
- * Falls man diese Dateien mit einfügen möchte:
- */
-include "help.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * NEU: me {} 
- * ALT: M:Line 
- * me {} legt Name, Beschreibung und eindeutige Nummer ('numeric') für diesen Server fest.
- * Syntax ist wie folgt: 
- * me { 
- *  name "server.name"; 
- *  info "Server Beschreibung";
- *  numeric (server numeric*);
- * }; 
- * Falls der Server mit anderen gelinkt wird, darf muss die Nummer bei 'numeric' eindeutig
- * sein, darf also von keinem anderen Server im Netzwerk verwendet werden.
- */
-me
-{
-	name "irc.foonet.com";
-	info "FooNet Server";
-	numeric 1;
-};
-
-/*
- * NEU: admin {} 
- * ALT: A:Line 
- * Admin liefert Informationen über den Server Administrator. Man kann
- * so viele Zeilen unter 'admin {' angeben, wie man will. 
- * Syntax ist wie folgt:
- * admin {
- *   "erste Zeile"; 
- *   "zweite Zeile"; 
- *   [usw]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"widely@used.name";
-};
-
-/*
- * NEU: class {} 
- * ALT: Y:line (alte Form war verwirrend) 
- * Hiermit werden Klassen und ihre Einstellungen festgelegt. Eine Klasse ist eine Gruppen-
- * einstellung für Verbindungen. So kann man beispielsweise Server Verbindungen in einer
- * eigenen Klasse behandeln, statt zusammen mit Clients.
- * Syntax ist wie folgt:
- * class (class name)
- * {
- *     pingfreq (wie oft in Sekunden wird ein user/server angepingt);
- *     maxclients (wie viele Verbindungen sind in dieser Klasse möglich);
- *     sendq (maximale send Queue einer Verbindung);
- *     recvq (maximale Empfangs Queue einer Verbindung [Flood Kontrolle!]);
- *  };
- */
-
-class           clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class           servers
-{
-	pingfreq 90;
-	maxclients 10;		/* Wieviele Servers können gleichzeitig gelinkt sein */
-	sendq 1000000;
-	connfreq 100;           /* Wieviele Sekunden zwischen jedem Verbindungsversuch */
-};
-
-/*
- * NEU: allow {} 
- * ALT: I:Line
- * Hier wird festgelegt, welche Verbindungen erlaubt sind...
- * Grundlegend kann man damit Clienten erlauben, zu verbinden und hat etwas Kontrolle
- * Syntax ist wie folgt: 
- * allow {
- *    ip (ip Maske für allow);
- *    hostname (host Maske);
- *    class (Klasse, die zugewiesen wird [siehe class {}]);
- *    password "(password)"; (optional)
- *    maxperip (wie viele Verbindungen je IP); (optional) 
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* Passworded allow line */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.passworded.ugly.people;
-	class           clients;
-	password "f00Ness";
-	maxperip 1;
-};
-
-/*
- * NEU: allow channel {} 
- * ALT: chrestrict 
- * Erlaubt es Usern, einen Channel zu betreten...
- * Ist wie eine Ausnahme von 'deny channel'. 
- * Syntax ist wie folgt:
- * allow channel {
- *   channel "channel name";
- * };
- */
-allow           channel {
-	channel "#WarezSucks";
-};
-
-/*
- * NEU: oper {} 
- * ALT: O:Line 
- * Legt einen IRC Operator fest
- * IRC Operatoren halten den Server in Ordnung, warten ihn und halten die Verbindung 
- * zum Netzwerk. 
- * Syntax ist wie folgt: 
- * oper (login) { 
- *     class (Klasse, die zugewiesen wird, falls anders als meine, wird eine neuee Klasse
- *                zugewiesen); 
- *     from { 
- *        userhost (ident@host);
- *        userhost (ident@host);
- *     }; 
- *     flags
- *     { 
- *       (Flags hier*);
- *     };
- *     ODER
- *     flags "alte Form von Flags, wie OAaRD";
- * };
- */
-
-
-/* Die Liste möglicher Oper Flags kann in doc/unreal32docs.html#operblock nachgelesen werden
- * [WIRKLICH empfehlenswert, zu lesen!]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * NEU: listen {}
- * ALT: P:Line
- * Legt den Port fest, an dem der ircd 'lauscht', um Usern/Servern zu erlauben, eine 
- * Verbindung zum Server aufzunehmen. 
- * Syntax ist wie folgt:
- * listen (ip number):(port number) 
- * { 
- *   options {
- *     (options here);
- *   };
- * };
- * oder für ein einfaches listen:
- * listen (ip):(port);
- * 
- * ACHTUNG: für ipv6 ips (3ffe:b80:2:51d::2 etc), benutze listen [ip]:port;
- * 
- * Das funktioniert ebenfalls.
- */
-
-/* Options for listen:
-	OLD	| 	NEW
-	S		serversonly
-	C		clientsonly
-	J		java
-	s		ssl
-	*		standard
-*/
-
-/* ZU BEACHTEN BEI SSL PORTS: SSL Ports sind nicht standardisiert.
- * Es wird oft gesagt, man solle den Port 994 benutzen, weil dies der
- * offizielle SSL Port sei. Aber das erfordert root Rechte! Andererseits
- * ist der Port 194 der offizielle Port und wann hat man je einen Ircd
- * auf diesem Port laufen gesehen?
- * Unsere Empfehlung ist, den Port 6697 für SSL zu benutzen, wie es auch
- * bei vielen anderen Netzwerken gemacht wird und für z.B. StunTour benutzt wird.
- * Man kann so viele SSL Ports öffnen, wie man will, aber wenn man (auch) den Port
- * 6697 benutzt, hilft man mit, die Welt ein klein wenig zu standardisieren ;).
- */
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* ACHTUNG: Wird der IRCd auf einer Shell mit verschiedenen IP's ausgeführt, kann
- *          die Fehlermeldung 'Address already in use' ('Adresse wird schon benutzt')
- *          in den Logfiles auftauchen und der IRCd startet nicht.
- *          Das bedeutet, dass man eine spezifische Adresse anstelle von '*' definieren
- *          MUSS, wie z.B.:
- *          listen 1.2.3.4:6667;
- *          Es sollte klar sein, dass die IP durch die zu ersetzen ist, die einem
- *          zugewiesen ist.
- */
-
-/*
- * NEU: link {}
- * ALT: C/N:Lines
- * Hiermit wird ein okay für eine Server Verbindung festgelegt.
- * ACHTUNG: BEIDE SERVER MÜSSEN EINE LINK {} EINSTELLUNG HABEN, UM KORREKT ZU VERBINDEN!
- * Syntax ist wie folgt:
- * link (server name)
- * {
- *	username	(username, * funktioniert auch);
- * 	hostname	(ip Nummer/Hostmaske);
- *	bind-ip	(Welche IP soll zum Verbinden benutzt werden, oder *);
- *	port		(Port, zu dem verbunden werden soll);
- *	hub (Wenn dies ein Hub ist, funktioniert * , oder Servermasken);
- *	[oder leaf *;]
- *	password-connect "(Passwort zu senden)";
- *	password-receive "(Passwort, welches wir emfangen sollten)";
- *	class		(Klasse, in die Server sollen);
- *	options {
- *		(options hier*);
- *	};
- *      // Wird SSL benutzt, kann bestimmt werden, welche Verschlüsselung im SSL 
- *      // Modus zu benutzen ist
- *      // Bei mehreren "openssl ciphers" sind die einzelnen Verschlüsselungen 
- *      // durch ':' zu trennen
- *      
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-	options:
-	OLD	|	NEW
-	S		ssl
-	Z		zip
-	N/A		autoconnect
-	N/A		quarantine
-	N/A		nodnscache
-*/
-
-
-link            hub.mynet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Achtung: autoconnect sollte nicht benutzt werden, wenn man Services linkt */
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * NEU: ulines {}
- * ALT: U:Line
- * U-lines geben Servern mehr Möglichkeiten/Befehle, sie sollten NUR für Services/Stats
- * gesetzt werden und NIEMALS für normale UnrealIRCd Server!
- * Syntax ist wie folgt:
- * ulines {
- *	(server to uline);
- *	(server to uline);
- *  [etc]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * NEU: drpass {}
- * ALT: X:Line
- * Hiermit werden die Passworte für /die und /restart festgelegt.
- * Syntax ist wie folgt:
- * drpass { 
- *  restart			"(Passwort für Restart)";
- *  die		      "(Passwort für die (die = 'sterben' = Abschaltung))";
- * };
- */
-drpass {
-	restart "I-love-to-restart";
-	die "die-you-stupid";
-};
-
-/*
- * NEU: log {} ALT: N/A Festlegung von Namen und Speicherort der Logfiles. Man kann
- * beliebig viele festlegen.
- * 
- * FLAGS: errors, kills, tkl, connects, server-connects, oper
- * 
- * Syntax: 
- * log "log file" 
- * {
- *    flags
- *    {
- *        flag;
- *        flag; 
- *        etc.. 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-	/* Lösche das Logfile und starte ein neues, wenn 2MB erreicht wurden,  
-	   nichts festlegen, wenn man immer das gleiche Log will */
-	maxsize 2097152;
-	flags {
-		oper;
-		kline;
-		connects;
-		server-connects;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * NEU: alias {}
- * ALT: N/A
- * Hier kann man Befels Aliasse festlegen, wie z.B. /nickserv, /chanserv usw.
- * FLAGS: services, stats, normal
- *
- * Syntax:
- * alias "name" {
- *	target "points to";
- *	type aliastype;
- * };
- *
- * [ACHTUNG: Mann kann hier auch eine Datei mit vordefinierten Aliassen per include
- * einfügen. Siehe auch: doc/unreal32docs.html Abschnitt 2.9]
- */
-
-// Hiermit wird der Befehl /nickserv an den User NickServ geleitet, welcher zur Einstellung set::services-server server verbunden ist
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Soll der Befehl auf denselben Nick wie das der Befehl leiten, kann man den Nick auslassen
-//alias ChanServ { type services; };
-
-// leitet den /statserv Befehl an den User StatServ aus set::stats-server server
-//alias StatServ { type stats; };
-
-// leitet den /superbot Befehl an den User SuperBot
-//alias SuperBot { type normal; };
-
-
-/* Standard Aliasse */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * NEU: alias {}
- * ALT: N/A
- * Hier können Befehls Aliase, wie z.B.: /identify, /services, usw festgelegt werden.
- *
- * Syntax:
- * alias "name" {
- *	format "format string" {
- *		target "zeigt auf";
- *              type aliastype;
- *		parameters "zu sendende Parameter";
- *	};
- *	type command;
- * };
- */
-/* Die nachfolgenden Zeilen eigens deshalb, um zu zeigen, dass trotz gleichem Namens die vorherige Anweisung
- * völlig unterschiedlich in der Syntax ist, obwohl eine ähnliche Funktion unterstützt wird.
- */
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-/* Die alias::format Anweisung ist ein regulärer Ausdruck. Das erste Format passt auf den /identify Befehl,
- * wenn das erste Zeichen ein # ist. Dann wird dies an den chanserv alias mit dem Parameters IDENTIFY
- * %1- übergeben. Das zweite Format passt auf den /identify Befehl, wenn das erste Zeichen kein # ist. Danach
- * wird der Befehl an den nickserv alias mit den Parameters IDENTIFY %1- geleitet.
- */
-
-/* Die alias::format::parameters Scripting Sprachen ähnlich. %N (wobei N einen Nummer ist) repräsentiert einen
- * Parameter, der an den Befehl (in diesem Fall /identify) zu senden ist. Wird  %N- angegeben, bedeutet dies
- * alle Parameter vom N bis zum letzten Parameter des Strings. Man kann ebenso %n angeben, welches durch den 
- * Nicknamen des users ersetzt wird.
-*/
-
-/* Standard Aliasse */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-
-/*
- * NEU: tld {}
- * ALT: T:Line
- * Hiermit werden unterschiedliche motd und rules Dateien in Abhängigkeit
- * von der Hostmaske des Clients eingestellt.
- * Syntax ist wie folgt: 
- * tld {
- *    mask (ident@host);
- *    motd "(motd file)";
- *    rules "(rules file)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* zu beachten: Will man nur die default motd/rules Dateien (ircd.motd, ircd.rules)
- * für jedermann benutzen, genügt es, den obigen Beispiel Block einfach zu löschen.
- */
-
-/*
- * NEU: ban nick {}
- * ALT: Q:Line
- * Bannt einen Nicknamen, so dass dieser nicht benutzt werden kann.
- * Syntax ist wie folgt:
- * ban nick {
- *	mask "(nick to ban)";
- *	reason "(reason)";
- * };
-*/
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Reserviert für Services";
-};
-/*
- * NEU: ban ip {}
- * ALT: Z:Line
- * Bannt eine IP, so dass diese nicht mehr zum Netzwerk verbinden kann.
- * Syntax:
- * ban ip { mask (ip Nummer/Hostmaske); reason "(Grund)"; };
-*/
-ban ip {
-	mask 195.86.232.81;
-	reason "Server nicht mehr gelinkt";
-};
-/*
- * NEU: ban server {}
- * ALT: Server Q:Line
- * Nimmt einem Server die Möglichkeit, zum Neztwerk zu verbinden.
- * Wenn der Server zu einem anderen Server des Netzwerkes linkt, wird der
- * lokale server die Verbindung zum Netzwerk trennen.
- * Syntax ist wie folgt:
- * ban server {
- *	mask "(Server Name)";
- *	reason "(angegebener Grund)";
- * };
-*/
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Hau ab hier.";
-};
-/*
- * NEU: ban user {}
- * ALT: K:Line
- * Bewirkt, dass ein User mit einer bestimmten Maske nicht mehr zum Server verbinden kann.
- * Syntax:
- * ban user { mask (Hostmaske/ip Nummer); reason "(Grund)"; };
-*/
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-        reason "Idiot";
-};
-
-/*
- * NEU: ban realname {}
- * ALT: n:Line
- * Verhindert, dass ein bestimmter Realname benutzt werden kann.
- * Syntax:
- * ban realname {
- *	mask "(Realname)";
- * 	reason "(Grund)";
- * };
-*/
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * Sämtliche Banns dürfen durch zusätzliche Einträge wiederholt werden!
- * 
- * NEU: except ban {} 
- * ALT: E:Line
- * Diese Maske ist von Banns ausgenommen. 
- * Syntax:
- * except ban { mask (ident@host); };
- * except ban {} kann so oft angegeben werden, wie man für verschiedene Hosts will.
- */
-
-except ban {
-	/* don't ban stskeeps */
-	mask           *stskeeps@212.*;
-};
-
-/*
- * NEU: deny dcc {} 
- * ALT: dccdeny.conf
- * Mit diesem Block können dcc send's geblockt werden... Gut, um Viren aufzuhalten. 
- * Syntax: 
- * deny dcc 
- * { 
- *   filename "zu sperrende Datei(ie, *exe)";
- *   reason "Grund";
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Möglicherweise Sub7 Virus";
-};
-
-/*
- * NEU: deny channel {}
- * ALT: N/A (NEW)
- * Verhindert, dass angegebene Channels benutzt werden können.
- * Syntax:
- * deny channel {
- * 	channel "(channel)";
- * 	reason "Grund";
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "Warez sind illegal";
-};
-
-/*
- * NEU: vhost {}
- * ALT: Vhost.conf file
- * Setzt eine Fake IP für Nicht-Opers, oder opers, die zu bequem für /sethost sind.... :P
- * Syntax:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (ident@host um die Nutzung zu gestatten);
- *       };
- *       login (Loginname);
- *       password (Passwort);
- *   };
- *        um den vhost zu nutzen, mache /vhost (login) (password) im IRC
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Man kann hier weitere Config Dateien einfügen */
-/* include "klines.conf"; */
-
-/* Network configuration */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 		"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix		"rox";
-	/* prefix-quit 		"no"; */
-	/* Cloak keys müssen angegeben sein und sie müssen die selben auf allen Servern
-       * im Netzwerk sein. Sie werden zur Generierung der maskierten Hosts verwendet
-	 * und sie sollten geheim gehalten werden.
-	 * Die Keys sollten 3 zufällige Strings von 5-100 Zeichen Länge sein (10-20 Zeichen
-	 * (sind ganz ok) und müssen aus Kleinbuchstaben(a-z), Großbuchstaben (A-Z) und
-       * Ziffern (0-9) bestehen [wie im ersten Key Beispiel].
-       * TIPP: Auf *NIX, kann man in der Shell './unreal gencloak' aufrufen und durch
-  	 *       Unreal 3 Zufalls Stings erzeugen und anzeigen lassen.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"und noch einer";
-		"und noch einer";
-	};
-	/* on-oper Host */
-	hosts {
-		local			"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin			"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 		"netadmin.roxnet.org";
-		host-on-oper-up 	"no";
-	};
-};
-
-/* Server spezifische Configuration */
-
-set {
-	kline-address "setze.diese.email";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#opers";
-	options {
-		hide-ulines;
-		/* Man kann hier ident checking aktivieren, wenn man will */
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* Die Mindestzeit, die ein User verbunden sein muss, bevor er eine QUIT Meldung
-	 * senden darf (Das wird offentlich helfen, Spam zu verhindern) */
-	anti-spam-quit-message-time 10s;
-	/* Macht die Meldung statisch, die in allen Quit Meldungen angezeigt wird.
-           Somit sind keine individuellen Quts auf dem lokalen Server mehr erlaubt */
-	/* static-quit "Client quit";	*/
-
-	/* Man kann auch sämtliche Part Meldungen blocken, indem man dies auskommentiert
-       * und 'yes' sagt oder einen anderen Text angibt (z.B. "Bye bye!")
-	/* static-part yes; */
-
-	/* Hiermit kann man bestimmte stats auf ausschliesslich Opers beschränken. Für
-       * alle Stats kann man * benutzen. Wenn man es weglässt, können alle User alle
-       * Stats abfragen. Eine vollständige Liste erhält man mit dem Befehl '/stats'.
-	 * Manche Admins entfernen 'kGs' und erlauben so normalen Usern die Anzeige von
-	 * klines, glines and shuns.
-	 */
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Throttling: Dieses Beispiel setzte ein Limit von 3 Verbindungen je 60s (pro Host). */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Anti Flood Schutz */
-	anti-flood {
-		nick-flood 3:60;	/* 3 Nickänderungen pro 60 Sekunden (Default) */
-	};
-
-	/* Spam Filter */
-	spamfilter {
-		ban-time 1d; /* Default Dauer eines *line Banns durch Spamfilter */
-		ban-reason "Spam/Belästigung"; /* default Grund */
-		virus-help-channel "#help"; /* Channel, der für die 'viruschan' action benutzt wird*/
-		/* except "#help"; Channel, der von Filtern ausgenommen wird */
-	};
-};
-
-/*
- * Probleme? Weitere Hilfe nötig?
- * 1) www.vulnscan.org/UnrealIrcd/unreal32docs.html
- * 2) www.vulnscan.org/UnrealIrcd/faq/ <- enthält 80% deiner Fragen - Wetten Dass?
- * 3) Hat man dann noch Probleme, kann man den Chat bei irc.unrealircd.org 
- *    #unreal-support aufsuchen. Achtung, wir setzen voraus, dass zuvor die 
- *    DOKU GELESEN WURDE (genauso, wie die FAQ!)!
- */

doc/example.es.conf

@@ -1,842 +0,0 @@
-/*
- * example.conf por Danial Hawton, alias Osiris (osiris@unrealircd.org).
- * Traducido al castellano por Severus_Snape (javiersnape@gmail.com).
- * 
- * Funciona desde Unreal3.2.x
- * 
- * Ok. Este es el nuevo example.conf. Es muy similar a C++.
- * De todas formas lleva tiempo hacer esto. En un principio, es dificil de comprender pero
- * con un poco de práctica y lectura lo comprenderás.
- *
- * Simplemente copia este archivo al directorio principal de unrealircd y cambiale el nombre a 'unrealircd.conf'.
- * 
- * NOTA: Todas las líneas, a excepción de la línea de apertura ( { ) terminan en ;, incluyendo la
- * línea de cierre ( } ). El IRCd ignorará las lineas comentadas.
- *
- * ¡POR FAVOR LEE doc/unreal32docs.es.html! La versión online esta disponible en:
- * www.vulnscan.org/UnrealIRCd/unreal32docs.es.html
- * Contiene mucha información acerca del archivo de configuración: Da información acerca de
- * cada bloque, variable, etc.
- * ¡Si intentas editar este archivo sin leer bien la documentación
- * estas destinado a fallar!
- */
-
-/* Tipos de Comentarios */
-#Comentario tipo 1 (Estilo Shell)
-// Comentario tipo 2 (Estilo C++)
-/* Comentario tipo 3 (Estilo C) */
-#Estas líneas son ignoradas por el IRCd.
-
-/*
- * UnrealIRCd soporta módulos, cargar algunos de ellos es requerido.
- * Al menos debes cargar el módulo de los comandos y un módulo de cifrado (cloaking).
- */
-
-/* PARA *NIX, descomenta las siguientes 2 líneas: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* PARA Windows, descomenta las siguientes 2 líneas: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Además pudes incluir otros archivos de configuración.
- * help.conf contiene todo el contenido de /helpop. Los archivos badwords.*.conf
- * contienen todas las entradas de badwords para el modo +G...
- * spamfilter.conf contiene algunas buenas reglas para los troyanos actuales.
- * Probablemente quieres incluirlos:
- */
-include "help.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * NUEVO: me {} 
- * VIEJO: M:Line 
- * me {} define el nombre, la descripción y el número de servidor
- * para este server. La Sintaxis es: 
- * me { 
- *  name "nombre.del.servidor"; 
- *  info "Descripción del Servidor";
- *  numeric (número del servidor*);
- * }; 
- *  * = Si estas enlazando este server, el número no debe ser usado por otro server en la red.
- */
-me
-{
-	name "irc.foonet.com";
-	info "FooNet Server";
-	numeric 1;
-};
-
-/*
- * NUEVO: admin {} 
- * VIEJO: A:Line
- * /Admin te da la información acerca del administrador del servidor. Tu
- * puedes poner cuantas líneas quieras debajo de admin {.
- * La sintaxis es:
- * admin {
- *   "primera línea"; 
- *   "segunda línea"; 
- *   [etc]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"widely@used.name";
-};
-
-/*
- * NUEVO: class {} 
- * VIEJO: Y:line (old was confusing) 
- * Esto define la configuración para las clases. Una clase es una configuración en grupo para las
- * conexiones. Por ejemplo, las conexiones de los servidores, en vez de ir a la clase de los clientes.
- * la diriges a la clase de servidores. La sintaxis es la siguiente:
- * class (nombre de la clase)
- * {
- *     pingfreq (que tan seguido pingueara a el servidor/cliente en segundos);
- *     maxclients (cuantas conexiones para esta clase);
- *     sendq (cola máxima de envios para la conexión);
- *     recvq (cola máxima de mensajes recibidos desde la conexión [Control de Flood]);
- *  };
- */
-
-class           clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class           servers
-{
-	pingfreq 90;
-	maxclients 10;		/* Cantidad máxima de servers que podemos enlazar a la vez */
-	sendq 1000000;
-	connfreq 100; /* Cuentos segundos entre cada intento de conexión */
-};
-
-/*
- * NUEVO: allow {} 
- * VIEJO: I:Line
- * Esto define los permisos de las conexiones...
- * Fundamentalmente para los clientes, les permite conectarse así tu puedes tener un poco de
- * control y/o poner una contraseña. 
- * La sintaxis es la siguiente: 
- * allow {
- *    ip (IP/IPs a permitir);
- *    hostname (nombre de host);
- *    class (clase asignada a esta conexión [ver class {}]);
- *    password "(contraseña)"; (opcional)
- *    maxperip (cuantas conexiones por IP); (opcional) 
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* allow {} con contraseña */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.gente.fea.con.clave;
-	class           clients;
-	password "f00Ness";
-	maxperip 1;
-};
-
-/*
- * NUEVO: allow channel {} 
- * VIEJO: chrestrict 
- * Permite a un usuario unirse a un canal...
- * como una expeción de deny channel.
- * Sintaxis:
- * allow channel {
- *   channel "#nombredelcanal";
- * };
- */
-allow           channel {
-	channel "#WarezApestan";
-};
-
-/*
- * NUEVO: oper {} 
- * VIEJO: O:Line 
- * Define a un Operador de IRC
- * Los Operadores de IRC estan para mantener al servidor "sano" y usualmente
- * mantenerlo y tenerlo conectado a la red. 
- * La sintaxis es la siguiente: 
- * oper (login) { 
- *     class (clase para ponerlos, si es difirente de la que esta en allow {], los mueve a la nueva clase); 
- *     from { 
- *        userhost (ident@host);
- *        userhost (ident@host);
- *     }; 
- *     flags
- *     { 
- *       (las flags aqui*);
- *     };
- *     O
- *     flags "flags antiguas como, OAaRD";
- * };
- */
-
-
-/* Para una lista de banderas de operador, lea doc/unreal32docs.es.html#operblock
- * [lectura ALTAMENTE recomendada]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * NUEVO: listen {}
- * VIEJO: P:Line
- * Esto define el puerto/IP a el que el IRCd debe escuchar y unirse, esto
- * permite a los usuarios/servidores conectarse al servidor.
- * La sintaxis es:
- * listen (Dirección IP):(número de puerto) 
- * { 
- *   options {
- *     (opciones aqui);
- *   };
- * };
- * o simplemente
- * listen: listen (ip):(puerto);
- * 
- * NOTA: para IPs IPv6 (3ffe:b80:2:51d::2, etc.), use listen [ip]:puerto;
- * 
- * Eso también funciona.
- */
-
-/* Opciones para listen {}:
-	VIEJAS	| 	NUEVAS	| 	SIGNIFICADO
-	S		serversonly		Sólo Servidores
-	C		clientsonly		Sólo Clientes
-	J		java		Sólo Clientes Java
-	s		ssl		Conexion Cifrada (SSL)
-	*		standard	Standard
-*/
-
-/* NOTA EN PUERTOS SSL: Los puertos SSL no están estandarizados,
- * muchos puertos SSL estan en números muy altos, algunas personas dicen que deberias hacerlo
- * en el puerto 994 por que ese es el puerto SSL oficial... ¡pero eso
- * requiere acceso root! Además, el puerto 194 es el puerto oficial de IRC... y
- * has visto alguna vez ver un IRCd corriendo en ese puerto? Usan el 6667.
- * Asi que, nuestra sugerencia es que uses el puerto 6697 para SSL, ese puerto es usado por
- * una cantidad de redes decente y es reconozido por ejemplo: por StunTour.
- * Además eres libre de abrir cuantos puertos SSL quieras, pero
- * correr uno en 6697 ayudaría al mundo a estandarizarlo un poco mas :).
- */
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* NOTA: Si estas en shell IRCd con multiples IPs, normalmente
- *       obtendras un error como 'La dirección ya esta en uso/Address already in use' en tus logs
- *       y el IRCd no iniciará. Esto significa que tu DEBES unir el IRCd
- *       a una IP específica en vez de '*', por ejemplo:
- *       listen 1.2.3.4:6667;
- *       Obviamente, reemplaza esa IP con la IP que se te fue asignada.
- */
-
-/*
- * NUEVO: link {}
- * VIEJO: C/N:Lines
- * Esto define los enlazes entre servidores.
- * NOTA: ¡LOS DOS SERVIDORES NECESITAN UN BLOQUE LINK {} PARA ENLAZARSE BIEN!
- * La sintaxis es:
- * link (nombre.del.servidor)
- * {
- *	username	(nombre de usuario, * también funciona);
- * 	hostname	(dirección IP/máscara de host);
- *	bind-ip		(A que IP unirse cuando se estan enlazando, o *);
- *	port		(Puerto al cual conectarse);
- *	hub (Si esto es un hub, * funciona.);
- *	[o leaf *;]
- *	password-connect "(contraseña a enviar)";
- *	password-receive "(contraseña que deberiamos)";
- *	class		(Clase a donde dirigir los servers);
- *	options {
- *		(las opciones van aqui*);
- *	};
- *      // Si tu uses SSL, debes escoger que cifrado usar en el modo SSL
- *      // Obtiene una lista con "openssl ciphers", separa los métodos de cifrados con ":"
- *      
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-	opciones:
-	VIEJAS	|	NUEVAS	|	SIGNIFICADO
-	S		ssl		Usar SSL
-	Z		zip		Comprimir los datos enviados.
-	N/A		autoconnect	su servidor intentará conectar automáticamente.
-					El tiempo usado entre intentos es el que especificó en class::connfreq
-					(se recomienda para un sólo lado, de leaf a hub)
-	N/A		quarantine	Aislar
-	N/A		nodnscache	No usar Caché DNS (Muy útil para DDNS)
-*/
-
-
-link            hub.mynet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Nota: No deberias usar autoconnect cuando conectas servicios */
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * NUEVO: ulines {}
- * VIEJO: U:Line
- * Las ulines {} le dan a los servidores mas poder/comandos, ¡esto SOLO debe ser usado
- * para los servidores de servicios/estadísticas y NUNCA para servidores UnrealIRCd normales!.
- * (Para un buen funcionamiento, todos los servidores deberían tener los mismos U:Lines)
- * La Sintaxis es la siguiente:
- * ulines {
- *	(servidor a ulinear);
- *	(servidor a ulinear);
- *  [etc]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * NUEVO: {}
- * VIEJO: X:Line
- * Esto define las contraseñas para /die y /restart.
- * La sintaxis es:
- * drpass { 
- *  restart		"(contraseña para reiniciar)";
- *  die		        "(contraseña para matar al IRCd)";
- * };
- */
-drpass {
-	restart "amo-reiniciar";
-	die "muere-inepto";
-};
-
-/*
- * NUEVO: log {} 
- * VIEJO: N/A
- * Le dice al IRCd donde y que loguear. Puedes tener cuantos tu quieras.
- * 
- * FLAGS: errors, kills, tkl, connects, server-connects, oper
- * 
- * Sintaxis: 
- * log "archivo.log" 
- * {
- *    flags
- *    {
- *        flag;
- *        flag; 
- *        etc... 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-	/* Borra el archivo e inicia uno nuevo cuando logre 2MB, no uses esto para siempre usar el mismo log */
-	maxsize 2097152;
-	flags {
-		oper;
-		connects;
-		server-connects;
-		kills;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * NUEVO: alias {}
- * VIEJO: N/A
- * Esto te permite hacer aliases de comandos como /nickserv, /chanserv, etc.
- * FLAGS: services, stats, normal
- *
- * Sintaxis:
- * alias "nombre" {
- *	target "apunta a";
- *	type aliastype;
- * };
- *
- * [NOTA: Tu también puedes usar un archivo de aliases-predefinidos, lea doc/unreal32docs.es.html sección 2.9]
- */
-
-// Esto apunta el comando a /nickserv a el usuario NickServ el cual esta conectado con el servidor de set::services-server.
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Si tu quieres el comando que apunta al el mismo nick que el comando, puedes dejar la entrada "nick" vacia.
-//alias ChanServ { type services; };
-
-// Apunta el comando /statserv a el usuario StatServ en el servidor set::stats-server.
-//alias StatServ { type stats; };
-
-// Apunta el comando /superbot a el usuario SuperBot
-//alias SuperBot { type normal; };
-
-
-/* Aliases Standard */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * NUEVO: alias {}
- * VIEJO: N/A
- * Esto te permite configurar aliases de comandos como /identify, /services, etc.
- *
- * Sintaxis:
- * alias "nombre" {
- *	format "Formato de la Cadena" {
- *		target "apunta a";
- *              type tipodealias;
- *		parameters "parametros a enviar";
- *	};
- *	type command;
- * };
- */
-/* Esto es mostrado separadamente por que hasta tiene el mismo nombre que la directiva anterioir as, es muy diferente en sintaxis,
- * pero provee una función muy similar.
- */
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-/* La directiva alias::format es una expresión regular. El primer formato coincide con el comando /identify cuando
- * el primer carácter es #. Luego pasa esto a ChanServ con los parámetros IDENTIFY
- * %1-. El segundo formato coincide con /identify cuando el primer caracter no es un #. Entonces
- * el comando pasa a nickserv con los parámetros IDENTIFY %1-.
- */
-
-/* El alias::format::parameters es similar a los lenguajes de scripting. %N (donde N es un número) representa el
- * parámetro enviado al comando (en este caso, /identify). Si especificas %N- significa "todos los parámetros desde
- * N hasta el último parámetro en la cadena". También puedes especificar %n que es reemplazado por el nick del usuario.
-*/
-
-/* Aliases Standard */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-/* Este es un ejemplo de un alias de comando real */
-/* Esto redirije /GLINEBOT a /GLINE <parámetro> Los Bots 2D... */
-alias "glinebot" {
-	format ".+" {
-		command "gline";
-		type real;
-		parameters "%1 Los Bots 2D no están permitidos en este servidor, para mas información lea la faq en http://www.ejemplo.com/faq/123";
-	};
-	type command;
-};
-
-/*
- * NUEVO: files {}
- * VIEJO: include/config.h
- *
- * Este bloque se sobrepone con el dirctorio principal del IRCd para cargar cosas
- * como el MOTD, el PIPfile, o escribir/cargar el tunefile. La
- * existencia de este bloque permite una instalación de UnrealIRCd a
- * soportar múltiples instancias corriendo cuando es combinado con la opción -c
- * en la línea de comandos.
- *
- * Usualmente. Los directorios relativos son interpretados relativamente a el directorio
- * donde UnrealIRCd encuentra unrealircd.conf si -c -no-
- * es especificado en la línea de comandos.
- */
-files
-{
-	/* El Mensaje del Dia (MOTD - Message of the Day) mostrado a los usuarios que se conectan: */
-	/* motd ircd.motd; */
-
-	/*
-	 * Un MOTD corto. Si el archivo existe, sera mostrado a
-	 * el usuario en vez del MOTD. Los usuarios todavia podrán ver el
-	 * MOTD completo usando el comando /MOTD.
-	 */
-	/* shortmotd ircd.smotd; */
-
-	/* Mostrado cuando un operador usa /OPER y se loguea exitosamente. */
-	/* opermotd oper.motd; */
-
-	/* El MOTD de los Servicios. */
-	/* svsmotd ircd.svsmotd; */
-
-	/* El MOTD de los Bots */
-	/* botmotd bot.motd; */
-
-	/* Las reglas que se muestran al usar /RULES */
-	/* rules ircd.rules; */
-
-	/*
-	 * Donde el IRCd guarda y carga algunos parámetros que deberían
-	 * ser persistentes entre reinicios del servidor. Debe apuntar a un
-	 * archivo existente el cual el IRCd tiene permiso para alterarlo o un
-	 * archivo en una carpeta donde el IRCd puede crear archivos.
-	 */
-	/* tunefile ircd.tune; */
-
-	/* Donde guardar el PID del IRCd. Debería ser modificable por el IRCd. */
-	/* pidfile ircd.pid; */
-};
-
-/*
- * NUEVO: tld {}
- * VIEJO: T:Line
- * Esto configura MOTDs y RULES distintos
- * dependiendo en la máscara de host del cliente.
- * La sintaxis es: 
- * tld {
- *    mask (ident@host);
- *    motd "(archivo-motd)";
- *    rules "(archivo-rules)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* NOTA: tu puedes simplemente borrar el bloque de ejemplo aqui arriba,
- * en ese caso los MOTD/RULES normales (ircd.motd, ircd.rules)
- * serán usados para todos.
- */
-
-/*
- * NUEVO: ban nick {}
- * VIEJO: Q:Line
- * Banea a un nick, así no puede ser usado.
- * La sintaxis es la siguiente:
- * ban nick {
- *	mask "(nick a banear)";
- *	reason "(rasón)";
- * };
-*/
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Reservado para los Servicios";
-};
-/*
- * NUEVO: ban ip {}
- * VIEJO: Z:Line
- * Banea una IP de conectarse a la red.
- * Sintaxis:
- * ban ip { mask (ip/hostmask); reason "(rasón)"; };
-*/
-ban ip {
-	mask 195.86.232.81;
-	reason "Servidor delinkeado";
-};
-/*
- * NUEVO: ban server {}
- * VIEJO: Server Q:Line
- * Prohibe a un servidor de conectarse a la red.
- * Si el servidor se linkea a un servidor remoto, el servidor local
- * se desconectará de la red.
- * La sintaxis es la siguiente:
- * ban server {
- *	mask "(nombre.del.servidor)";
- *	reason "(Rasón)";
- * };
-*/
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Fuera de aca.";
-};
-/*
- * NUEVO: ban user {}
- * VIEJO: K:Line
- * Esto hace que un usuario con una máscara de host determinada no se pueda conectar
- * a tu servidor.
- * Sintaxis:
- * ban user { mask (hostmask/ip); reason "(rasón)"; };
-*/
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-        reason "Idiota";
-};
-
-/*
- * NUEVO: ban realname {}
- * VIEJO: n:Line
- * Este bloque banea a un determinado realname (nombre real) de ser usado.
- * Sintaxis:
- * ban realname {
- *	mask "(nombre real)";
- * 	reason "(rasón)";
- * };
-*/
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * NOTA PARA TODOS LOS BANS, puedes repetirlos para agregar mas!
- * 
- * NUEVO: except ban {} 
- * VIEJO: E:Line
- * Eso hace que no puedas ser baneado.
- * Sintaxis:
- * except ban { mask (ident@host); };
- * Repite el except ban {} cuantas veces quieras
- * para diferentes bans.
- */
-
-except ban {
-	/* no banees a stskeeps */
-	mask           *stskeeps@212.*;
-};
-
-/*
- * NUEVO: deny dcc {} 
- * VIEJO: dccdeny.conf
- * Use este block para denegar DCC SENDs...
- * detiene a los virus mejor.
- * Sintaxis
- * deny dcc 
- * { 
- *   filename "(archivo a bloquear (por ejemplo: *.exe"));
- *   reason ("rasón");
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Posiblemente un virus Sub7";
-};
-
-/*
- * NUEVO: deny channel {}
- * VIEJO: N/A (NUEVO)
- * Esto bloquea canales de ser creados.
- * Sintaxis:
- * deny channel {
- * 	channel "(canal)";
- * 	reason "rasón";
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "El Warez es ilegal";
-};
-
-/*
- * NEW: vhost {}
- * OLD: Vhost.conf file
- * Setea una IP para los no-operadores, o
- * para opers muy flojos para hacer /sethost :P
- * Sintaxis:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (ident@host.a.permitir.usar.el.vhost);
- *       };
- *       login (nombre del login);
- *       password (contraseña);
- *   };
- *        para usar este vhost, usa /vhost (login) (contraseña) en IRC
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Puedes incluir otros archivos de configuración */
-/* include "klines.conf"; */
-
-/* Configuración de la red */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 	"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix	"rox";
-	/* prefix-quit 		"no"; */
-	/* Las llaves de cifrado (cloak keys) deberían ser las mismas en toda la red.
-	 * Son usadas para generar hosts "enmascarados" y mantenerlos secretos.
-	 * Las llaves deben ser 3 cadenas aleatorias de 5 a 100 carácteres
-	 * (de 10 a 20 es aceptable también) y deben tener una minúscula (a-z),
-	 * mayúscula (A-Z) y dígitos (0-9) [mira el ejemplo de la primera llave].
-	 * CONSEJO: En *NIX puedes ejecutar './unreal gencloak' en tu shell para hacer que
-	 *       Unreal genere tres cadenas aleatorias por ti.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"and another one";
-		"and another one";
-	};
-	/* host para los operadores */
-	hosts {
-		local		"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin		"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 	"netadmin.roxnet.org";
-		host-on-oper-up "no";
-	};
-};
-
-/* Configuración específica del servidor */
-
-set {
-	kline-address "configura.este@email";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#opers";
-	options {
-		hide-ulines;
-		/* Puedes habilitar el chequeo de ident si quieres*/
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* El tiempo mínimo que un usuario debe estar conectado antes de usar un mensaje QUIT,
-	 * Esto podria detener el spam */
-	anti-spam-quit-message-time 10s;
-	/* Hace que el mensaje en static-quit se muestr en todos kis quits - significando que
-           no se permiten quits personalizados en este servidor */
-	/* static-quit "El Cliente se desconectó";	*/
-
-	/* También puedes bloquear todas las razones de part, descomentando el siguiente comentario y poniendo 'yes',
-	 * o especificar otro mensaje (ejemplo: "¡Adiós!") para usar siempre como razón. */
-	/* static-part yes; */
-
-	/* Esto permite que pudas hacer algunos comandos de /stats solo para uso de los operadores, use * para ocultar todos los stats,
-	 * dejelo en blanco para permitir a los usuarios ver todos los /stats. Escriba '/stats' para una lista completa.
-	 * Algunos administradores querrán remover los stats "kGs" para prohibir a los usuarios normales ver los
-	 * klines, glines y shuns.
-	 */
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Regulación de Conexiones: este ejemplo setea un límite de 3 intentos de conexión cada 60 segundos (por host). */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Protección anti-flood */
-	anti-flood {
-		nick-flood 3:60;	/* 3 cambios de nick por cada 60 segunos (por defecto) */
-	};
-
-	/* Filtro de Spam */
-	spamfilter {
-		ban-time 1d; /* duración de un *line puesto por spamfilter (filtro de spam) */
-		ban-reason "Spam/Publicidad"; /* razón */
-		virus-help-channel "#help"; /* canal para usar para la acción "viruchan" */
-		/* exceptuar "#help"; el canal "#help" esta libre de filtro */
-	};
-};
-
-/*
- * Problemas o necesitas mas ayuda?
- * 1) www.vulnscan.org/UnrealIRCd/unreal32docs.es.html
- * 2) www.vulnscan.org/UnrealIRCd/faq/ (en inglés)<- ¡contiene el 80% de tus preguntas!
- * 3) Si sigues teniendo problemas, ve a irc.unrealircd.org #unreal-support,
- *    ¡nótese que NECESITAMOS que leas la DOCUMENTACIÓN y la FAQ antes de preguntarnos!
- */

doc/example.fr.conf

@@ -1,858 +0,0 @@
-/*
- * example.conf par Daniel Hawton AKA Osiris (osiris@unrealircd.org).
- * Ancien traducteur français : babass
- * Tradution française : Alef Burzmali - http://www.burzmali.com
- * Dernière mise à jour : 2010-09-11
- * $Id$
- *
- * Fonctionne pour Unreal3.2.x
- *
- * Okay les gars, voici la nouvelle version de l'example.conf. Cela ressemble plus à du C++.
- * Peu importe, il est temps de se lancer.  Il est difficile de l'attaquer pour la première fois, mais
- * avec un peu d'expérience et de lecture vous comprendrez.
- *
- * Copiez juste ce fichier dans votre répertoire unrealircd principal et appellez le 'unrealircd.conf'.
- *
- * NOTE: Toutes les lignes, exceptées les ligne d'ouvertures { , se terminent par un ;, en particulier
- * celles de fermeture }.
- * L'IRCd ignorera les lignes commentées.
- *
- * LISEZ S'IL VOUS PLAIT doc/unreal32docs.fr.html !
- * La version en ligne est aussi disponible à : http://www.unrealircd.com/files/docs/unreal32docs.fr.html
- * Elle contient beaucoup d'informations à propos du fichier de configuration : fournit des informations
- * à propos de chaque bloc, variable, etc..
- * Si vous essayez de modifier ce fichier sans avoir bien lu la documentation,
- * vous êtes presque sûr de vous tromper.
- */
-
-/* Type de commentaires */
-#Commentaire type 1 (type Shell)
-// Commentaire type 2 (style C++)
-/* Commentaire type 3 (style C) */
-# Toutes ces lignes sont ignorées par l'ircd.
-
-/*
- * UnrealIRCd supporte des modules et certains sont obligatoires.
- * Vous aurez besoin au moins du module commands et du module cloaking.
- */
-
-/* POUR *NIX, décommentez les 2 lignes suivantes : */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* POUR Windows, décommentez les 2 lignes suivantes : */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Vous pouvez également inclure d'autres fichiers de configuration.
- * doc/help.fr.conf contient tout le texte de /helpop en français.
- * help.conf contient la version anglaise.
- * Les fichiers badwords.*.conf contiennent tous les badwords pour le mode +G...
- * spamfilter.conf contient quelques bonnes règles pour les trojans courrants.
- * Vous voudrez probablement les inclure:
- */
-include "doc/help.fr.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * ACTUEL : me {}
- * ANCIEN : M:Line
- * me {} definit le nom, la description et l'identifiant numérique pour ce serveur.
- * La syntaxe est la suivante :
- * me {
- *  name "nom.du.serveur";
- *  info "Description du Serveur";
- *  numeric (numeric* serveur);
- * };
- * En cas de link, cet identifiant ne peut être utilisé pour aucun autre serveur du réseau.
- */
-me
-{
-	name "irc.foonet.com";
-	info "FooNet Server";
-	numeric 1;
-};
-
-/*
- * ACTUEL : admin {}
- * ANCIEN : A:Line
- * Admin donne des informations sur les server admins.
- * Vous pouvez mettre autant de lignes que vous voulez après admin {.
- * La syntaxe est la suivante :
- * admin {
- *   "première ligne";
- *   "deuxième ligne";
- *   [etc]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"widely@used.name";
-};
-
-/*
- * ACTUEL : class {}
- * ANCIEN : Y:line (l'ancien était déroutant)
- * Définit les réglages pour les classes. Une classe est un groupe de réglages pour
- * des connexions. Par exemple, pour les connexions serveurs, au lieu de passer par une classe
- * client, vous utilisez directement une classe serveur. La syntaxe est la suivante :
- * class (nom de la classe)
- * {
- *     pingfreq (fréquence des pings utilisateurs/serveurs en secondes);
- *     maxclients (combien de connexions pour cette classe);
- *     sendq (file d'attente maximum pour l'envoie depuis une connexion);
- *     recvq (file d'attente maximum pour la réception depuis une connexion [contrôle du flood]);
- *  };
- */
-
-class clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class servers
-{
-	pingfreq 90;
-	maxclients 10;  /* Nombre maximum de serveurs pouvant être reliés en même temps */
-	sendq 1000000;
-	connfreq 100;   /* Combien de secondes entre chaque tentatives de connexions */
-};
-
-/*
- * ACTUEL : allow {}
- * ANCIEN : I:Line
- * Définit les autorisations de connexions...
- * Principalement pour les clients, cela leur permet de se connecter, vous pouvez donc avoir un certain
- * contrôle et/ou mettre un mot de passe.
- * La syntaxe est la suivante :
- * allow {
- *    ip (ip mask à autoriser);
- *    hostname (host mask);
- *    class (classe à laquelle les renvoyer [voir class {}]);
- *    password "(mot de passe)"; (optionnel)
- *    maxperip (nombre de connexions par ip); (optionnel)
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* connexion autorisée avec mot de passe */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.passworded.ugly.people;
-	class           clients;
-	password "f00Ness";
-	maxperip 1;
-};
-
-/*
- * ACTUEL : oper {}
- * ANCIEN : O:Line
- * Définit un IRC Operateur
- * Les IRC operateurs sont là pour préserver la qualité du serveur mais aussi d'en assurer
- * la maintenance et sa connexion au réseau.
- * La syntaxe est la suivante :
- * oper (login) {
- *     class (classe à laquelle les associer, si différent du bloc allow, les déplace vers une nouvelle classe);
- *     from {
- *        userhost (ident@host);
- *        userhost (ident@host);
- *     };
- *     flags
- *     {
- *       (flags ici*);
- *     };
- *     OU
- *     flags "ancien type de flags, comme OAaRD";
- * };
- */
-
-
-/* Pour avoir la liste des flags oper, voir doc/unreal32docs.fr.html#operblock
- * [lecture HAUTEMENT recommendée]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * ACTUEL : listen {}
- * ANCIEN : P:Line
- * Définit un port à rattacher à l'ircd, pour autoriser
- * des utilisateurs/serveurs à se connecter au serveur.
- * La syntaxe est la suivante :
- * listen (ip):(port)
- * {
- *   options {
- *     (options ici);
- *   };
- * };
- * ou pour une écoute
- * indifférente : listen (ip):(port);
- *
- * NOTICE : pour les ips ipv6 (3ffe:b80:2:51d::2 etc), utilisez listen [ip]:port;
- *
- * Cela fonctionne également.
- */
-
-/* Options de listen:
-     ANCIEN	| 	ACTUEL
-	   S       serversonly
-	   C       clientsonly
-	   J       java
-	   s       ssl
-	   *       standard
-*/
-
-/* NOTE SUR LES PORTS SSL: les ports SSL sont plutôt non standardisés,
- * A côté des nombreux ports high-SSL, certaines personnes disent que vous devez
- * l'utiliser sur le port 994 car c'est le port SSL officiel.. mais cela
- * requière d'être root! D'un autre coté, le port 194 est le port irc officiel et
- * avez vous déjà vu un ircd fonctionner sur celui-ci ?
- * Donc, notre suggestion est d'utiliser le port 6697 pour le SSL, ceci est utilisé par
- * beaucoup de réseaux et est reconnu par exemple par StunTour.
- * Vous êtes libre d'ouvrir autant de ports SSL que vous le désirez mais
- * en utilisant (au moins) 6697 vous aidez le monde à se standardiser un peu ;).
- */
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* NOTE: Si vous êtes sur un shell avec de multiples IP vous êtes
- *       susceptibles d'avoir l'erreur 'Address already in use' (adresse déjà utilisée)
- *       dans vos logs et l'ircd refusera de démarer.
- *       Cela signifie que vous devrez utiliser une IP spécifique au lieu de '*',
- *       Donc par exemple :
- *       listen 1.2.3.4:6667;
- *       Evidemment, remplacez l'IP par celle qui vous a été assignée.
- */
-
-/*
- * ACTUEL : link {}
- * ANCIEN : C/N:Lines
- * Définit un accord pour la connexion d'un serveur.
- * NOTE : CHACUN DES SERVEURS NECESSITE UN PARAMETRE LINK {} POUR SE CONNECTER CORRECTEMENT !
- * La syntaxe est la suivante :
- * link (nom du serveur)
- * {
- *	username	(username, * fonctionne aussi);
- * 	hostname	(ip/hostmask);
- *	bind-ip		(IP à laquelle se relier lors de la connexion, ou *);
- *	port		(port auquel se connecter, si il y en a un);
- *	hub (Si c'est un a hub, * fonctionne, ou les servermasks qu'il doit porter);
- *	[ou leaf *;]
- *	password-connect "(mot de passe à envoyer)";
- *	password-receive "(mot de passe que l'on doit recevoir)";
- *	class		(classe à affecter aux serveurs);
- *	options {
- *		(options ici*);
- *	};
- *      // Si vous utilisez le SSL, vous pouvez choisir quel algorithme de hash utiliser dans le mode SSL
- *      // Utilisez la commande "openssl ciphers" pour obtenir la liste des algorithmes disponibles, séparez les par des ":"
- *
- *      ciphers "DES-CBC3-MD5";
- *
- * };
-*/
-
-/*
-	options:
-	ANCIEN	|	ACTUEL
-	S		    ssl
-	Z		    zip
-	N/A		    autoconnect
-	N/A		    quarantine
-	N/A		    nodnscache
-*/
-
-
-link            hub.mynet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Note : Vous ne devriez pas utiliser autoconnect lorsque vous linkez des services */
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * ACTUEL : ulines {}
- * ANCIEN : U:Line
- * Les U-lines donnent aux serveurs plus de pouvoir/commandes, ceci doit UNIQUEMENT être appliqué
- * aux serveurs de services/stats et JAMAIS pour des serveurs UnrealIRCd normaux !
- * La syntaxe est la suivante :
- * ulines {
- *	(serveur auquel appliquer la uline);
- *	(serveur auquel appliquer la uline);
- *  [etc]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * ACTUEL : drpass {}
- * ANCIEN : X:Line
- * Défini les mots de passe pour les commandes /die et /restart.
- * La syntaxe est la suivante :
- * drpass {
- *  restart		"(mot de passe pour relancer)";
- *  die		    "(mot de passe pour arrêter)";
- * };
- */
-drpass {
-	restart "I-love-to-restart";
-	die "die-you-stupid";
-};
-
-/*
- * ACTUEL : log {}
- * ANCIEN : N/A
- * Dit à l'ircd où et quoi loguer. Vous pouvez en avoir
- * autant que vous le souhaitez.
- *
- * FLAGS : errors, kills, tkl, connects, server-connects, oper
- *
- * Syntaxe :
- * log "fichier de log"
- * {
- *    flags
- *    {
- *        flag;
- *        flag;
- *        etc..
- *    };
- * };
- */
-
-log "ircd.log" {
-	/* Efface le fichier de log et commence un nouveau lorsqu'il dépasse 2MB,
-	   retirez ceci pour toujour utiliser le même fichier de log */
-	maxsize 2097152;
-	flags {
-		oper;
-		connects;
-		server-connects;
-		kills;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * ACTUEL : alias {}
- * ANCIEN : N/A
- * Ceci vous permet de définir des alias pour les commandes telles que /nickserv, /chanserv etc
- * FLAGS: services, stats, normal
- *
- * Syntaxe :
- * alias "nom" {
- *	target "pointe vers";
- *	type typedalias;
- * };
- *
- * [NOTE : Vous pouvez également inclure un fichier d'alias prédéfinis ici, voir
- * doc/unreal32docs.fr.html section 2.9]
- */
-
-// Ceci fait pointer la commande /nickserv vers l'utilisateur NickServ qui est connecté au serveur set::services-server
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Si vous voulez que la commande pointe vers le même nom que la commande, vous pouvez ignorez l'entré du nom
-//alias ChanServ { type services; };
-
-// Faire pointer la commande /statserv vers l'utilisateur StatServ sur le serveur set::stats-name
-//alias StatServ { type stats; };
-
-// Faire pointer la commande /superbot vers l'utilisateur SuperBot
-//alias SuperBot { type normal; };
-
-
-/* Alias Standards */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * ACTUEL : alias {}
- * ANCIEN : N/A
- * Ceci vous permet de définir des alias pour les commandes telles que /identify, /services, etc
- *
- * Syntaxe :
- * alias "nom" {
- *	format "format string" {
- *		target "pointer vers";
- *              type typedalias;
- *		parameters "paramètres à envoyer";
- *	};
- *	type command;
- * };
- */
-/* Ceci est expliqué séparément car même si elle a le même nom que la directive précédente, elle est très
- * différente dans sa syntaxe, bien qu'elle a une fonction similaire et dépend des alias standards pour
- * fonctionner.
- */
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-/* La directive alias::format est une expression régulière. Le premier format correspond à la commande
- * /identify command lorsque le premier caractère est un #. Cela renvoit donc à l'alias chanserv avec
- * les paramètres IDENTIFY %1-. Le second format correspond à la commande /identify lorsque le premier
- * caractère n'est pas un #. Cela envoie alors la commande à l'alias nickserv avec les paramètres
- * IDENTIFY %1-.
- */
-
-/* L'alias::format::parameters est similaire aux languages de programmation. %N (où N est un nombre)
- * représente un paramètre envoyé à la commande (dans ce cas /identify). Si vous spécifiez %N- cela
- * signifie que tous les paramètres depuis N jusqu'au dernier paramètre dans la chaîne de caractères.
- * Vous pouvez également spécifier %n qui est remplacé par le pseudo de l'utilisateur.
-*/
-
-/* Alias Standards */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-/* Ceci est un exemple de véritable alias de commande*/
-/* Ceci renvoye /GLINEBOT à /GLINE <parameter> 2d etc... */
-alias "glinebot" {
-         format ".+" {
-                 command "gline";
-                 type real;
-                 parameters "%1 2d Les bots ne sont pas permis sur ce serveur, lisez s'il-vous-plait la faq sur http://www.example.com/faq/123";
-         };
-         type command;
- };
-
-/*
- * ACTUEL : files {}
- * ANCIEN : include/config.h
- *
- * Ce bloc écrase les chemins utilisés par défaut par l'IRCd pour charger des choses
- * comme le MOTD, enregistrer son PID ou écrire ou lire son fichier de sauvegarde (tunefile).
- * L'existence de ce bloc permet à une installation de UnrealIRCd de supporter
- * plusieurs instances tournant simultanément lorsque combinée à l'option de ligne
- * de commande -c
- *
- * Comme d'habitude, les chemins relatifs sont interprétés à partir du répertoire
- * dans lequel UnrealIRCd trouverait unrealircd.conf si -c N'est PAS spécifiée
- * sur la ligne de commande.
- */
-files
-{
-	/* Le message du jour (Message Of The Day) affiché aux utilisateurs se connectant : */
-	/* motd ircd.motd; */
-
-	/*
-	 * Un MOTD court. Si ce fichier existe, il sera affiché aux
-	 * utilisateurs à la place du MOTD. Ceux-ci peuvent toujours voir
-	 * le MOTD complet en utilisant la commande /MOTD
-	 */
-	/* shortmotd ircd.smotd; */
-
-	/* Affiché lorsqu'un opérateur utilise /OPER */
-	/* opermotd oper.motd; */
-
-	/* MOTD des services. */
-	/* svsmotd ircd.svsmotd; */
-
-	/* MOTD des bots */
-	/* botmotd bot.motd; */
-
-	/* Affiché par la commande /RULES */
-	/* rules ircd.rules; */
-
-	/*
-	 * Fichier dans lequel l'IRCd sauvegarde et charge quelques valeurs qui devraient
-	 * être conservées malgré les redémarrages du serveur. Doit pointer vers un fichier
-	 * existant que l'IRCd peut modifier ou vers un fichier dans un dossier dans
-	 * lequel l'IRCd peut créer des fichiers.
-	 */
-	/* tunefile ircd.tune; */
-
-	/* Fichier dans lequel l'IRCd stocke son pid. L'IRCd doit pouvoir le modifier. */
-	/* pidfile ircd.pid; */
-};
-
-/*
- * ACTUEL : tld {}
- * ANCIEN : T:Line
- * Ceci applique un MOTD et des fichiers de règles différents
- * en fonction de l'hostmask des clients.
- * La syntaxe est la suivante :
- * tld {
- *    mask (ident@host);
- *    motd "(motd file)";
- *    rules "(rules file)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* Note : vous pouvez juste effacer le bloc d'exemple ci-dessus,
- * auquel cas les fichiers motd/règles par défaut (ircd.motd, ircd.rules)
- * seront utilisés pour tout le monde.
- */
-
-/*
- * ACTUEL : ban nick {}
- * ANCIEN : Q:Line
- * Bannit un pseudo, il ne peut donc être utilisé.
- * La syntaxe est la suivante :
- * ban nick {
- *	mask "(pseudo à bannir)";
- *	reason "(raison)";
- * };
-*/
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Reservé aux Services";
-};
-/*
- * ACTUEL : ban ip {}
- * ANCIEN : Z:Line
- * Empêche une ip de se connecter au réseau.
- * Syntaxe :
- * ban ip { mask (ip/hostmask); reason "(raison)"; };
-*/
-ban ip {
-	mask 195.86.232.81;
-	reason "Serveur délinké";
-};
-/*
- * ACTUEL : ban server {}
- * ANCIEN : Server Q:Line
- * Empêche un serveur de se connecter au réseau.
- * Si le serveur est linké à un serveur distant, le serveur local
- * sera déconnecté du réseau.
- * La syntaxe est la suivante :
- * ban server {
- *	mask "(nom du serveur)";
- *	reason "(raison à donner)";
- * };
-*/
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Va-t-en d'ici.";
-};
-/*
- * ACTUEL : ban user {}
- * ANCIEN : K:Line
- * Fait qu'un utilisateur avec un certain masque ne peut se connecter
- * à votre serveur.
- * Syntaxe :
- * ban user { mask (hostmask/ip); reason "(raison)"; };
-*/
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-    reason "Idiot";
-};
-
-/*
- * ACTUEL : ban realname {}
- * ANCIEN : n:Line
- * Ceci empêche un certain realname d'être utilisé.
- * Syntaxe :
- * ban realname {
- *	mask "(realname)";
- * 	reason "(raison)";
- * };
-*/
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * NOTE POUR TOUS LES BANS, ils peuvent être répetés pour ajouter des entrées !
- *
- * ACTUEL : except ban {}
- * ANCIEN : E:Line
- * Fait que vous ne pouvez être banni.
- * Syntaxe :
- * except ban { mask (ident@host); };
- * Répétez l'except ban {} autant de fois
- * que vous voulez pour différents hosts.
- */
-
-except ban {
-	/* ne bannit pas stskeeps */
-	mask           *stskeeps@212.*;
-};
-
-/*
- * ACTUEL : deny dcc {}
- * ANCIEN : dccdeny.conf
- * Utilisez ceci pour bloquer l'envoi de dcc ...
- * Utile pour bloquer les virus.
- * Syntaxe :
- * deny dcc
- * {
- *   filename "fichier à bloquer (ex : *exe)";
- *   reason "raison";
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Possible Sub7 Virus";
-};
-
-/*
- * ACTUEL : deny channel {}
- * ANCIEN : N/A (NEW)
- * Ceci empêche des salons d'être joints.
- * Syntaxe :
- * deny channel {
- * 	channel "(salon)";
- * 	reason "raison";
- * 	class "clients"; (optionnel)
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "Warez is illegal";
-	class "clients";
-};
-
-
-/*
- * ACTUEL : allow channel {}
- * ANCIEN : chrestrict
- * Autorise un utilisateur à joindre un salon...
- * comme une exception au deny channel.
- * Syntaxe :
- * allow channel {
- *   channel "nom du salon";
- *   class "clients"; (optionnel)
- * };
- */
-allow channel {
-	channel "#WarezSucks";
-	class "clients";
-};
-
-/*
- * ACTUEL : vhost {}
- * ANCIEN : Vhost.conf file
- * Applique une ip factice aux non-opers, ou aux
- * opers trop flemmards pour utiliser /sethost :P
- * Syntaxe :
- *   vhost {
- *       vhost (vhost.com);
- *       from {
- *            userhost (ident@host à autoriser à utiliser);
- *       };
- *       login (login);
- *       password (mot de passe);
- *   };
- *        ensuite pour utiliser ce vhost, tapez /vhost (login) (mot de passe) sur l'IRC
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Vous pouvez utiliser d'autres fichiers de configuration */
-/* include "klines.conf"; */
-
-/* Configuration du réseau */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 	"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix	"rox";
-	/* prefix-quit 		"no"; */
-	/* Les Cloak keys doivent être les mêmes sur tous les serveurs du réseau.
-	 * Ils sont utilisés pour générer des hosts masqués et doivent être gardés secrets.
-	 * Les clés doivent être 3 chaînes de 5-100 caractères melangés.
-	 * (10-20 caractères est parfait) et elles doivent être constituées de minuscules (a-z),
-	 * majuscules (A-Z) et chiffres (0-9) [voir le premier exemple de clé].
-	 * Astuce : Sur *NIX, vous pouvez utiliser la commande './unreal gencloak' dans votre shell pour que
-	 *       Unreal génère 3 chaînes aléatoires pour vous.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"et une autre";
-		"et un autre";
-	};
-	/* host à l'identification oper */
-	hosts {
-		local		"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin		"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 	"netadmin.roxnet.org";
-		host-on-oper-up "no";
-	};
-};
-
-/* Configuration spécifique d'un serveur */
-
-set {
-	kline-address "définir.cet.email";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#opers";
-	options {
-		hide-ulines;
-		/* Vous pouvez enclencher la vérification des idents si vous voulez */
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* Durée maximum pendant laquelle un utilisateur doit rester connecté avant de pouvoir utiliser
-	 * un message de QUIT.
-	 * Ceci devrait aider à stoper le spam */
-	anti-spam-quit-message-time 10s;
-	/* Applique le message de static-quit à tous les quits - cela signifie qu'aucun
-           message de quit personalisé ne sera autorisé sur le serveur local */
-	/* static-quit "Client quit";	*/
-
-	/* Vous pouvez également bloquer toutes les raisons de part en décommentant ceci et en disant
-	 * 'yes', ou spécifiez un autre texte (ex: "Bye bye!") pour qu'il soit toujours utilisé.. */
-	/* static-part yes; */
-
-	/* Vous permet de restreindre certaines stats aux opers, utilisez * pour toutes les stats,
-	 * enlevez le pour autoriser les utilisateurs à voir toutes les stats. Tapez '/stats' pour
-	 * une liste complète.
-	 * Certains admins pourront vouloir bloquer 'kGs' pour que les utilisateurs normaux ne puissent
-	 * lister les klines, glines et shuns.
-	 */
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Throttling: cet exemple applique une limite de 3 tentatives de connection en 60s (par host). */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Protection Anti flood */
-	anti-flood {
-		nick-flood 3:60;	/* 3 changements de pseudo en 60 secondes (la valeur par défaut) */
-	};
-
-	/* Filtre anti-spam */
-	spamfilter {
-		ban-time 1d; /* durée par défaut d'un ban *line appliqué par le spamfilter */
-		ban-reason "Spam/Advertising"; /* raison par défaut */
-		virus-help-channel "#help"; /* salon à utiliser pour l'action 'viruschan' */
-		/* excepté "#help"; salon à exempter de filtrage */
-	};
-};
-
-/*
- * Problèmes ou besoin de plus d'aide ?
- * 1) http://www.unrealircd.com/files/docs/unreal32docs.fr.html
- * 2) http://www.vulnscan.org/UnrealIRCd/faq/ <- contient 80% de vos questions !
- * 3) Si vous avez encore des problèmes vous pouvez aller sur irc.unrealircd.org #unreal-support,
- *    notez que vous devez avoir LU LA DOCUMENTATION ET LA FAQ d'abord !
- */

doc/example.hu.conf

@@ -1,875 +0,0 @@
-/*
- * example.conf Daniel Hawton avagy Osiris jóvoltából (osiris@unrealircd.org).
- * A magyar fordítást AngryWolf <angrywolf2009@gmail.com> készítette.
- * $Id$
- * 
- * Felhasználható Unreal3.2.x
- * 
- * Oké, emberek! Ez az új példa konfiguráció. A kinézete nagyon hasonló
- * a C++-hoz, olyasformán. Mindenesetre itt az ideje végigmennünk rajta. Eleinte
- * nehéz nekilendülni, de kis gyakorlással és olvasgatással meg fogjuk érteni.
- *
- * Csak másoljuk be ezt a fájlt a fő unrealircd könyvtárunkba, és nevezzük
- * 'unrealircd.conf'-nak.
- * 
- * MEGJEGYZÉS:  Minden sor, kivéve a nyitó { sort, ;-vel végződik, beleértve
- * a záró } sort is. Az IRCd figyelmen kívül hagyja a megjegyzéssorokat.
- *
- * KÉRLEK, OLVASD EL A doc/unreal32docs.html-T! Az online verzió is elérhető
- * a www.vulnscan.org/UnrealIRCd/unreal32docs.html címen.
- * Rengeteg információt tartalmaz a konfigurációs fájlról: tájékoztatást ad
- * minden blokkról, változóról stb.
- * Ha megpróbálod szerkeszteni ezt a fájlt anélkül, hogy megfelelően elolvastad
- * volna a dokumentációt, jó eséllyel kanyarodsz a biztos kudarc felé!
- */
-
-/* Megjegyzések típusai */
-#1. Megjegyzéstípus (Shell típusú)
-// 2. Megjegyzéstípus (C++ stílusú)
-/* 3. Megjegyzéstípus (C stílusú) */
-#ezeket a sorokat az ircd figyelmen kívül hagyja.
-
-/*
- * Az UnrealIRCd támogat modulokat, néhányuk betöltése kötelező is.
- * Legalább a parancsokat biztosító és egy álcázó modulra lesz szükségünk.
- */
-
-/* *NIX-BAN vegyük ki a megjegyzésből a következő két sort: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* Windows-BAN vegyük ki a megjegyzésből a következő két sort: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Azt is megtehetjük, hogy befűzünk más konfigurációs fájlokat.
- * A help.conf tartalmazza az összes /helpop szöveget. A badwords.*.conf
- * fájlok tartalmazzák az összes csúnyaszó bejegyzést a +G módhoz...
- * A spamfilter.conf néhány jó szabályt a jelenlegi trójai vírusokra.
- * Valószínűleg be akarjuk tölteni őket:
- */
-include "help.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * ÚJ:   me {} 
- * RÉGI: M:Line 
- * A me {} határozza meg ennek a szervernek a nevét, a leírását és az unrealbeli
- * szerverazonosító-számát. A szintaktikája a következő: 
- * me { 
- *  name "szerver.név"; 
- *  info "A szerver leírása";
- *  numeric (szerverazonosító*);
- * }; 
- * Ha linkelünk, ezt az azonosítószámot nem használhatja semmilyen más szerver
- * a hálózaton.
- */
-me
-{
-	name "irc.valaminet.com";
-	info "ValamiNet Szerver";
-	numeric 1;
-};
-
-/*
- * ÚJ:   admin {} 
- * RÉGI: A:Line
- * Ez a blokk információt ad a szerver adminisztrátorairól. Annyi sort tehetünk
- * az admin { alá, amennyit kívánunk. 
- * A szintaktikája a következő:
- * admin {
- *   "első sor"; 
- *   "második sor"; 
- *   [stb]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"szeleskorben@hasznalt.nev";
-};
-
-/*
- * ÚJ:   class {} 
- * RÉGI: Y:line (a régi zavarbaejtő volt) 
- * Ezek az osztályokat állítják be. Az osztályok a kapcsolatok egy csoportjának
- * beállításai. Például a szerver kapcsolatokat, ahelyett, hogy egy kliens
- * osztályába kerülnének, beleirányítjuk a szerverek osztályába. Szintaktika:
- * class (osztálynév)
- * {
- *     pingfreq (hány másodpercenként pingeljünk egy felhasználót/szervert);
- *     maxclients (mennyi kapcsolat lehet ebben az osztályban);
- *     sendq (egy kapcsolat küldési sorának maximális mérete);
- *     recvq (egy kapcsolat fogadási sorának maximális mérete [árvízvédelem]);
- *  };
- */
-
-class           clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class           servers
-{
-	pingfreq 90;
-	maxclients 10;	/* Legfeljebb ennyi szervert linkelhetünk egyszerre */
-	sendq 1000000;
-	connfreq 100; /* Ennyi másodpercet várjon, mielőtt újra kapcsolódik */
-};
-
-/*
- * ÚJ:   allow {} 
- * RÉGI: I:Line
- * Ez a kapcsolatok engedélyezését határozza meg...
- * Alapvetően kliensekre használjuk; megengedi nekik, hogy kapcsolódjanak, így
- * némileg van lehetőség a szabályozásra, valamint jelszót is beállíthatunk. 
- * A szintaktika a következő: 
- * allow {
- *    ip (ip maszk az engedélyezéshez);
- *    hostname (gazdanév maszk);
- *    class (osztály, ahová küldjük őket [lásd: class {}]);
- *    password "(jelszó)"; (nem kötelező)
- *    maxperip (mennyi kapcsolatot engedjünk ip címenként); (nem kötelező) 
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* Jelszavas allow blokk */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.jelszavas.csunya.emberkek;
-	class           clients;
-	password "V4lami";
-	maxperip 1;
-};
-
-/*
- * ÚJ:   allow channel {} 
- * RÉGI: chrestrict 
- * Megengedi egy felhasználónak, hogy belépjen egy csatornára...
- * mint egy csatornáról letiltás alóli kivétel. 
- * Szintaktika:
- * allow channel {
- *   channel "csatornanév";
- *   class "clients"; (nem kötelező)
- * };
- */
-allow channel {
-	channel "#AWarezSzívás";
-	class "clients";
-};
-
-/*
- * ÚJ:   oper {} 
- * RÉGI: O:Line 
- * Definiál egy IRC operátort
- * Az IRC operátorok feladata, hogy épségben tartsák a szervert; rendszerint
- * ügyelnek a karbantartottságára és arra, hogy kapcsolatban maradjon
- * a hálózattal. A szintaktika a következő: 
- * oper (bejelentkezőnév) { 
- *     class (osztály, ahová berakjuk őket; ha eddig más osztályban voltak,
- *                átteszi őket ebbe az új osztályba); 
- *     from { 
- *        userhost (azonosító@gazdanév);
- *        userhost (azonosító@gazdanév);
- *     }; 
- *     flags
- *     { 
- *       (flagek ide*);
- *     };
- *     VAGY
- *     flags "régi típusú flagek, mint pl. OAaRD";
- * };
- */
-
-
-/* Az oper flagek listáját lásd a doc/unreal32docs.hu.html#operblock szekcióban
- * [ERŐSEN ajánlott elolvasni]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * ÚJ:   listen {}
- * RÉGI: P:Line
- * Meghatároz egy olyan portot, amelyet az ircd megnyit, és engedélyt ad
- * a felhasználóknak/szervereknek, hogy kapcsolódjanak a szerverre.
- * A szintaktika a  következő:
- * listen (ip cím):(portszám) 
- * { 
- *   options {
- *     (opciók ide);
- *   };
- * };
- * vagy egy síma portnyitáshoz:
- * listen (ip):(port);
- * 
- * MEGJEGYZÉS: ipv6-os ip-kre (3ffe:b80:2:51d::2 stb.) használjuk a
- * listen [ip]:port;
- * szintaktikát. Az is működik.
- */
-
-/* Opciók a listenhez:
-	RÉGI	| 	ÚJ
-	S		serversonly
-	C		clientsonly
-	J		java
-	s		ssl
-	*		standard
-*/
-
-/* MEGJEGYZÉS SSL PORTOKRA: az SSL portok eléggé szabványosítatlanok, emellett
- * sok a magas SSL port. Néhányan azt mondják, a 994-en célszerű futtatni,
- * mert az a hivatalos SSL port... de a rendszergazdát igényel! Ezenkívül,
- * a 194 a hivatalos irc port, de láttunk valaha egy ircd-t azon futni?
- * Így mi a javaslatunk az, hogy használjuk a 6697-et SSL-hez, ezt használja
- * jónéhány hálózat, és ezt ismeri fel például a StunTour is.
- * Szabadon megnyithatunk annyi SSL portot, amennyit akarunk, de ha a 6697-et
- * (is) használjuk, kicsit segítjük a világot szabványosodni ;).
- */
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* MEGJEGYZÉS: Ha egy több IP címes IRCd shellen vagyunk, előfordulhat, hogy
- *       "Address already in use" ("A cím már használatban van") hibaüzeneteket
- *       találunk a naplóban, és az ircd nem indul el. Ez azt jelenti, hogy
- *       az ircd-nek egy meghatározott IP címre KELL bindelnie a "*" helyett
- *       vagyis például így:
- *       listen 1.2.3.4:6667;
- *       Természetesen cseréljük ki az IP címet arra az IP-re, amelyet nekünk
- *       osztottak ki.
- */
-
-/*
- * ÚJ:   link {}
- * RÉGI: C/N:Line-ok
- * Ez a blokk "igen"-t mond egy szerver kapcsolódására.
- * MEGJEGYZÉS: MINDKÉRT SZERVEREN KELL EGY LINK {} BEÁLLÍTÁS A HELYES
- *             KAPCSOLÓDÁSHOZ!
- * A szintaktika a következő:
- * link (szervernév)
- * {
- *	username	(felhasználónév, * is működik);
- * 	hostname	(ip cím/gazdanév maszk);
- *	bind-ip		(amilyen IP címre bindeljen kapcsolódáskor, vagy *);
- *	port		(port, ahová kapcsolódjon, ha van);
- *	hub (Ha ez egy hub; * működik, vagy szervermaszkokat is beírhatunk);
- *	[vagy leaf *;]
- *	password-connect "(elküldendő jelszó)";
- *	password-receive "(fogadandó jelszó)";
- *	class		(osztály, ahová betesszük a szervereket);
- *	options {
- *		(opciók ide*);
- *	};
- *      // Ha SSL-t használunk, kiválaszthatjuk, milyen rejtjelező algoritmusok
- *      // legyenek használatban SSL módban. Listát kapunk az "openssl ciphers"
- *      // paranccsal. Az egyes algoritmusokat :-tal válasszuk el.
- *
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-	opciók:
-	RÉGI	|	ÚJ
-	S		ssl
-	Z		zip
-	N/A		autoconnect
-	N/A		quarantine
-	N/A		nodnscache
-*/
-
-
-link            hub.sajatnet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Megjegyzés: szolgáltatások linkelésekor célszerű nem
-			 * használni az autoconnect opciót.
-			 */
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * ÚJ:   ulines {}
- * RÉGI: U:Line
- * Az U-line-ok több hatalmat/parancsot adnak a szervereknek. CSAK
- * szolgáltatásokat és statisztikákat nyújtó szerverekre érdemes beállítani,
- * és SOHA rendes UnrealIRCd szerverekre!
- * A szintaktika a következő:
- * ulines {
- *	(uline-ra teendő szerver);
- *	(uline-ra teendő szerver);
- *  [stb.]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * ÚJ:   drpass {}
- * RÉGI: X:Line
- * Meghatározza a jelszavakat a /die és /restart parancsokhoz.
- * A szintaktika a következő:
- * drpass { 
- *  restart		"(újraindítás jelszava)";
- *  die		        "(leállítás jelszava)";
- * };
- */
-drpass {
-	restart "Imádok-újraindítani";
-	die "Halj-te-buta";
-};
-
-/*
- * ÚJ:   log {}
- * RÉGI: N/A
- * Megmondja az ircd-nek, hová és mit naplózzon. Annyi naplófájlunk lehet,
- * amennyit szeretnénk.
- * 
- * FLAGEK: errors, kills, tkl, connects, server-connects, oper
- * 
- * Szintaktika: 
- * log "naplófájl" 
- * {
- *    flags
- *    {
- *        (flag);
- *        (flag); 
- *        [stb.] 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-	/* Törölje a naplófájlt, és kezdjen egy újat, ha eléri a 2 MB-ot;
-	 * hagyjuk ki ezt a beállításból, ha mindig ugyanazt a naplót
-	 * szeretnénk használni
-	 */
-	maxsize 2097152;
-	flags {
-		oper;
-		connects;
-		server-connects;
-		kills;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * ÚJ:   alias {}
- * RÉGI: N/A
- * Ezzel olyan álparancsokat készíthetünk, mint a /nickserv, /chanserv stb.
- * FLAGEK: services (szolgáltatás), stats (statisztika), normal (közönséges
- *         felhasználó)
- *
- * Szintaxis:
- * alias "név" {
- *	target "ahová mutasson";
- *	type álparancstípus;
- * };
- *
- * [MEGJEGYZÉS: Beilleszthetünk ide egy előre beállított álparancsfájlt is,
- *              lásd: doc/unreal32docs.html, 2.9-es szekció]
- */
-
-// Ez a /nickserv parancsot a NickServ felhasználóra irányítja, aki a set::services-server szerverre kapcsolódott.
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Ha a parancsot ugyanarra a nicknévre szeretnénk irányítani, ami a parancs neve, kihagyhatjuk a nick bejegyzést.
-//alias ChanServ { type services; };
-
-// A /statserv parancsot a set::stats-server szerveren lévő StatServ felhasználóra irányítja
-//alias StatServ { type stats; };
-
-// A /superbot parancsot a SuperBot felhasználóra irányítja.
-//alias SuperBot { type normal; };
-
-
-/* Szabványos álparancsok */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * ÚJ:   alias {}
- * RÉGI: N/A
- * Ezzel olyan álparancsokat készíthetünk, mint az /identify, /services stb.
- *
- * Szintaktika:
- * alias "név" {
- *	format "formátumsztring" {
- *		target "ahova mutasson";
- *              type álparancstípus;
- *		parameters "küldendő paraméterek";
- *	};
- *	type command;
- * };
- */
-/* Ezt azért mutatjuk külön, mert még ha ugyanaz is a neve, mint az előző direktívának, a szintaktikája nagyon
- * más, habár hasonló feladatot lát el, és a szabványosok álparancsokra van szüksége, hogy működjön.
- */
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-/* Az alias::format direktíva egy reguláris kifejezés. Az első formátum akkor illeszkedik az /identify parancsra,
- * ha az első karakter egy #. Azután elküldi ezt a chanserv álparancshoz az IDENTIFY %1- paraméterekkel.
- * A második formátum akkor illeszkedik az /identify parancsra, ha az első karakter nem egy #. Azután
- * elküldi a parancsot a nickserv álparancshoz az IDENTIFY %1- paraméterekkel.
- */
-
-/* Az alias::format::parameters hasonló a scriptnyelvekhez. Az %N (ahol N egy szám) a parancshoz küldött egyik
- * paramétert ábrázolja (ebben az esetben az /identify-ét). Ha azt írjuk, hogy %N-, a sztring N-edik
- * paraméterétől az utolsóig minden paramétert fog jelenteni. Megadhatunk egy %n-et is, amely ki lesz cserélve
- * a felhasználó nicknevével.
-*/
-
-/* Szabványos álparancsok */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-/* Példa egy valódi álparancsra */
-/* A /GLINEBOT parancsot leképezi arra, hogy /GLINE <paraméter> 2d stb... */
-alias "glinebot" {
-	format ".+" {
-		command "gline";
-		type real;
-		parameters "%1 2d Botok tilosak ezen a szerveren, kérlek, olvasd el a faq-ot a http://www.example.com/faq/123 címen";
-	};
-	type command;
-};
-
-/*
- * ÚJ:   files {}
- * RÉGI: include/config.h
- *
- * Ez a blokk felülírja az IRCd alapértelmezett útvonalait olyan fájlok
- * betöltésére, mint az MOTD, PID fájl mentése vagy a behangoló fájl
- * írása/olvasása. Ennek a blokknak a jelenléte támogatást ad arra, hogy
- * egyetlen telepített UnrealIRCd-nek több példányát futtassuk, amikor
- * a -c parancssori opcióval párosítjuk.
- *
- * Ahogy megszoktuk, a relatív útvonalak ahhoz a könyvtárhoz relatívan
- * értendőek, ahol az UnrealIRCd megtalálja az unrealircd.conf fájlt,
- * hacsak nem a -c paramétert megadjuk a parancssorban.
- */
-files
-{
-	/* A Nap Üzenete (Message Of The Day), elküldve a belépett felhasználóknak: */
-	/* motd ircd.motd; */
-
-	/*
-	 * Egy rövid MOTD (short MOTD). Ha létezik ez a fájl, ezt a fájlt
-	 * fogják látni a felhasználók az MOTD helyett. A teljes MOTD-t
-	 * továbbra is megnézhetik az /MOTD parancs használatával.
-	 */
-	/* shortmotd ircd.smotd; */
-
-	/* Megjelenik, ha egy operátor bejelentkezik (/OPER) */
-	/* opermotd oper.motd; */
-
-	/* MOTD hozzáfűzés a szolgáltatásoknak. */
-	/* svsmotd ircd.svsmotd; */
-
-	/* Bot MOTD */
-	/* botmotd bot.motd; */
-
-	/* Megjelenik a /RULES parancsra */
-	/* rules ircd.rules; */
-
-	/*
-	 * Itt tárol és innen tölt be az IRCd néhány olyan értéket, amelyet
-	 * minden szerverújraindítás során meg kell őriznie. Egy olyan fájlra
-	 * kell, hogy mutasson, amely létezik, és az IRCd-nek van módosítási joga,
-	 * vagy pedig olyan könyvtárban van, ahol az IRCd-nek van fájllétrehozási joga.
-	 */
-	/* tunefile ircd.tune; */
-
-	/* Ide mentjük az IRCd PID fájlját. Az IRCd számára írhatónak kell lennie. */
-	/* pidfile ircd.pid; */
-};
-
-/*
- * ÚJ:   tld {}
- * RÉGI: T:Line
- * Beállít más motd és rules fájlt
- * a kliens hostmaszkjára.
- * A szintaktikája a következő: 
- * tld {
- *    mask (azonosító@gazda);
- *    motd "(motd fájl)";
- *    rules "(rules fájl)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* megjegyzés: a fenti példa blokkot akár le is törölhetjük; ebben az esetben
- * mindenkire az alapértelmezett motd/rules fájlok (ircd.motd, ircd.rules)
- * lesznek használatban.
- */
-
-/*
- * ÚJ:   ban nick {}
- * RÉGI: Q:Line
- * Kitilt egy nicknevet, így az nem használható.
- * A szintaktikája a következő:
- * ban nick {
- *	mask "(kitiltandó nick)";
- *	reason "(indoklás)";
- * };
-*/
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Fenntartva a szolgáltatásoknak";
-};
-/*
- * ÚJ:   ban ip {}
- * RÉGI: Z:Line
- * Megtiltja egy ip-nek, hogy a hálózatra kapcsolódjon.
- * Szintaktika:
- * ban ip { mask (ip cím/gazdanévmaszk); reason "(indoklás)"; };
-*/
-ban ip {
-	mask 195.86.232.81;
-	reason "Lecsatolt szerver";
-};
-/*
- * ÚJ:   ban server {}
- * RÉGI: Q:Line szerverekre
- * Megtiltja egy szervernek, hogy a hálózatra kapcsolódjon.
- * Ha egy szerver távoli szerverre linkel, a helyi szerver
- * szétkapcsolja a hálózatról.
- * A szintaktikája a következő:
- * ban server {
- *	mask "(szervernév)";
- *	reason "(indoklás)";
- * };
-*/
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Mars ki innen!";
-};
-/*
- * ÚJ:   ban user {}
- * RÉGI: K:Line
- * Elintézi, hogy egy felhasználó egy bizonyos maszkról ne tudjon kapcsolódni
- * a szerverünkre.
- * Szintaktika:
- * ban user { mask (gazdanévmaszk/ip cím); reason "(indok)"; };
-*/
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-        reason "Idióta";
-};
-
-/*
- * ÚJ:   ban realname {}
- * RÉGI: n:Line
- * Letiltja egy bizonyos valós név használatát.
- * Szintaktikája:
- * ban realname {
- *	mask "(valós név)";
- * 	reason "(indok)";
- * };
-*/
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * MEGJEGYZÉS MINDEN BANRA: ezek ismételhetőek további bejegyzésekhez!
- * 
- * ÚJ:   except ban {} 
- * RÉGI: E:Line
- * Elintézi, hogy ne lehessen minket kibannolni. 
- * Szintaktika:
- * except ban { mask (azonosító@gazda); };
- * További gazdákhoz annyiszor ismételjük az except ban {}-t,
- * amennyiszer szükséges.
- */
-
-except ban {
-	/* ne tiltsuk ki stskeeps-t */
-	mask           *stskeeps@212.*;
-};
-
-/*
- * ÚJ:   deny dcc {} 
- * RÉGI: dccdeny.conf
- * Használjuk dcc küldések blokkolására... Jobban
- * megállítja a vírusokat. 
- * Szintaktika: 
- * deny dcc 
- * { 
- *   filename "blokkolandó fájl (pl. *exe)";
- *   reason "indok";
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Valószínűleg Sub7 Virus";
-};
-
-/*
- * ÚJ:   deny channel {}
- * RÉGI: N/A (ÚJ)
- * Letiltja bizonyos csatornákon a belépést.
- * Szintaktika:
- * deny channel {
- * 	channel "(csatorna)";
- * 	reason "indok";
- *      class "clients"; (nem kötelező)
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "A warez törvényellenes";
-	class "clients";
-};
-
-/*
- * ÚJ:   vhost {}
- * RÉGI: Vhost.conf fájl
- * Beállít egy hamis ip címet közönséges felhasználókon, vagy
- * olyan operátorokon, akik lusták a /sethost-ot használni :P
- * Szintaktika:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (azonosító@gazda, aki használhatja);
- *       };
- *       login (bejelentkezőnév);
- *       password (jelszó);
- *   };
- *        azután e vhost használatához adjuk ki
- *        a /vhost (bejelentkezőnév) (jelszó) parancsot IRC-n
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Befűzhetünk más konfigurációs fájlokat */
-/* include "klines.conf"; */
-
-/* Hálózati beállítások */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 	"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix	"rox";
-	/* prefix-quit 		"no"; */
-	/* Az álcázó kulcsoknak a hálózat minden szerverén azonosnak kell
-	 * lenniük. Az álcázott gazdanevek előállításában van szerepük, ezért
-	 * legyenek titokban tartva! Mind 3 kulcs legyen egy-egy véletlenszerű
-	 * sztring 5-100 karakterből (10-20 karakter kitűnő), valamint
-	 * tartalmazniuk kell kisbetűket (a-z), nagybetűket (A-Z) és számokat
-	 * (0-9) [ahogy az első kulcsos példában látható].
-	 * TIPP: *NIX alatt az './unreal gencloak' parancsot futtatva
-         *       a parancsértelmezőnkben, az Unreal 3 véletlen sztringet
-         *       generál nekünk.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"írjunk hozzá még egyet";
-		"írjunk hozzá még egyet";
-	};
-	/* gazdanevek opereléskor */
-	hosts {
-		local		"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin		"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 	"netadmin.roxnet.org";
-		host-on-oper-up "no";
-	};
-};
-
-/* Szerverszintű beállítások */
-
-set {
-	kline-address "állítsuk.be.ezt.az.emailt";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#operek";
-	options {
-		hide-ulines;
-		/* Itt engedélyezhetjük az ident ellenőrzést, ha szeretnénk */
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* Legkevesebb ennyi ideig kell a felhasználónak kapcsolatban lennie,
-	 * mielőtt engedélyt kap a QUIT üzenetek használatára. Remélhetőleg
-	 * ez leállítja a spamot. */
-	anti-spam-quit-message-time 10s;
-	/* A static-quit a neki megadott üzenetet megjeleníti minden
-	 * kilépésben - avagy egyéni kilépési szövegek nem engedélyezettek
-	 * a helyi szerveren */
-	/* static-quit "Kliens kilépés";	*/
-
-	/* Hasonlóan blokkolható minden lelépési indok, úgy, hogy kivesszük
-	 * a megjegyzésből ezt, és "yes"-t írunk vagy megadunk valamilyen
-	 * más szöveget (pl. "Bye bye!"), hogy mindig az legyen a lelépés
-	 * indoklószövege. */
-	/* static-part yes; */
-
-	/* Ezzel megmondhatjuk, mely statisztikákat szeretnénk csak operátorok
-	 * számára engedélyezni. Használjunk *-ot, ha az összeset kívánjuk,
-	 * és hagyjuk el a direktívát, ha a felhasználók mindet láthatják. Írjuk
-	 * be a "/stats" parancsot a teljes listáért.
-	 * Lehet, hogy néhány adminisztrátor törölni fogja a "kGs"-t, hogy
-	 a közönséges felhasználók láthassák a kline-okat, gline-okat és
-	 * shunokat.
-	 */
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Elfojtás: ez a példa 60 másodpercenként legfeljebb 3 kapcsolódási
-	 * kísérletet engedélyező korlátozást állít be (gazdánként). */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Árasztásellenes védelem */
-	anti-flood {
-		nick-flood 3:60;	/* 3 nicknévváltás 60 másodpercenként
-		            		   (az alapértelmezés) */
-	};
-
-	/* Spamszűrő */
-	spamfilter {
-		ban-time 1d; /* a spamszűrő által beállított *line-ok
-		                alapértelmezett kitiltási ideje */
-		ban-reason "Spam/Reklámozás"; /* alapértelmezett indok */
-		virus-help-channel "#help"; /* a "viruschan" tevékenységhez
-		                               használt csatorna */
-		/* except "#help"; kivesszük a szűrés alól ezt a csatornát */
-	};
-};
-
-/*
- * Problémák akadtak, vagy szükség van további segítségre?
- * 1) www.vulnscan.org/UnrealIRCd/unreal32docs.html
- * 2) www.vulnscan.org/UnrealIRCd/faq/ <- a kérdéseid 80%-át tartalmazza!
- * 3) Ha még mindig gondod van, felmehetsz az irc.unrealircd.org #unreal-support
- *    csatornájára. Fontos: kérjük, hogy előbb OLVASD EL A DOKUMENTÁCIÓT és
- *    a GYIK-ot!
- */

doc/example.nl.conf

@@ -1,816 +0,0 @@
-/*
- * example.conf door Daniel Hawton AKA Osiris (osiris@unrealircd.org).
- * $Id$
- * Vertaald door Mark
- * 
- * Werkt voor Unreal3.2.x
- * 
- * Dit is de nieuwe example.conf. Het lijkt veel op C++.
- * Het begin is wellicht moeilijk, maar met wat ervaring en lezen
- * zul je het wel begrijpen.
- *
- * Kopieer dit bestand naar je hoofd UnrealIRCd dir en noem het 'unrealircd.conf'.
- * 
- * OPMERKING: Alle regels, behalve de openings { regel, eindingen met een ;, dus
- * ook de sluitende } regel. Commentaar regels worden door de IRCd niet verwerkt.
- *
- * LEES doc/unreal32docs.html! De online versie is tevens te bereiken op:
- * www.vulnscan.org/UnrealIRCd/unreal32docs.html
- * Er staat heel veel informatie in over het configbestand: informatie over
- * elk block, variabele, etc..
- * Wanneer je dit bestand aanpast zonder de documentatie grondig te lezen,
- * zul je gegarandeerd falen!
- */
-
-/* Type van commentaar */
-#Commentaar type 1 (Shell type)
-// Commentaar type 2(C++ style)
-/* Commentaar type 3 (C Style) */
-#Deze regels worden niet verwerkt door de IRCd.
-
-/*
- * UnrealIRCd ondersteunt modules, het laden van sommige is benodigd.
- * Je hebt tenminste een commands module en een cloacking module nodig.
- */
-
-/* VOOR *NIX, haal de commentaartekens weg bij de volgende 2 regels: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* VOOR Windows, haal de commentaartekens weg bij de volgende 2 regels: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Je kan tevens andere configuratiebestanden toevoegen.
- * help.conf bevat alle /helpop tekst. De badwords.*.conf
- * bestanden bevatten alle badword instellingen voor mode +G..
- * spamfilter.conf bevat enkele goede regels voor huidige trojans.
- * Je wilt deze waarschijnlijk laden:
- */
- 
-include "help.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * NIEUW: me {} 
- * OUD: M:Line 
- * me {} definieert de naam, beschrijving en unreal numeriek voor deze server.
- * De syntax is als volgt:
- * me { 
- *  name "server.naam"; 
- *  info "Server Beschrijving";
- *  numeric (server numeric*);
- * }; 
- * Waneer je servers linkt, mag de numeric niet door een andere server in gebruik zijn.
- */
-me
-{
-	name "irc.foonet.com";
-	info "FooNet Server";
-	numeric 1;
-};
-
-/*
- * NIEUW: admin {} 
- * OUD: A:Line
- * Admin geeft informatie over de server admin. Je mag hier
- * zo veel regels opgeven als je wilt.
- * De syntax is als volgt:
- * admin {
- *   "eerste regel"; 
- *   "tweede regel"; 
- *   [etc]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"widely@used.name";
-};
-
-/*
- * NIEUW: class {} 
- * OUD: Y:line (de oude was verwarrend) 
- * Hiermee stel je de classes in. Een class is een groepsinstelling voor
- * connections. Server connecties stuur je naar een andere class dan
- * gebruikers.
- * De syntax is als volgt:
- * class (class naam)
- * {
- *     pingfreq (hoe vaak er gepingt moet worden naar een gebruiker/server in seconden);
- *     maxclients (hoeveel connecties er maximaal in deze class mogen zijn);
- *     sendq (maximale send queue voor 1 connectie);
- *     recvq (maximale receive queue voor 1 connectie [flood control]);
- *  };
- */
-
-class           clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class           servers
-{
-	pingfreq 90;
-	maxclients 10;		/* Hoeveel servers we maximaal tegelijk gelinkt kunnen hebben */
-	sendq 1000000;
-	connfreq 100; /* Hoeveel seconden tussen een poging to verbinden */
-};
-
-/*
- * NIEUW: allow {} 
- * OUD: I:Line
- * Hiermee stel je het toestaan van connecties in.
- * Gebruikers kunnen verbinden, en jij hebt wat controle en kan eventueel
- * een wachtwoord instellen.
- * De syntax is als volgt: 
- * allow {
- *    ip (ip mask dat toegestaan moet worden);
- *    hostname (host mask);
- *    class (class waarnaar ze gestuurd moeten worden [see class {}]);
- *    password "(wachtwoord)"; (optioneel)
- *    maxperip (hoeveel connecties per IP); (optioneel) 
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* Allow met wachtwoord */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.passworded.ugly.people;
-	class           clients;
-	password "f00Ness";
-	maxperip 1;
-};
-
-/*
- * NIEUW: allow channel {} 
- * OUD: chrestrict 
- * Geeft de mogelijkheid een kanaal te joinen,
- * als uitzondering voor een deny channel {}
- * De syntax is als volgt:
- * allow channel {
- *   channel "kanaal naam";
- * };
- */
-allow           channel {
-	channel "#WarezSucks";
-};
-
-/*
- * NIEUW: oper {} 
- * OUD: O:Line 
- * Stelt een IRC Operator in
- * IRC Operators zorgen voor orde op de server en zorgen er
- * tevens voor dat de server verbonden blijft met het netwerk.
- * De syntax is als volgt: 
- * oper (login) { 
- *     class (class waarin ze geplaatst moeten worden.); 
- *     from { 
- *        userhost (ident@host);
- *        userhost (ident@host);
- *     }; 
- *     flags
- *     { 
- *       (flags hier*);
- *     };
- *     OF
- *     flags "oud type flags, zoals OAaRD";
- * };
- */
-
-
-/* Voor een lange lijst van oper flags, zie doc/unreal32docs.html#operblock
- * [wordt ten zeerste aangeraden te lezen!]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * NIEUW: listen {}
- * OUD: P:Line
- * Hiermee stel je een poort in voor de IRCd, zodat
- * gebruikers/servers kunnen verbinden met je server.
- * De syntax is als volgt:
- * listen (ip nummer):(port nummer)
- * { 
- *   options {
- *     (opties hier);
- *   };
- * };
- * of een gewone:
- * listen: listen (ip):(port);
- * 
- * OPMERKING: voor IPv6 IPs (3ffe:b80:2:51d::2 etc), gebruik listen [ip]:port;
- * 
- * Dat werkt ook.
- */
-
-/* Opties voor listen:
-	OUD	| 	NIEUW
-	S		serversonly
-	C		clientsonly
-	J		java
-	s		ssl
-	*		standard
-*/
-
-
-/* Opmerking voor SSL poorten: SSL poorten zijn niet echt
- * standaard. Mensen zeggen dat je SSL op poort 994 moet laten
- * lopen, omdat dit de standaard SSL poort is.. Maar meestal worden
- * hogere poorten gebruikt. Om poort 994 te gebruiken, moet je root
- * zijn! Tevens is poort 194 de officiele IRC poort. Maar heb je daar
- * ooit een IRCd op zien lopen?
- * Wij raden je aan om poort 6697 voor SSL te gebruiken. Dit wordt op
- * vrijwel alle netwerken gebruikt en wordt herkend door bijvoorbeeld
- * StunTour. Je mag zoveel SSL poorten openen als je wil, maar als je
- * (tevens) 6697 gebruikt, help je mee de wereld meer uniform te maken ;).
- */
- 
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-
-/* Opmerking: Als je een IRCd shell gebruikt met meerdere IPs, krijg
- *            je wellicht een "Address already in use" error in je log
- *            en de IRCd zal niet starten. Dit betekent dat je MOET binden
- *            naar een specifiek IP in plaats van '*', bijvoorbeeld:
- *            listen 1.2.3.4:6667l
- *            Natuurlijk moet je het IP vervangen door het IP dat je toewezen is.
- */
- 
-/*
- * NIEUW: link {}
- * OUD: C/N:Lines
- * Geeft een server toegang om te verbinden.
- * OPMERKING: Beiden servers hebben een link { } nodig om goed te kunnen verbinden!
- * De syntax is als volgt:
- * link (server naam)
- * {
- *	username	(username, * werkt ook);
- * 	hostname	(ip number/hostmask);
- *	bind-ip		(welk IP te binden wanneer je connect, of *);
- *	port		(poort om naar te verbinden);
- *	hub (Als dit een hub is, werkt '*');
- *	[of leaf *;]
- *	password-connect "(wachtwoord te zenden)";
- *	password-receive "(wachtwoord te ontvangen)";
- *	class		(class waarin de server geplaatst moet worden);
- *	options {
- *		(opties hier*);
- *	};
- *      // Als we SSL gebruiken, kunnen we kiezen welke cipher we willen gebruiken in SSL mode
- *      // Verkrijg een lijst door "openssl ciphers", onderscheid ciphers met :'s
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-	opties:
-	OUD	|	NIEUW
-	S		ssl
-	Z		zip
-	N/A		autoconnect
-	N/A		quarantine
-	N/A		nodnscache
-*/
-
-
-link            hub.mynet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Opmerking: Gebruik geen autoconnect naar Services */
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * NIEUW: ulines {}
- * OUD: U:Line
- * U:Lines geven servers meer macht/commando's. Gebruik het alleen voor
- * services en stats, en NOOIT voor normale UnrealIRCd servers!
- * De syntax is als volgt:
- * ulines {
- *	(server to uline);
- *	(server to uline);
- *  [etc]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * NIEUW: drpass {}
- * OUD: X:Line
- * Stelt de wachtwoorden voor /die en /restart in.
- * De syntax is als volgt:
- * drpass { 
- *  restart		"(wachtwoord voor herstart)";
- *  die		    "(wachtwoord voor beeindigen)";
- * };
- */
-drpass {
-	restart "I-love-to-restart";
-	die "die-you-stupid";
-};
-
-/*
- * NIEUW: log {}
- * OUD: N/A
- * Laat de IRCd weten wat en waar te loggen. Je kan er
- * zoveel instellen als je wilt.
- * 
- * FLAGS: errors, kills, tkl, connects, server-connects, kline, oper
- * 
- * De syntax is als volgt: 
- *
- * log "log file" 
- * {
- *    flags
- *    {
- *        flag;
- *        flag; 
- *        etc.. 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-  /* Verwijder het logbestand en begint een nieuwe wanneer de oude 2MB groot is. Laat dit leeg om altijd
-     hetzelfde bestand te gebruiken */
-	maxsize 2097152;
-	flags {
-		oper;
-		kline;
-		connects;
-		server-connects;
-		kills;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * NIEUW: alias {}
- * OUD: N/A
- * Hiermee stel je commando's zoals /nickserv, /chanserv etc in.
- * FLAGS: services, stats, normal
- *
- * De syntax is als volgt:
- * alias "naam" {
- *	target "wijst naar";
- *	type aliastype;
- * };
- *
- * [Opmerking: Je kan ook een standaard alias bestand gebruiken, zie doc/unreal32docs.nl.html sectie 2.9]
- */
-
-// Dit wijst het commando /nickserv naar de gebruiker NickServ welke verbonden is met set::services-server
-
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Als je het commando naar dezelfde nick als het commando wil sturen, kun je "target" weglaten.
-//alias ChanServ { type services; };
-
-// Wijst het /statserv commando naar de gebruiker Statserv verbonden met set::stats-server
-//alias StatServ { type stats; };
-
-// Wijst het /superbot commando naar de gebruiker SuperBot
-//alias SuperBot { type normal; };
-
-/* Standaard aliases */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * NIEUW: alias {}
- * OUD: N/A
- * Hiermee stel je commando's zoals /identify, /services in.
- *
- * De syntax is als volgt:
- * alias "naam" {
- *	format "format string" {
- *		target "wijst naar";
- *    type aliastype;
- *		parameters "parameters te verzenden";
- *	};
- *	type command;
- * };
- */
-
-/* Hier wordt apart notitie van gemaakt, hoewel het dezelfde naam heeft als het vorige block. Het verschilt veel
- * in syntax, maar het maakt gebruik van dezelfde functies.
- */
-
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-
-/* De alias::format is een reguliere expressie. Het eerste formaat matcht het /identify commando wanneer
- * het eerste teken een # is. Daarna wordt het doorgezonden naar de chanserv alias met de parameters
- * IDENTIFY %1-. Het tweede formaat matcht het /identify commando wanneer het eerste teken geen # is. Daarna
- * wordt het commando doorgestuurd naar de nickserv alias met de parameters IDENTIFY %1-.
- */
-
-/* Het alias::format::parameters is gelijk aan script-talen. %N (N is een nummer) staat voor de parameter die
- * gezonden is naar het commando (in dit geval /identify). Wanneer je %N- opgeeft, betekent dat alle parameters
- * vanaf N tot de laatste paramater in de string. Je kan ook %n gebruiken, waar %n vervangen wordt door de nick.
-*/
-
-/* Standaard aliases */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-/* Dit is een voorbeeld van een echt commando alias */	
-/* Dit verwijst /GLINEBOT naar /GLINE <parameter> 2d etc... */	
-alias "glinebot" {	
-	format ".+" {	
-		command "gline";	
-		type real;	
-		parameters "%1 2d Bots are not allowed on this server, please read the faq at http://www.example.com/faq/123";	
-	};	
-	type command;	
-};
-
-/*
- * NIEUW: tld {}
- * OUD: T:Line
- * Hiermee stel je verschillende MOTD en RULES bestanden in,
- * afhangend van de gebruikers hostmask.
- * De syntax is als volgt: 
- * tld {
- *    mask (ident@host);
- *    motd "(motd bestand)";
- *    rules "(rules bestand)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* Opmerking: je kan het bovenstaande voorbeeld verwijderen.
- * In dat geval worden de standaard motd/rules bestanden (ircd.motd, ircd.rules).
- * gebruikt voor iedereen.
- */
-
-/*
- * NIEUW: ban nick {}
- * OUD: Q:Line
- * Bant een nickname zodat deze niet gebruikt kan worden.
- * De syntax is als volgt:
- * ban nick {
- *	mask "(nick om te bannen)";
- *	reason "(reden)";
- * };
- */
- 
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Reserved for Services";
-};
-
-/*
- * NIEUW: ban ip {}
- * OUD: Z:Line
- * Bant een IP van de server
- * De syntax is als volgt:
- * ban ip {
- *  mask (ip number/hostmask);
- *  reason "(reden)";
- * };
- */
-
-ban ip {
-	mask 195.86.232.81;
-	reason "Delinked server";
-};
-
-/*
- * NIEUW: ban server {}
- * OUD: Server Q:Line
- * Zorgt ervoor dat een server niet kan verbinden met het netwerk.
- * Als de server naar een andere server linkt, zal de lokale server
- * de verbinding met het netwerk verbreken.
- * De syntax is als volgt:
- * ban server {
- *	mask "(server naam)";
- *	reason "(reden)";
- * };
- */
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Get out of here.";
-};
-/*
- * NIEUW: ban user {}
- * OUD: K:Line
- * Zorgt ervoor dat een gebruiker met een bepaalde mask niet
- * kan verbinden met je server.
- * De syntax is als volgt:
- * ban user {
- *  mask (hostmask/ip number);
- *  reason "(reden)";
- * };
- */
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-        reason "Idiot";
-};
-
-/*
- * NIEUW: ban realname {}
- * OUD: n:Line
- * Belet het gebruik van een bepaalde realname.
- * De syntax is als volgt:
- * ban realname {
- *	mask "(real name)";
- * 	reason "(reden)";
- * };
- */
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * OPMERKING VOOR ALLE BANS: Ze mogen herhaald worden voor extra toevoegingen!
- * 
- * NIEUW: except ban {} 
- * OUD: E:Line
- * Zorgt ervoor dat jij niet gebanned kan worden.
- * De syntax is als volgt:
- * except ban { mask (ident@host); };
- * Herhaal de except ban {} zo vaak als je wilt
- * voor andere hosts.
- */
-
-except ban {
-	/* don't ban stskeeps */
-	mask           *stskeeps@212.*;
-};
-
-/*
- * NIEUW: deny dcc {} 
- * OUD: dccdeny.conf
- * Wordt gebruikt om DCC sends te blokkeren..
- * Stopt virii beter.
- * De syntax is als volgt: 
- * deny dcc 
- * { 
- *   filename "bestand te blokkeren (bv, *exe)";
- *   reason "reden";
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Possible Sub7 Virus";
-};
-
-/*
- * NIEUW: deny channel {}
- * OUD: N/A (NIEUW)
- * Belet het gebruik van een kanaal.
- * De syntax is als volgt:
- * deny channel {
- * 	channel "(kanaal)";
- * 	reason "reden";
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "Warez is illegal";
-};
-
-/*
- * NIEUW: vhost {}
- * OUD: Vhost.conf file
- * Dit zet een nep ip voor niet-opers, of voor opers
- * die te lui zijn /sethost te gebruiken ;)
- * De syntax is als volgt:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (ident@host toegestaan de vhost te gebruiken);
- *       };
- *       login (login name);
- *       password (password);
- *   };
- * Om je vhost te gebruiken, typ /vhost (login) (password) op IRC
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Je kan ook andere configuratiebestanden laden */
-/* include "klines.conf"; */
-
-/* Netwerk configuratie */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 	"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix	"rox";
-	/* prefix-quit 		"no"; */
-	/* Cloak keys moeten op alle servers in het netwerk hetzelfde zijn.
-	 * Ze worden gebruikt voor het maken van gemaskte hosts en moeten geheim blijven.
-	 * De keys moeten 3 willekeurige strings zijn, bestaande uit 5-100 tekens
-	 * (10-20 tekens is genoeg) en moeten bestaan uit kleine letters (a-z),
-	 * hoofdletters (A-Z) en getallen (0-9) [zie de eerste key als voorbeeld].
-     * Tip: Wanneer je met een *NIX systeem werkt, kun je './unreal gencloak' gebruiken in
-     * je shell. Dit genereert 3 willekeurige strings die je kunt gebruiken.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"en nog eentje";
-		"en nog eentje";
-	};
-	/* on-oper host */
-	hosts {
-		local		"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin		"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 	"netadmin.roxnet.org";
-		host-on-oper-up "no";
-	};
-};
-
-/* Server gerelateerde configuratie */
-
-set {
-	kline-address "stel.dit.adres.in";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#opers";
-	options {
-		hide-ulines;
-		/* Je kan hier ident checking aanzetten als je wilt */
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* Hoelang een gebruiker minimaal verbonden moet zijn voordat hij toegestaan wordt het
-	 * QUIT bericht te gebruiken. Dit stopt spam hopelijk. */
-	anti-spam-quit-message-time 10s;
-	/* Stelt een tekst in die standaard wordt gebruikt voor een quit.
-	 * Houdt in dat er geen eigen quits gebruikt mogen worden op deze server. */
-	/* static-quit "Client quit";	*/
-
-  /* Je kan ook alle part-redenen blokkeren door hieronder het commentaar weg te halen
-   * en er 'yes' neer te zetten. Je kan ook een standaard tekst gebruiken (bijvoorbeeld
-   * "Bye bye!") om deze tekst altijd te gebruiken..
-   */
-	/* static-part yes; */
-
-	/* Stelt in dat stats alleen door opers gebruikt mogen worden. Gebruik * voor alle stats,
-	 * en laat het weg zodat gebruikers alle stats kunnen zien. Typ '/stats' voor een lijst
-	 * van alle stats.
-	 * Sommige admins willen 'kGs' wellicht verwijderen zodat gewone gebruikers een lijst van
-	 * klines, glines en shunts kunnen zien.
-	 */
-	
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Throttle: dit voorbeeld zet een limie van 3 conneties per 60s (per host). */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Anti flood protectie */
-	anti-flood {
-		nick-flood 3:60;	/* 3 naamsveranderingen per 60 seconden (standaard) */
-	};
-
-	/* Spam filter */
-	spamfilter {
-		ban-time 1d; /* standaard duur van een *line gezet door spamfilter */
-		ban-reason "Spam/Advertising"; /* standaard reden */
-		virus-help-channel "#help"; /* kanaal te gebruiken voor 'viruschan' actie */
-		/* except "#help"; kanaal waar niet gefilterd wordt */
-	};
-};
-
-/*
- * Problemen of meer hulp nodig?
- * 1) www.vulnscan.org/UnrealIRCd/unreal32docs.html
- * 2) www.vulnscan.org/UnrealIRCd/faq/ <- hier staat 80% van je vragen!
- * 3) Als je nog steeds problemen hebt, kun je naar irc.unrealircd.org #unreal-support,
-      maar je moet wel eerst de documentatie en FAQ gelezen hebben!
- */

doc/example.ru.conf

@@ -1,791 +0,0 @@
-/*
- * example.conf by Daniel Hawton AKA Osiris (osiris@unrealircd.org).
- * example.ru.conf by Samets Anton aka Bock (bock@bynets.org).
- * $Id$
- * 
- * (Encoding): Windows-1251
- *
- * Работает для Unreal3.2.x
- * 
- * Итак, это русскоязычный пример example.conf. По синтаксису похож на C++.
- * По началу будет тяжело понять, что тут написано, однако во время практики и чтения
- * вы научитесь это делать.
- *
- * Просто скопируйте этот файл в главную директорию unrealircd и переименуйте в 'unrealircd.conf'.
- * 
- * Замечание: Все линии, кроме тех, которые начинаются с {, заканчиваются ; включая и закрывающую }. 
- * IRCd проигнорирует закомментированные линии.
- *
- * ПРОЧТИТЕ doc/unreal32docs.ru.html! Версия в интернете доступна по адресу:
- * www.vulnscan.org/UnrealIRCd/unreal32docs.ru.html
- * Она содержит большинство информации о конфигурировании, даёт представление о каждом блоке,
- * переменной и так далее...
- * Если вы пытаетесь редактировать этот файл без прочтения документации, вы гарантированно
- * потерпите неудачу!
- */
-
-/* Типы комментариев */
-# Первый тип (Shell type)
-// Второй тип (C++ style)
-/* Третий тип (C Style) */
-# данные линии игнорируются ircd.
-
-/*
- * UnrealIRCd поддерживает модули, загрузка некоторых необходима для запуска.
- * Вам необходимо загрузить как минимум модули команд и скрытия хоста.
- */
-
-/* Для *NIX систем раскомментируйте следующие 2 линии: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* Для Windows систем раскомментируйте следующие 2 линии: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Вам необходимо подключить и другие конфигурационные файлы.
- * help.ru.conf содержит весь текст команды /helpop. Файлы badwords.*.conf
- * содержат все включения матных слов для режима +G...
- * spamfilter.conf содержит правила для защиты от троянских коней.
- * Вы вероятно захотите подключить эти файлы:
- */
-include "help.ru.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * НОВОЕ: me {} 
- * СТАРОЕ: M:Line 
- * me {} определяет имя, описание и нумерик сервера unreal для данного сервера.
- * Синтаксис: 
- * me { 
- *  name "Имя.сервера"; 
- *  info "Описание сервера";
- *  numeric (нумерик сервера*);
- * }; 
- * При соединении с другими серверами, нумерик должен быть уникальным в сети. Имя сервера - англоязычное.
- */
-me
-{
-    name "irc.foonet.com";
-    info "Сервер FooNet";
-    numeric 1;
-};
-
-/*
- * НОВОЕ: admin {} 
- * СТАРОЕ: A:Line
- * Данный блок предоставляет информацию об администраторе сервера.
- * Вы можете поместить сколько угодно линий после admin {. 
- * Синтаксис:
- * admin {
- *   "первая линия"; 
- *   "вторая линия"; 
- *   [так далее]
- * };
- */
-admin {
-    "Вася Пупкин!";
-    "vasya_pupkin";
-    "haker@lamer.ru";
-    "ICQ: 987654321";
-};
-
-/*
- * НОВОЕ: class {} 
- * СТАРОЕ: Y:line (был слишком запутан) 
- * Определяет настройки для классов. Класс определяет групповые настройки для подключений.
- * Например, подключение сервера, вместо включения его в класс пользователей, вы направляете в
- * класс серверов. Используется следующий синтаксис:
- * class (имя класса)
- * {
- *     pingfreq (как часто пиновать пользователя/сервер в секундах);
- *     maxclients (сколько максимально соединений разрешено данному классу);
- *     sendq (максимальная очередь для отправки от подключения);
- *     recvq (максимальная очередь для получения от подключения [контроль за флудом]);
- *  };
- */
-
-class           clients
-{
-    pingfreq 90;
-    maxclients 500;
-    sendq 100000;
-    recvq 8000;
-};
-
-class           servers
-{
-    pingfreq 90;
-    maxclients 10;        /* Какое максимальное количество серверов может быть прилинковано к этому серверу */
-    sendq 1000000;
-    connfreq 100; /* Через сколько секунд проводить следующую попытку подключения */
-};
-
-/*
- * НОВОЕ: allow {} 
- * СТАРОЕ: I:Line
- * Определяет, кому разрешено подключаться к серверу...
- * В основном используется для клиентов, это разрешает им подключаться к серверу, а вы можете их контролировать
- * и/или устанавивать пароль.
- * Синтаксис: 
- * allow {
- *    ip (разрешённая маска ip);
- *    hostname (маска хоста);
- *    class (класс, в который определить[смотри class {}]);
- *    password "(пароль)"; (необязательно)
- *    maxperip (сколько подключений с одного ip); (необязательно) 
- * };
- */
-
-allow {
-    ip             *@*;
-    hostname       *@*;
-    class           clients;
-    maxperip 5;
-};
-
-/* Разрешение подключения с паролем */
-allow {
-    ip             *@255.255.255.255;
-    hostname       *@*.passworded.ugly.people;
-    class           clients;
-    password "аццкип0р0ль";
-    maxperip 1;
-};
-
-/*
- * НОВОЕ: allow channel {} 
- * СТАРОЕ: chrestrict 
- * Позволяет пользователю зайти на канал...
- * служит как исключение из запрещённых каналов. 
- * Синтаксис:
- * allow channel {
- *   channel "имя канала";
- * };
- */
-allow           channel {
-    channel "#WarezSucks";
-};
-
-/*
- * НОВОЕ: oper {} 
- * СТАРОЕ: O:Line 
- * Определяет IRC оператора
- * IRC операторы следят за сервером, занимаются его поддержкой и подключением к сети. 
- * Синтаксис: 
- * oper (логин) { 
- *     class (класс, в который определять их, если отличен от блока I, в какой класс переместить); 
- *     from { 
- *        userhost (идент@хост);
- *        userhost (идент@хост);
- *     }; 
- *     flags
- *     { 
- *       (тут флаги*);
- *     };
- *     ИЛИ
- *     flags "флаги старого типа, вида OAaRD";
- * };
- */
-
-
-/* Для списка флагов оператора прочитайте doc/unreal32docs.ru.html#operblock
- * [ОЧЕНЬ НАСТОЯТЕЛЬНО рекомендуется к прочтения]
- */
-
-oper vasyapupkin {
-    class           clients;
-    from {
-        userhost vasya@somewhere.by;
-    };
-    password "p0r0l'";
-    flags
-    {
-        netadmin;
-        can_zline;
-        can_gzline;
-        can_gkline;
-        global;
-    };
-};
-
-/*
- * НОВОЕ: listen {}
- * СТАРОЕ: P:Line
- * Определяет, на каких портах будет работать ircd,
- * позволяя пользователям/серверам подключаться к серверу. 
- * Синтаксис:
- * listen (ip):(номер порта) 
- * { 
- *   options {
- *     (тут опции);
- *   };
- * };
- * или просто
- * listen: listen (ip):(порт);
- * 
- * ЗАМЕЧАНИЕ: для протокола ip v6 (3ffe:b80:2:51d::2), используйте [ip]:порт;
- * 
- * Это так же будет работать.
- */
-
-/* Опции для listen:
-    СТАРЫЕ    |     НОВЫЕ
-    S        serversonly
-    C        clientsonly
-    J        java
-    s        ssl
-    *        standard
-*/
-
-/* ЗАМЕЧАНИЕ ДЛЯ ПОРТОВ SSL: SSL порты стандартизированы,
- * за исключением многочисленных "высоких" портов SSL, некоторые люди могут сказать вам, 
- * чтобы вы запустили на порту 994, потому что он официальный порт SSL... Но это же
- * требует привилегий пользователя root! К слову, порт 194 - официальный порт irc, 
- * но вы видели когда-нибудь ircd, запущенный на нём?
- * Итак, наше предложение - использовать порт 6697 для SSL, он используется уже рядом сетей
- * и используется в примере StunTour.
- * Вы можете открыть сколько угодно портов SSL, но используя так же и 6697, вы поможете
- * стандартизировать его;).
- */
-listen         *:6697
-{
-    options
-    {
-        ssl;
-        clientsonly;
-    };
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* ЗАМЕЧАНИЕ: Если вы используете шелл IRCd, где несколько IP адресов, вы можете получить сообщение типа
- *            'Address already in use', ошибки в вашем лог-файле и ircd не запустится.
- *            Это значит, что вам необходимо указать определённый адрес IP вместо '*', к примеру:
- *            listen 1.2.3.4:6667;
- *            Конечно же, измените IP адрес на тот, который назначен вам.
- */
-
-/*
- * НОВОЕ: link {}
- * СТАРОЕ: C/N:Lines
- * Определяет блок для подключения серверов.
- * ЗАМЕЧАНИЕ: ЧТОБЫ ПОДКЛЮЧИТЬСЯ БЕЗ ВОПРОСОВ, НА ОБОИХ СЕРВЕРАХ НЕОБХОДИМЫ ПРАВИЛЬНЫЕ НАСТРОЙКИ LINK {}!
- * Синтаксис:
- * link (имя сервера)
- * {
- *    username    (имя пользователя, * работает тоже);
- *     hostname    (адрес ip/маска хоста);
- *    bind-ip        (На каком адресе IP слушать или *);
- *    port        (порт для соединения);
- *    hub (если это хаб, * так же работает, или макси сервера, которые могут быть под ним);
- *    [или leaf *;]
- *    password-connect "(пароль для отправки)";
- *    password-receive "(пароль, что мы должны получить)";
- *    class        (класс, в который определить сервер);
- *    options {
- *        (тут указываются опции*);
- *    };
- *      // Если мы используем SSL, мы можем указать, какой шифр использовать в режиме SSL
- *      // Получить список можно "openssl ciphers", шифры разделяются двоеточиями (:)
- *      
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-    опции:
-    СТАРЫЕ    |    НОВЫЕ
-    S        ssl
-    Z        zip
-    N/A        autoconnect
-    N/A        quarantine
-    N/A        nodnscache
-*/
-
-
-link		hub.ru.by
-{
-    username    *;
-    hostname     1.2.3.4;
-    bind-ip     *;
-    port         7029;
-    hub             *;
-    password-connect "LiNk";
-    password-receive "LiNk";
-    class           servers;
-        options {
-            /* Замечание: Вы не должны использовать автоподключение (autoconnect) при подключении сервисов */
-            autoconnect;
-            ssl;
-            zip;
-        };
-};
-/*
- *
- * НОВОЕ: ulines {}
- * СТАРОЕ: U:Line
- * U-lines обладают большей силой/властью, чем другие сервера. Это нужно устанавливать только на
- * сервисы/сервера сбора статистики и НИКОГДА на обычные сервера UnrealIRCd!
- * Синтаксис:
- * ulines {
- *    (сервер в uline);
- *    (сервер в uline);
- *  [и т.д.]
- * };
-*/
-ulines {
-    services.roxnet.org;
-    stats.roxnet.org;
-};
-
-/*
- * НОВОЕ: drpass {}
- * СТАРОЕ: X:Line
- * Определяет пароли для использования команд /die и /restart.
- * Синтаксис:
- * drpass { 
- *  restart        "(пароль для перезапуска)";
- *  die            "(пароль для отключения)";
- * };
- */
-drpass {
-    restart "Я-люблю-перезапускать-сервер";
-    die "умри-тупое!:)";
-};
-
-/*
- * НОВОЕ: log {} 
- * СТАРОЕ: N/A 
- * Указыает ircd куда и что протоколировать (вести лог). Вы можете указать столько, сколько пожелаете.
- * 
- * ФЛАГИ: errors, kills, tkl, connects, server-connects, oper
- * 
- * Синтаксис: 
- * log "путь_к_лог_файлу" 
- * {
- *    flags
- *    {
- *        flag;
- *        flag; 
- *        etc.. 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-    /* Удалять логфайл и старовать новый, если размер превышает 2MB, оставьте это как есть, чтобы использовать
-	тот же самый файл */
-    maxsize 2097152;
-    flags {
-        oper;
-        connects;
-        server-connects;
-        kills;
-        errors;
-        sadmin-commands;
-        chg-commands;
-        oper-override;
-        spamfilter;
-    };
-};
-
-/*
- * НОВОЕ: alias {}
- * СТАРОЕ: N/A
- * Позволяет установить вам псевдонимы на команды, такие как /nickserv, /chanserv и т.д.
- * ФЛАГИ: services, stats, normal
- *
- * Синтаксис:
- * alias "имя" {
- *    target "куда направить";
- *    type aliastype;
- * };
- *
- * [ЗАМЕЧАНИЕ: Вы так же можете подключить уже определённый файл с псевдонимами,подробнее doc/unreal32docs.ru.html в секции 2.9]
- */
-
-// Данный псевдноним /nickserv направляет команды пользователю NickServ, который подключён к серверу set::services-server
-/*alias NickServ {
-    target "NickServ";
-    type services;
-};*/
-
-// Если вы хотите, чтобы команды направлялись на тот же ник, что и команда, вы можете не указывать target
-//alias ChanServ { type services; };
-
-// Указывает, что команда /statserv будет отправлена пользователю StatServ, подключённого к серверу set::stats-server
-//alias StatServ { type stats; };
-
-// Указывает, что команда /superbot будет отправлена пользователю SuperBot
-//alias SuperBot { type normal; };
-
-
-/* Стандартные псевдонимы */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * НОВОЕ: alias {}
- * СТАРОЕ: N/A
- * Позволяет установить такие псевдонимы на команды как /identify, /services и т.д.
- *
- * Синтаксис:
- * alias "имя" {
- *    format "строка формата" {
- *        target "кому";
- *              type aliastype;
- *        parameters "список параметров";
- *    };
- *    type command;
- * };
- */
-/* Вынесено отдельно, так как имеются отличия по сравнению с предыдущим типом псевдонимов и имеются очень большие отличия в
- * синтаксисе, так же используется для других целей, чем стандартные псевдонимы.
- */
-/*
-alias "identify" {
-    format "^#" {
-        target "chanserv";
-        type services;
-        parameters "IDENTIFY %1-";
-    };
-    format "^[^#]" {
-        target "nickserv";
-        type services;
-        parameters "IDENTIFY %1-";
-    };
-    type command;
-};
-*/
-/* Директива alias::format является регулярным выражением. Под первый формат подпадает команда /identify, 
- * если первым символом является #. Она посылает команду chanserv с параметрами IDENTIFY %1-.
- * Второй формат срабатывает, если в команде, посланной посредством /identify первый символ не #. Тогда ircd
- * передаёт эту команду nickserv с параметрами IDENTIFY %1-.
- */
-
-/* alias::format::parameters сходно со скриптовыми языками. %N (где N число) представляет собой параметр, посланный командой
- * (в случае /identify). Если вы указали %N-, так вы определили все параметры, начиная от N до последнего в этой строке.
- * Вы можете так же указать %n, что будет означать ник пользователя.
-*/
-
-/* Стандартные псевдонимы */
-alias "services" {
-    format "^#" {
-        target "chanserv";
-        type services;
-        parameters "%1-";
-    };
-    format "^[^#]" {
-        target "nickserv";
-        type services;
-        parameters "%1-";
-    };
-    type command;
-};
-
-alias "identify" {
-    format "^#" {
-        target "chanserv";
-        type services;
-        parameters "IDENTIFY %1-";
-    };
-    format "^[^#]" {
-        target "nickserv";
-        type services;
-        parameters "IDENTIFY %1-";
-    };
-    type command;
-};
-
-/* Тут идёт пример использования "действительно псевдонима" (real command alias) */
-/* Данный пример - использование /GLINEBOT как /GLINE <параметры> 2d и т.д... */
-alias "glinebot" {
-    format ".+" {
-        command "gline";
-        type real;
-        parameters "%1 2d Боты запрещены на этом сервере, прочитайте ЧаВО на http://www.example.com/faq/123";
-    };
-    type command;
-};
-
-
-
-/*
- * НОВОЕ: tld {}
- * СТАРОЕ: T:Line
- * Устанавливает различные different motd и rules файлы
- * в зависимости от маски хостов клиентов.
- * Синтаксис: 
- * tld {
- *    mask (идент@хост);
- *    motd "(файл motd)";
- *    rules "(файл rules)";
- * };
- */
-
-tld {
-    mask *@*.ru;
-    motd "ircd.motd.ru";
-    rules "ircd.rules.ru";
-};
-
-/* замечание: вы можете просто удалить блок выше, указанный для примера в случае, если есть в наличии
- * файлы motd/rules, используемые по умолчанию (ircd.motd, ircd.rules), которые будут использоваться всеми
- */
-
-/*
- * НОВОЕ: ban nick {}
- * СТАРОЕ: Q:Line
- * Банит ник, он не может быть использован.
- * Синтаксис:
- * ban nick {
- *    mask "(ник для бана)";
- *    reason "(причина)";
- * };
-*/
-ban nick {
-    mask "*C*h*a*n*S*e*r*v*";
-    reason "Зарезервирован для сервисов";
-};
-/*
- * НОВОЕ: ban ip {}
- * СТАРОЕ: Z:Line
- * Банит адрес ip при подключении в сеть.
- * Синтаксис:
- * ban ip { mask (адрес ip/маска хоста); reason "(причина)"; };
-*/
-ban ip {
-    mask 195.86.232.81;
-    reason "Отключённый сервер";
-};
-/*
- * НОВОЕ: ban server {}
- * СТАРОЕ: Серверный Q:Line
- * Отключает сервер от попыток подключиться в сеть.
- * Если сервер подключается к удалённому серверу в сети, локальный сервер
- * будет отключён он сети.
- * Синтаксис:
- * ban server {
- *    mask "(имя сервера)";
- *    reason "(причина)";
- * };
-*/
-
-ban server {
-    mask eris.berkeley.edu;
-    reason "Ламерский сервер :).";
-};
-/*
- * НОВОЕ: ban user {}
- * СТАРОЕ: K:Line
- * Пользователь с указанной маской не может подключиться к вашему серверу.
- * Синтаксис:
- * ban user { mask (маска хоста/адрес ip); reason "(причина)"; };
-*/
-
-ban user {
-    mask *newiceman@*.irc.by;
-        reason "Идиот!";
-};
-
-/*
- * НОВОЕ: ban realname {}
- * СТАРОЕ: n:Line
- * Банит по указанному пользователем реальному имени.
- * Синтаксис:
- * ban realname {
- *    mask "(Реальное имя)";
- *     reason "(причина)";
- * };
-*/
-
-ban realname {
-    mask "Swat Team";
-    reason "mIRKFORCE";
-};
-
-ban realname {
-    mask "sub7server";
-    reason "sub7";
-};
-
-/*
- * ЗАМЕЧАНИЕ ДЛЯ ВСЕХ БАНОВ: они могут повторятся в случае необходимости уточнений!
- * 
- * НОВОЕ: except ban {} 
- * СТАРОЕ: E:Line
- * Предотвращает бан. 
- * Синтаксис:
- * except ban { mask (идент@хост); };
- * Повторите except ban {} столько раз, сколько хотите использовать различные хосты.
- */
-
-except ban {
-    /* не банить wax */
-    mask           *wax@195.222.*;
-};
-
-/*
- * НОВОЕ: deny dcc {} 
- * СТАРОЕ: dccdeny.conf
- * Используется чтобы запретить отправку dcc... служит для защиты от вирусов
- * Синтаксис: 
- * deny dcc 
- * { 
- *   filename "имя файла для блокироваки (т.е. *exe)";
- *   reason "причина";
- * };
- */
-deny dcc {
-    filename "*sub7*";
-    reason "Вероятность вируса Sub7";
-};
-
-/*
- * НОВОЕ: deny channel {}
- * СТАРОЕ: N/A (НОВОЕ)
- * Запрещает вход на указанные каналы.
- * Синтаксис:
- * deny channel {
- *     channel "(канал)";
- *     reason "причина";
- * };
-*/
-deny channel {
-    channel "*warez*";
-    reason "Warez нелегален";
-};
-
-/*
- * НОВОЕ: vhost {}
- * СТАРОЕ: файл Vhost.conf
- * Устанавливает фейковый ip для не-операторов или операторы слишком
- * ленивые, чтобы сделать /sethost :P
- * Синтаксис:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (идент@хост, кому разрешено использовать);
- *       };
- *       login (логин);
- *       password (пароль);
- *   };
- *        чтобы использовать vhost, наберите /vhost (логин) (пароль) в IRC
- */
-vhost {
-    vhost           i.hate.microsefrs.com;
-    from {
-        userhost       *@*.image.dk;
-    };
-    login           stskeeps;
-    password        moocowsrulemyworld;
-};
-
-/* Вы так же можете подключить и другие конфигурационные файлы */
-/* include "klines.conf"; */
-
-/* Конфигурация Сети */
-set {
-    network-name         "ROXnet";
-    default-server         "irc.roxnet.org";
-    services-server     "services.roxnet.org";
-    stats-server         "stats.roxnet.org";
-    help-channel         "#ROXnet";
-    hiddenhost-prefix    "rox";
-    /* prefix-quit         "no"; */
-    /* Ключи скрытия хостов должны быть одинаковы на всех серверах в сети.
-     * Они использутся для генерации замаскированных хостов и должны держаться в секрете.
-     * Ключи должен быть 3-мя случайными срочками с 5-100 символами в каждой
-     * (10-20 символов должно быть достаточно) и должны содержать прописные (a-z),
-     * заглавные (A-Z) буквы и цифрты (0-9) [смотрите пример первого ключа].
-     * Подсказка: В *NIX системах вы можете запустить './unreal gencloak' в вашем шелле, чтобы получить
-     * 3 строки, сгенерированные случайным образом.
-     */
-    cloak-keys {
-        "aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-        "и ещё одна;
-        "и ещё одна";
-    };
-    /* хост on-oper */
-    hosts {
-        local        "locop.roxnet.org";
-        global        "ircop.roxnet.org";
-        coadmin        "coadmin.roxnet.org";
-        admin        "admin.roxnet.org";
-        servicesadmin     "csops.roxnet.org";
-        netadmin     "netadmin.roxnet.org";
-        host-on-oper-up "no";
-    };
-};
-
-/* Специфическая конфигурация сервера */
-
-set {
-    kline-address "set.this.email";
-    modes-on-connect "+ixw";
-    modes-on-oper     "+xwgs";
-    oper-auto-join "#opers";
-    options {
-        hide-ulines;
-        /* Если желаете, вы можете включить проверку ident  */
-        /* identd-check; */
-        show-connect-info;
-    };
-
-    maxchannelsperuser 10;
-    /* Указывает минимальное время, сколько был подключен пользователь, 
-     * прежде чем разрешать ему использовать сообщение QUIT.
-     * Должно помочь в борьбе со спамом */
-    anti-spam-quit-message-time 10s;
-    /* Устанавливает постоянное сообщение о выходе - значит, что локальный сервер не разрешит
-           различные сообщения о выходе */
-    /* static-quit "Клиент вышел";    */
-
-    /* Вы так же можете блокировать все сообщения о выходе из канала просто раскомментировав это и указать'yes'
-     * или указать какой-нибудь другой текст (например: "Пока пока!"), который всегда будет использован как причина. */
-    /* static-part yes; */
-
-    /* Позволяет сделать важные сообщения stats были использованы только операторами, используйте * для всех сообщений stats,
-     * или закомментируйте, что позволит пользователям видеть все сообщения stats. Чтобы получить весь список, введите '/stats'.
-     * Некоторые администраторы могут убрать 'kGs' для того, чтобы разрешить обычным пользователям видеть список
-     * klines, glines и shuns.
-     */
-    oper-only-stats "okfGsMRUEelLCXzdD";
-
-    /* Тротлинг: данный пример устанавливает предел в 3 попытки подключения в 60 секунд (для одного хоста). */
-    throttle {
-        connections 3;
-        period 60s;
-    };
-
-    /* Защита от флуда */
-    anti-flood {
-        nick-flood 3:60;    /* 3 изменения ника в 60 секунд (по умолчанию) */
-    };
-
-    /* Фильтр спама */
-    spamfilter {
-        ban-time 1d; /* длительность по умолчанию бана *line, установленного spamfilter */
-        ban-reason "Спам/Реклама"; /* причина по умолчанию */
-        virus-help-channel "#help"; /* канал при использовании действия 'viruschan' */
-        /* except "#help"; канал для исключения действия фильтра */
-    };
-};
-
-/*
- * Проблемы или нуждаетесь в более подробной информации?
- * 1) www.vulnscan.org/UnrealIRCd/unreal32docs.ru.html
- * 2) www.vulnscan.org/UnrealIRCd/faq/ <- содержит 80% ваших вопросов!
- * 3) Если у вас до сих пор остались проблемы, зайдите на irc.unrealircd.org #unreal-support,
- *    но мы требуем, чтобы вы ПРЕЖДЕ ПРОЧИТАЛИ ДОКУМЕНТАЦИЮ и ЧаВО!
- */

doc/example.tr.conf

@@ -1,841 +0,0 @@
-/*
- * example.conf by Daniel Hawton AKA Osiris (osiris@unrealircd.org).
- * $Id$ 
- * Önceki Çevirmen: Mustafa "Ironic" Cakmak (ironic@unrealircd.org)
- * Türkçe Çeviri:   Serkan Sepetçi (diablo@unrealircd.org)
- *
- * Unreal3.2.x sürümler için kullanılmaktadır
- * 
- * Peki beyler.  Bu example.conf dosyasının yenisi. C++ türüne çok benziyor.
- * Neyse şimdi bunun üstesinden gelme zamanı.  Başlangıçta zor gelebilir, fakat
- * okuyarak ve biraz pratikle anlayacaksınız.
- *
- * Yapmanız gereken bu dosyayı ana dizine atıp, 'unrealircd.conf' olarak adlandırmak.
- * 
- * NOTE:  Bütün satırlar, açılış { satırı dışında, kapama } satırı dahil, sonunda ; taşır.
- * IRCd açıklama satırlarını göz ardı edecektir.
- *
- * Lütfen doc/unreal32docs.tr.html dosyasını okuyunuz! Çevrimiçi sürümüne ulaşabileceğiniz adres:
- * www.vulnscan.org/UnrealIRCd/unreal32docs.tr.html
- * Yapılandırma dosyası hakkında bir çok bilgi içerir: Her blok,
- * değişken vs.. hakkında bilgi verir.
- * Eğer dökümantasyon dosyasını tam olarak okumadan bu dosyayı düzenlemeye kalkarsanız
- * başarısız olacağınız oldukça yüksek bir oranda garanti edilir!
- *
- */
-
-/* Açıklama satırı çeşitleri */
-#Açıklama satırı 1 (Shell tipi)
-// Açıklama satırı 2 (C++ tipi)
-/* Açıklama satırı satırı 3 (C tipi) */
-#Bu satırlar ircd tarafından göz ardı edilecektir.
-
-/*
- * UnrealIRCd modülleri destekler, Bunların bazılarının yüklenmesi gereklidir.
- * En azından komutlar modülü(commands) ve gizleme modülü(cloaking)'ne ihtiyacınız vardır.
- */
-
-/* *NIX için, sonraki 2 satırın açıklama satıracını(//) kaldırın: */
-//loadmodule "src/modules/commands.so";
-//loadmodule "src/modules/cloak.so";
-
-/* Windows için, sonraki 2 satırın açıklama satıracını(//) kaldırın: */
-//loadmodule "modules/commands.dll";
-//loadmodule "modules/cloak.dll";
-
-/*
- * Diğer yapılandırma dosyalarınıda dahil edebilirsiniz.
- * help.conf bütün /helpop metinlerini içerir. +G kipi için badwords.*.conf
- * dosyaları bütün kötü kelime girdilerini içerir...
- * spamfilter.conf güncel trojanlar için uygun kuralları içerir.
- * Muhtemelen bunları eklemek isteyeceksiniz:
- */
-include "help.conf";
-include "badwords.channel.conf";
-include "badwords.message.conf";
-include "badwords.quit.conf";
-include "spamfilter.conf";
-
-/*
- * YENI: me {} 
- * ESKI: M:Line 
- * me {} bu sunucu için isim, tanımlama ve unreal sunucu sayısalını(numeric) belirler.
- * Sözdizimi aşağıdaki gibidir: 
- * me { 
- *  name "sunucu.ismi"; 
- *  info "Sunucu tanımlaması";
- *  numeric (sunucu sayısalı*);
- * }; 
- * Eğer link varsa, bu sayısal ağ üzerinde varolan herhangi bir server tarafından kullanılmamalıdır.
- */
-me
-{
-	name "irc.foonet.com";
-	info "FooNet Server";
-	numeric 1;
-};
-
-/*
- * YENI: admin {} 
- * ESKI: A:Line
- * Admin sunucu yöneticisine dair bilgi verir. Dilediğiniz kadar
- * satırı admin { altına yerleştirebilirsiniz. 
- * Sözdizimi aşağıdaki gibidir:
- * admin {
- *   "ilk satır"; 
- *   "ikinci satır"; 
- *   [vs]
- * };
- */
-admin {
-	"Bob Smith";
-	"bob";
-	"widely@used.name";
-};
-
-/*
- * YENI: class {} 
- * ESKI: Y:line (eskisi karışıktı) 
- * Bu sınıflar için ayarları belirtir. Bir sınıf bağlantılar için bir grup 
- * ayarıdır. Örneğin, sunucu bağlantılarını, bir istemci sınıfı
- * yerine, sunucu sınıfına yönlendirirsiniz. Sözdizimi aşağıdaki gibidir:
- * class (class name)
- * {
- *     pingfreq (ne sıklıkta saniye içerisinde kullanıcı veya sunucunun ping edileceği);
- *     maxclients (bu sınıf için kaç bağlantı);
- *     sendq (bir bağlantıdan gönderilecek en yüksek dizi);
- *     recvq (bir bağlantıdan alınacak en yüksek dizi [flood kontrolü]);
- *  };
- */
-
-class   clients
-{
-	pingfreq 90;
-	maxclients 500;
-	sendq 100000;
-	recvq 8000;
-};
-
-class   servers
-{
-	pingfreq 90;
-	maxclients 10;		/* Link edebileceğimiz en yüksek sunucu sayısı */
-	sendq 1000000;
-	connfreq 100; /* Her bağlantı girişimi arasında ne kadar saniye olacağı */
-};
-
-/*
- * YENI: allow {} 
- * ESKI: I:Line
- * Bağlantı izinlerini belirtir..
- * Temel olarak istemcilerin sunucuya bağlanabilmesi için herhangi bir kontrol
- * ve/veya bir şifre belirtmenize olanak sağlar.
- * Sözdizimi aşağıdaki gibidir:
- * allow {
- *    ip (izin verilecek ip maskesi);
- *    hostname (host maskesi);
- *    class (gönderilecek sınıf [class {} bloğuna göz atınız]);
- *    password "(şifre)"; (isteğe bağlı)
- *    maxperip (ip başına kabul edilecek bağlantı sayısı); (isteğe bağlı) 
- * };
- */
-
-allow {
-	ip             *@*;
-	hostname       *@*;
-	class           clients;
-	maxperip 5;
-};
-
-/* Şifrelendirilmiş allow bloğu */
-allow {
-	ip             *@255.255.255.255;
-	hostname       *@*.passworded.ugly.people;
-	class           clients;
-	password "f00Ness";
-	maxperip 1;
-};
-
-/*
- * YENI: allow channel {} 
- * ESKI: chrestrict 
- * Bir kullanıcının bir kanala girmesine olanak sağlar...
- * yasak kanal bloğundaki hariçlik gibi.
- * Sözdizimi:
- * allow channel {
- *   channel "kanal ismi";
- *   class "clients"; (isteğe bağlı)
- * };
- */
-allow   channel {
-	channel "#WarezSucks";
-	class "clients";
-};
-
-/*
- * YENI: oper {} 
- * ESKI: O:Line 
- * Bir IRC Operatörü tanımlamanızı sağlar.
- * IRC Operatörleri sunucuya uygun bir biçimde bağlanılmasını ve
- * makullüğü sağlarlar. 
- * Sözdizimi aşağıdaki gibidir:
- * oper (login) { 
- *     class (sınıf ismini ekleyin, eğer istemciden farklıysa, yeni sınıfı ekleyin); 
- *     from { 
- *        userhost (ident@host);
- *        userhost (ident@host);
- *     }; 
- *     flags
- *     { 
- *       (flaglar buraya*);
- *     };
- *     VEYA
- *     flags "OAaRD gibi eski tip flaglar";
- * };
- */
-
-
-/* Oper flaglarının listesine doc/unreal32docs.html#operblock dan göz atabilirsiniz.
- * [Okumanız şiddetle önerilir]
- */
-
-oper bobsmith {
-	class           clients;
-	from {
-		userhost bob@smithco.com;
-	};
-	password "f00";
-	flags
-	{
-		netadmin;
-		can_zline;
-		can_gzline;
-		can_gkline;
-		global;
-	};
-};
-
-/*
- * YENI: listen {}
- * ESKI: P:Line
- * İstemci ve sunucuların sunucuya bağlanmasını sağlamak için ircd tarafından
- * kullanılacak bir port tanımlamanızı sağlar .
- * Sözdizimi aşağıdaki gibidir:
- * listen (ip adresi):(port numarası) 
- * { 
- *   options {
- *     (tercihler buraya);
- *   };
- * };
- * veya sade bir biçimde
- * listen: listen (ip):(port);
- * 
- * UYARI: ipv6 ipleri için (3ffe:b80:2:51d::2 vb),  [ip]:port; kullanınız
- * 
- * Böylede çalışır.
- */
-
-/* listen için tercihler:
-	ESKI	| 	YENI
-	S		serversonly
-	C		clientsonly
-	J		java
-	s		ssl
-	*		standard
-*/
-
-/* SSL PORTLARI İÇİN NOT: SSL portları oldukça standart dışıdır,
- * ayrıca pek çok yüksek-SSL portları için bazı insanlar 994 te çalıştırın 
- * der çünkü bu resmi SSL portudur..Fakat bu root erişimi gerektirir.Yanı sıra, 
- * 194 resmi irc portu olarak bunun üzerinde çalışan ircd 
- * hiç gördünüz mü?
- * Böyle olunca bizim önerimiz 6697 portunu SSL için kullanmanız, bu hayli 
- * sunucuda kullanılıyor ve örnek için StunTour tarafından kabul görmüş durumda.
- * İstediğiniz kadar SSL port açmakta özgürsünüz, fakat 6697 yi kullanmanız
- * dünya standartı haline gelmesine biraz daha yardım edecektir. ;).
- */
-listen         *:6697
-{
-	options
-	{
-		ssl;
-		clientsonly;
-	};
-};
-
-listen         *:8067;
-listen         *:6667;
-
-/* NOT: Eğer bir çok IP barındıran bir IRCd Shell kullanıyorsanız logunuzda olası
- *       'Address already in use' alırsınız ve ircd başlamaz.Bunun anlamı '*' yerine 
- *       belirli bir IP adresi kullanmanız gerektiğidir.Yani örneğin:
- *       listen 1.2.3.4:6667;
- *       Açıkça, IP yi önceden koyduğunuz IP ile değiştirin.
- */
-
-/*
- * YENI: link {}
- * ESKI: C/N:Lines
- * Bir sunucu bağlantısı için bir onay tanımlamanızı sağlar.
- * NOT: HER IKI SUNUCUDA BAĞLANTI IÇIN TAM OLARAK DÜZGÜN BİR LINK {} GEREĞİ DUYAR!
- * Sözdizimi aşağıdaki gibidir:
- * link (sunucu ismi)
- * {
- *	username	(username, * da uygundur);
- * 	hostname	(ip adresi/hostmask);
- *	bind-ip		(Bağlanırken hangi IP ile bağlanacağı, veya *);
- *	port		(bağlantı portu, eğer herhangi biriyse);
- *	hub (Bu bir hub ise, * çalışır, veya sunucu maskeleri bunu sağlar);
- *	[veya leaf *;]
- *	password-connect "(gönderilecek şifre)";
- *	password-receive "(almamız gereken şifre)";
- *	class		(sunucuların yönetileceği sınıf);
- *	options {
- *		(tercihler buraya*);
- *	};
- *      // Eğer SSL kullanıyorsak, SSL modunda ne tür bir anahtar kullanacağımızı seçebiliriz
- *      // "openssl ciphers" ile bir liste alınır, anahtarlar birbirinden : ile ayrılırak belirtilebilirler.
- *      
- *      ciphers "DES-CBC3-MD5";
- * 
- * };
-*/
-
-/*
-	tercihler:
-	YENI	|	ESKI
-	S		ssl
-	Z		zip
-	N/A		autoconnect
-	N/A		quarantine
-	N/A		nodnscache
-*/
-
-
-link    hub.mynet.com
-{
-	username	*;
-	hostname 	1.2.3.4;
-	bind-ip 	*;
-	port 		7029;
-	hub             *;
-	password-connect "LiNk";
-	password-receive "LiNk";
-	class           servers;
-		options {
-			/* Note: Servisler link edilirken autoconnect kullanmamalısınız.*/
-			autoconnect;
-			ssl;
-			zip;
-		};
-};
-/*
- *
- * YENI: ulines {}
- * ESKI: U:Line
- * U-lines satırları sunuculara daha güç/komut kazandırır.Bu servis/istatistik
- * sunucuları içindir ve ASLA normal UnrealIRCd sunucuları için değildir.
- * Sözdizimi aşağıdaki gibidir:
- * ulines {
- *	(uline olacak sunucu);
- *	(uline olacak sunucu);
- *  [vb]
- * };
-*/
-ulines {
-	services.roxnet.org;
-	stats.roxnet.org;
-};
-
-/*
- * YENI: drpass {}
- * ESKI: X:Line
- * Bu blok /die ve /restart için şifre tanımlamanızı sağlar.
- * Sözdizimi aşağıdaki gibidir:
- * drpass { 
- *  restart		"(yeniden başlatmak için şfire)";
- *  die		        "(sona erdirmek için şifre)";
- * };
- */
-drpass {
-	restart "I-love-to-restart";
-	die "die-you-stupid";
-};
-
-/*
- * YENI: log {} ESKI: N/A Ircd e logun ne ve nerede olacağını bildirir. Dilediğiniz 
- * kadara sahip olabilirsiniz.
- * 
- * FLAGS: errors, kills, tkl, connects, server-connects, oper
- * 
- * Syntax: 
- * log "log file" 
- * {
- *    flags
- *    {
- *        flag;
- *        flag; 
- *        etc.. 
- *    }; 
- * };
- */
-
-log "ircd.log" {
-	/* Eğer 2 MB yi geçerse log dosyasını sil ve yenisini aç, eğer her zaman aynı log 
-         dosyasını kullanmak istiyorsanız karışmayın */
-	maxsize 2097152;
-	flags {
-		oper;
-		connects;
-		server-connects;
-		kills;
-		errors;
-		sadmin-commands;
-		chg-commands;
-		oper-override;
-		spamfilter;
-	};
-};
-
-/*
- * YENI: alias {}
- * ESKI: N/A
- * /nickserv, /chanserv gibi komutlar hazırlamanızı sağlar.
- * FLAGS: services, stats, normal
- *
- * Sözdizimi:
- * alias "isim" {
- *	target "gidecek nokta";
- *	type aliastype;
- * };
- *
- * [NOT: Aynı zamanda önceden tanımlanmış alias dosyası dahil edebilirsiniz, doc/unreal32docs.html bölüm 2.9]
- */
-
-// Bu nokta /NickServ komutu ile set::services-server server üzerinden bağlanmış olan NickServ e döner.
-/*alias NickServ {
-	target "NickServ";
-	type services;
-};*/
-
-// Eğer komutla noktanın aynı olmasını istiyorsanız nick girişini gözardı edebilirsiniz
-//alias ChanServ { type services; };
-
-// Bu nokta /statserv komutu ile set::stats-server server üzerinden bağlanmış olan StatServ e döner.
-//alias StatServ { type stats; };
-
-// Bu nokta /superbot komutu ile kullanıcı SuperBot a döner
-//alias SuperBot { type normal; };
-
-
-/* Standart aliases */
-alias NickServ { type services; };
-alias ChanServ { type services; };
-alias OperServ { type services; };
-alias HelpServ { type services; };
-alias StatServ { type stats; };
-
-/*
- * ESKI: alias {}
- * YENI: N/A
- * Bu /identify, /services gibi komutlar hazırlamanızı sağlar.
- *
- * Sözdizimi:
- * alias "isim" {
- *	format "format satırı" {
- *		target "gidecek nokta";
- *              type aliastype;
- *		parameters "gönderilecek parametreler";
- *	};
- *	type command;
- * };
- */
-/* Bu ayrı bir şekilde gösterilir.Çünkü bir önceki direktif ile aynı isme sahip olsa bile benzer bir 
- * fonksiyon sağlaması ve standart aliaseslerin çalışmasına dayanması ile birlikte çok farklı sözdizimine sahip olması.
- */
-/*
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-*/
-/* alias::format direktifi bir düzenli ifadedir. İlk biçim /identify komutundan sonraki ilk karakter bir # ise eşleşir.
- * Ardından IDENTIFY %1- ile chanserv aliases e döner.
- * İkinci biçim ise /identify komutundan sonraki ilk karakterin bir # işareti ile eşleşmeme durumunu belirtir.Ardından
- * IDENTIFY %1- ile nickserv aliases e döner.
- */
-
-/* alias::format::parameters betik diline benzerdir. %N (N bir numaradır) komuta gönderilecek
- * parametreyi temsil eder.(bu durumda /identify). Eğer bir %N- belirtirseniz bu N den sonraki
- * bütün parametleri içerir. Ayrıca kullanıcı nickname inin yerine %n kullanabilirsiniz.
-*/
-
-/* Standart aliases */
-alias "services" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "%1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "%1-";
-	};
-	type command;
-};
-
-alias "identify" {
-	format "^#" {
-		target "chanserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	format "^[^#]" {
-		target "nickserv";
-		type services;
-		parameters "IDENTIFY %1-";
-	};
-	type command;
-};
-
-/* Bu gerçek komut aliası için bir örnektir */
-/* Bu eşlem /GLINEBOT ile /GLINE <parametre> 2d vb... şeklindedir */
-alias "glinebot" {
-	format ".+" {
-		command "gline";
-		type real;
-		parameters "%1 2d Bu sunucuda botlara izin verilmemektedir, lütfen http://www.example.com/faq/123 sayfasından sss ı okuyunuz.";
-	};
-	type command;
-};
-
-
- /*
- * YENI: dosyalar {}
- * ESKI: include/config.h
- *
- * Bu blok MOTD gibi şeyleri yüklemek için IRCd varsayılan yolları
- * PID haricinde geçersiz kılar veya yazma/yükleme olarak dosyayı kendi ayarlar.
- * Bu bloğun varlığı bir UnrealIRCd kurulumuna destek sağlar.
- * -c ile kombine edildiğinde birden fazla komut seçeneğinin
- * çalışmasına izin verir.
- *
- * Her zamanki gibi bu gibi yakın yollar -c komut satırında belirtilmezse,
- * UnrealIRCd unrealircd.conf'u nerede bulunacağını dizinine göre yorumlar.
- */
-files
-{
-	/* Günün mesajı, oturum açan kullanıcılara gösterilir: */
-	/* motd ircd.motd; */
-
-	/*
-	 * Kısa MOTD. Eğer bu dosya varsa, MOTD yerine kullanıcıya
-	 * bu gösterilecektir. Yinede kullanıcılar /MOTD komutu kullanarak
-	 * tam MOTD içeriğini görebilecekler.
-	 */
-	/* shortmotd ircd.smotd; */
-
-	/* Operatör olduğunda gösterilir. /OPER 'liğe yükselmiş */
-	/* opermotd oper.motd; */
-
-	/* Servislere MOTD ekler. */
-	/* svsmotd ircd.svsmotd; */
-
-	/* Bot MOTD */
-	/* botmotd bot.motd; */
-
-	/* /RULES üzerinde gösterilir */
-	/* rules ircd.rules; */
-
-	/*
-	 * IRCd'nin bazı değerlerinin nerede olduğunu gösterir.
-	 * Bu değerler kalıcı olarak saklanır.Sunucu yeniden başlatıldığında 
-	 * ise bu değerleri yeniden yükleyecektir.
-	 */
-	/* tunefile ircd.tune; */
-
-	/* IRCd pidini nerede kaydedildiğini gösterir. IRCd tarafından yazılabilir olmalıdır. */
-	/* pidfile ircd.pid; */
-};
-
-/*
- * ESKI: tld {}
- * YENI: T:Line
- * Bu istemcilerin hostmaskesine bağlı olarak farklı 
- * motd ve rules dosyaları belirler.
- * Sözdizimi aşağıdaki gibidir: 
- * tld {
- *    mask (ident@host);
- *    motd "(motd dosyası)";
- *    rules "(rules dosyası)";
- * };
- */
-
-tld {
-	mask *@*.fr;
-	motd "ircd.motd.fr";
-	rules "ircd.rules.fr";
-};
-
-/* not: Bütün istemciler için aynı motd/rules (ircd.motd, ircd.rules) dosyaları 
- * görüntületmek istiyorsanız sadece yukarıdaki örnek bloğu silebilirsiniz.
- */
-
-/*
- * YENI: ban nick {}
- * ESKI: Q:Line
- * Nir nickname yasaklar, bundan doalyı kullanılamaz.
- * Sözdizimi aşağıdaki gibidir:
- * ban nick {
- *	mask "(yasaklanak nick)";
- *	reason "(neden)";
- * };
-*/
-ban nick {
-	mask "*C*h*a*n*S*e*r*v*";
-	reason "Servisler için ayrılmıştır";
-};
-/*
- * YENI: ban ip {}
- * ESKI: Z:Line
- * Ağa bağlanan bir ip yi yasaklar.
- * Sözdizimi:
- * ban ip { mask (ip adresi/hostmask); reason "(neden)"; };
-*/
-ban ip {
-	mask 195.86.232.81;
-	reason "Bağlı olmayan sunucu";
-};
-/*
- * YENI: ban server {}
- * ESKI: Server Q:Line
- * Ağa bir sunucunun bağlanmasını devredışı kılar.
- * eğer sunucu uzak bir sunucuya bağlanmışsa, yerel sunucunun
- * ağdan bağlantısı kesilir.
- * Sözdizimi aşağıdaki gibidir:
- * ban server {
- *	mask "(sunucu ismi)";
- *	reason "(neden)";
- * };
-*/
-
-ban server {
-	mask eris.berkeley.edu;
-	reason "Defol buradan.";
-};
-/*
- * YENI: ban user {}
- * ESKI: K:Line
- * Kullanıcının belirtilen kesin bir mask ile sunucuya bağlanmasını engeller.
- * Sözdizimi:
- * ban user { mask (hostmask/ip adresi); reason "(neden)"; };
-*/
-
-ban user {
-	mask *tirc@*.saturn.bbn.com;
-        reason "Idiot";
-};
-
-/*
- * YENI: ban realname {}
- * ESKI: n:Line
- * Kullanılan kesin bir realname i yasaklar.
- * Sözdizimi:
- * ban realname {
- *	mask "(real name)";
- * 	reason "(neden)";
- * };
-*/
-
-ban realname {
-	mask "Swat Team";
-	reason "mIRKFORCE";
-};
-
-ban realname {
-	mask "sub7server";
-	reason "sub7";
-};
-
-/*
- * BUTUN BANLAR İÇİN NOT, ilave girdiler için tekrarlanabilir!
- * 
- * YENI: except ban {} 
- * ESKI: E:Line
- * Bu yasaklanmamanızı sağlar.
- * Sözdizimi:
- * except ban { mask (ident@host); };
- * Farklı hostlar için istediğiniz kadar except ban {}
- * bloğunu tekrarlayın.
- */
-
-except ban {
-	/* stskeeps i yasaklama*/
-	mask           *stskeeps@212.*;
-};
-
-/*
- * YENI: deny dcc {} 
- * ESKI: dccdeny.conf
- * Dcc gönderimlerini bloklamak için kullanılır..Virüsler
- * dursa iyi olur. 
- * Sözdizimi: 
- * deny dcc 
- * { 
- *   filename "bloklanacak dosya (örnek, *exe)";
- *   reason "neden";
- * };
- */
-deny dcc {
-	filename "*sub7*";
-	reason "Muhtemek Sub7 Virüsü";
-};
-
-/*
- * ESKI: deny channel {}
- * YENI: N/A (NEW)
- * Girilen kanalları bloklar.
- * Sözdizimi:
- * deny channel {
- * 	channel "(kanal)";
- * 	reason "neden";
- *	class "clients"; (isteğe bağlı)
- * };
-*/
-deny channel {
-	channel "*warez*";
-	reason "Warez yasaktır";
-	class "clients";
-};
-
-/*
- * YENI: vhost {}
- * ESKI: Vhost.conf file
- * Oper olmayan kullanıcılar için sahte ip hazırlar, veya
- * tembellik yaparak /sethost kullanmayan operler içindir :P
- * Sözdizimi:  
- *   vhost { 
- *       vhost (vhost.com); 
- *       from {
- *            userhost (kullanılacak ident@host);
- *       };
- *       login (login ismi);
- *       password (şifre);
- *   };
- *        ardından bu vhostu kullanmak için, IRC de /vhost (login) (şifre) yapın
- */
-vhost {
-	vhost           i.hate.microsefrs.com;
-	from {
-		userhost       *@*.image.dk;
-	};
-	login           stskeeps;
-	password        moocowsrulemyworld;
-};
-
-/* Diğer yapılandırma dosyalarını dahil edebilirsiniz */
-/* include "klines.conf"; */
-
-/* Ağ yapılandırması */
-set {
-	network-name 		"ROXnet";
-	default-server 		"irc.roxnet.org";
-	services-server 	"services.roxnet.org";
-	stats-server 		"stats.roxnet.org";
-	help-channel 		"#ROXnet";
-	hiddenhost-prefix	"rox";
-	/* prefix-quit 		"no"; */
-	/* Gizleme anahtarları ağ üzerindeki bütün sunucularda aynı olmalı.
-	 * Bu anahtarlar maskeli hostlar yaratmak ve bunları saklamak için kullanılır.
-	 * Anahtarlar 5-100 karakterlik (10-20 karakter yeterli) 3 rastgele diziden oluşmalı ve 
-	 * küçük harf (a-z), büyük harf (A-Z) ve rakamlardan (0-9) meydana gelmelidirler.. [ilk örneğe bakınız].
-	 * IPUCU: './unreal gencloak' Unreal sizin için rastgele 3 adet dizin oluşturur.
-	 *       Bunu NIX üzerinde çalıştırabilirsiniz.
-	 */
-	cloak-keys {
-		"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
-		"and another one";
-		"and another one";
-	};
-	/* on-oper host */
-	hosts {
-		local		"locop.roxnet.org";
-		global		"ircop.roxnet.org";
-		coadmin		"coadmin.roxnet.org";
-		admin		"admin.roxnet.org";
-		servicesadmin 	"csops.roxnet.org";
-		netadmin 	"netadmin.roxnet.org";
-		host-on-oper-up "no";
-	};
-};
-
-/* Sunucunun kendine özgü yapılandırması */
-
-set {
-	kline-address "bunu.email.olarak.ayarlayın";
-	modes-on-connect "+ixw";
-	modes-on-oper	 "+xwgs";
-	oper-auto-join "#opers";
-	options {
-		hide-ulines;
-		/* Eğer isterseniz identd kontrolünü buradan aktif edebilirsiniz */
-		/* identd-check; */
-		show-connect-info;
-	};
-
-	maxchannelsperuser 10;
-	/* /quit mesajının görüntülenebilmesi için, bir kullanıcının sunucuya bağlı kalması gereken süre
-	 * Umarız spamleri durdurmak için yardım eder */
-	anti-spam-quit-message-time 10s;
-	/* Bütün çıkışlarda değişmeyen bir çıkış mesajı yaratır - anlamı yerel sunucuda
-           ısmarlama çıkışlara izin verilmemesidir */
-	/* static-quit "Client quit";	*/
-
-	/* Ayrıca bu seçeneğin açıklama satırlarını kaldırıp 'yes' diyerek bütün kanaldan ayrılma mesajlarını,
-	 * bloklamış veya belirli bir diğer metini bunun için kullanabilirsiniz. (örnek: "Bye bye!") Her zaman kanaldan 
-       * ayrılma mesajı olarak kullanılır */
-	/* static-part yes; */
-
-	/* Operlerin sadece belirli istatistikleri görüntüleyebilmesini sağlar, bütün istatistikler için * kullanın,
-	 * bütün istatistikleri görebilmeleri için gözardı edin. Full liste için '/stats' yapınız.
-	 * Bazı yöneticiler normal kullanıcıların 'kGs' istatistiklerine ulaşmasını istemeyebilir.
-	 */
-	oper-only-stats "okfGsMRUEelLCXzdD";
-
-	/* Throttling: Bu örnek bir hosta 60 saniye içerisine yanlızca 3 bağlantı imkanı sağlar. */
-	throttle {
-		connections 3;
-		period 60s;
-	};
-
-	/* Anti flood koruması */
-	anti-flood {
-		nick-flood 3:60;	/* Her 60 saniyede 3 nick değişikliği (varsayılan) */
-	};
-
-	/* Spam filtresi */
-	spamfilter {
-		ban-time 1d; /* spamfilter ile bir *line yasağının varsayılan devaö süresi */
-		ban-reason "Spam/Advertising"; /* varsayılan neden */
-		virus-help-channel "#help"; /* 'viruschan' eylemi için kullanılacak kanal */
-		/* except "#help"; spam filtreden muaf tutulacak kanal */
-	};
-};
-
-/*
- * Sorununuz veya daha fazla yardımamı ihtiyacınız var?
- * 1) www.vulnscan.org/UnrealIRCd/unreal32docs.tr.html
- * 2) www.vulnscan.org/UnrealIRCd/faq/ <- sorularınızın %80 ini kapsamakta!
- * 3) Eğer probleminiz hala devam ediyorsa irc.unrealircd.org sunucusu #unreal-support kanalına girebilirsiniz
- *    DÖKÜMANTASYON ve FAQ kısmını okumanızı gerekli gördüğümüzü belirtiyoruz!
- */

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/technical/005.txt

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

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,160 +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).
-
-NICKIP        This token indicates that a (standard) base64 encoded IP address is included
-              in the NICK command. The IP is in binary network byte order formated and
-              encoded using the standard base64 algorithm. '*' is used if no IP is available.
-
-NICKCHARS     This specifies a list of language characters that are allowed in nicks.
-              USMARC codes are used, with a suffix if needed. See src/charsys.c for the full
-              list (ctrl+f, static LangList) of possible languages (2nd column).
-              The items in the list sent as NICKCHARS=.. must always be sorted.
-              If a server sends NICKCHARS= and if the remote parameters do not match the
-              charsets in use locally, then the server link is rejected.
-
-CHANMODES     Like CHANMODES from the 005 numeric. Useful to see which channel modes are
-              supported/used, and can also be used to properly eat parameters in parameter
-              modes in the MODE command (for eg: +jk 1:1 a).
-
-EAUTH         Early Authorization. This makes it possible for servers to authenticate each
-              other before the regular SERVER command. Needs to be done prior to using the
-              SERVERS token, and possibly other tokens or commands in the future. Hence,
-              is recommended to be sent as first (or early) PROTOCTL token. Note also that
-              the PASS command should be sent prior to this PROTOCTL token.
-              EAUTH=my.server.name[,options]
-
-SERVERS       Informs the other server about the other servers (numerics) on this network
-              (including our own numeric).
-              Syntax: SERVERS=numeric1,numeric2,numeric3,etc
-
-ESVID         This token indicates that the traditional services stamp value may take any
-              arbitrary value for the SVID field, such as an account name or other unique
-              identifier, including a traditional timestamp value.

doc/technical/serverprotocol.html

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

doc/technical/token.txt

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

doc/technical/vl.txt

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

doc/translations.txt

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

doc/win32-compile-guide

@@ -0,0 +1,16 @@
+Compiling UnrealIRCd 3.1.x for Windows
+--------------------------------------
+This document assumes you have a working build environment for
+Visual Studio .NET or Visual Studio 6.0. Other versions may work
+as well, but have not been tested.
+
+1. Copy include/win32/settings.h and setup.h to include/
+2. Copy extras/regex/regex.h to include/
+3. Copy extras/regex/regex.c to src/
+4. Edit include/settings.h to your liking (pretty much change DOMAINNAME)
+5. Unzip src/win32/unrealircd.bmp.gz
+6. Execute "nmake makefile.win32"
+
+Congratulations, you should have a functioning win32 binary.
+
+--Luke (luke@unrealircd.com)

dynconf

@@ -0,0 +1,21 @@
+             Dynamic Configuration Guide
+
+- Edit ircd.conf to correctly reflect your server configuration.
+
+- Edit networks/unrealircd.conf to suit you. If you're going
+to use your own network file (encouraged), change the "Include"
+line to point to your own network file.
+
+- Assuming you do want your own network file, copy template.network
+in networks/ to yourircnet.network. Edit it to your liking.
+
+If you've completed all these steps *correctly* your server should
+start up without any problems. If there are errors, there is an
+extremely high chance that it's due to user configuration error.
+Please read the documentation and check over your configuration files
+before contacting us.
+
+If the problem persists, and you cannot fix it, email luke@unrealircd.com
+or come on irc.ircsystems.net and /join #unreal-support.
+
+- Luke (luke@unrealircd.com)

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,128 +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;
-
-ModuleHeader MOD_HEADER(defizzer)
-  = {
-	"defizzer",	/* Name of module */
-	"$Id$", /* Version */
-	"de-Fizzer", /* Short description of module */
-	"3.2-b8-1",
-	NULL 
-    };
-
-DLLFUNC int MOD_INIT(defizzer)(ModuleInfo *modinfo)
-{
-	bcopy(modinfo,&DefizzerModInfo,modinfo->size);
-	LocConnect = HookAddEx(DefizzerModInfo.handle, HOOKTYPE_PRE_LOCAL_CONNECT, h_defizzer_connect);
-	return MOD_SUCCESS;
-}
-
-DLLFUNC int MOD_LOAD(defizzer)(int module_load)
-{
-	return MOD_SUCCESS;
-}
-
-
-DLLFUNC int MOD_UNLOAD(defizzer)(int module_unload)
-{
-	HookDel(LocConnect);
-	return MOD_SUCCESS;
-}
-
-static void ban_fizzer(aClient *cptr)
-{
-	int i;
-	aClient *acptr;
-	char hostip[128], mo[100], mo2[100];
-	char *tkllayer[9] = {
-		me.name,	/*0  server.name */
-		"+",		/*1  +|- */
-		"z",		/*2  G   */
-		"*",		/*3  user */
-		NULL,		/*4  host */
-		NULL,
-		NULL,		/*6  expire_at */
-		NULL,		/*7  set_at */
-		NULL		/*8  reason */
-	};
-
-	strlcpy(hostip, Inet_ia2p(&cptr->ip), sizeof(hostip));
-
-	tkllayer[4] = hostip;
-	tkllayer[5] = me.name;
-	ircsprintf(mo, "%li", 86400 + TStime());
-	ircsprintf(mo2, "%li", TStime());
-	tkllayer[6] = mo;
-	tkllayer[7] = mo2;
-	tkllayer[8] = "Fizzer";
-	m_tkl(&me, &me, 9, tkllayer);
-	return;
-}
-
-DLLFUNC int h_defizzer_connect(aClient *sptr)
-{
-	char user[USERLEN + 1];
-	char *infobackup;
-	char *s1, *s2;
-
-	/*
-	 * Algorithm is basically like this, inspired by Zaphod:
-	 * Exchange first word with second in realname, prepend with 
-	 * ~, then add in second word and first word upto limit of username.
-	 * sounds fun?
-	*/
-	infobackup = strdup(sptr->info);
-	if (!(s1 = strtok(infobackup, " ")))
-	{
-		free(infobackup);
-		return 0;
-	}		
-	if (!(s2 = strtok(NULL, " ")))
-	{
-		free(infobackup);
-		return 0;
-	}		
-	snprintf(user, sizeof(user), "%s%s%s", (IDENT_CHECK ? "~" : ""), s2, s1);
-	free(infobackup);	
-	if (!strcmp(user, sptr->user->username))
-	{
-		ircstp->is_ref++;
-		ban_fizzer(sptr);			
-		return exit_client(sptr, sptr, &me, "Fizzer client");
-	}	
-	return 0;
-}

extras/extras.txt

@@ -1,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.