unreal-users

[Unreal-users] config question

[pat x. <pat...@ho...>]

hi,
=20
I have this idea and I will need to run an irc server (or at least some sor=
t of a chat server).
=20
now my question is,=20
=20
is there a way to run a simplistic version of this irc server. All I want a=
 user to do is to chat, no commands, nothing just type in words. so no /who=
 etc...
=20
so is there a way to remove/disble all the extra irc commands?
=20
thank you.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/=

[Unreal-users] Unreal3.2.5 released

[Bram M. (Syzop) <sy...@un...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A new Unreal3.2* version is out: 3.2.5

This release comes with several new features such as CGI:IRC host spoofing and
time synchronization support. It also fixes a couple of important bugs.
This is a recommended release.

I would like to use this opportunity to do a call for help for UnrealIRCd, or
more specifically: Unreal3.3*. A wiki for this has been created at
http://dev.unrealircd.com/wiki/
Since we need fresh blood in the team, we are organizing a coders contest, for
more info check out http://dev.unrealircd.com/wiki/Coders_Contest

Special thanks for helping with this 3.2.5 release go to our testers team
(and everyone else who tested) which helped testing the 3.2.5 release candidates,
and to Dukat for recoding the testers site when we badly needed it.

Release notes follow..

 Unreal3.2.5 Release Notes
 ==========================

 If you are upgrading, please take a minute to read these release notes.
 *NIX Users: PREFIX_AQ is now enabled by default. See under 'CHANGED' below.

 ==[ GENERAL INFORMATION ]==
 - If you are upgrading on *NIX, make sure you run 'make clean' and './Config'
   first before doing 'make'
 - The official UnrealIRCd documentation is doc/unreal32docs.html
   online version at: http://www.vulnscan.org/UnrealIRCd/unreal32docs.html
   FAQ: http://www.vulnscan.org/UnrealIRCd/faq/
   Read them before asking for help.
 - Report bugs at http://bugs.unrealircd.org/
 - When upgrading a network, we assume you are upgrading from the previous
   version (3.2.4). Upgrading from 3.2.3 is ok as well.
   However, if you have a network running with servers that are several versions behind
   (eg: 3.2.1) then you might experience small (desynch) problems.
   Please also minimize the time you have multiple versions running, a few days or
   one week is generally not a problem, but having mixed versions on a network for several
   weeks or months is not recommended.

 ==[ NEW ]==
 - CGI:IRC Host spoofing support. This means you can mark certain CGI:IRC gateways
   as trusted, and then the IRCd will show the real IP/host everywhere for those
   users, instead of the IP/host of the CGI:IRC gateway. See docs section 4.36.
 - Time synchronization support. This is enabled by default and will synch the IRCd
   clock when Unreal is started. This should get rid of most time differences, though
   the clock can still be off 1-3 seconds. If for some reason no reply from the time
   servers is received within 3 seconds, then the IRCd will continue to boot as usual.
   Several set::timesynch::* settings have been added, including set::timesynch::enabled
   which you can set to 'no' to disable time synching (eg: because you already run ntpd).
 - NAMESX support. This (mostly) fixes a long-standing IRC protocol bug. If, for
   example, a user was +vo and then deops (-o), other clients could not always
   know the user was then still +v, now they can. Supported by XChat and newest mIRC.
 - Chained SSL certificates support
 - Russian doc/example.ru.conf and Turkish doc/unreal32docs.tk.html

 ==[ CHANGED ]==
 - PREFIX_AQ (the ~ and & symbols for +q and +a) are now ENABLED BY DEFAULT on *NIX.
   They have always been enabled on Windows, so it made sense to do the same for *NIX.
   Pretty much all major clients support it now (mIRC, xchat, irssi, epic, PJIRC,
   CGI:IRC, etc).
 - If DNS info (*NIX: /etc/resolv.conf, Win: registry) is updated, a '/REHASH -dns'
   now rereads this info, no restart needed anymore.
 - me::numeric can now be changed without a restart, if no servers are linked.
 - Improved windows crash info: we now create minidumps, this should aid debugging.
 - '/quote dns i' (as an oper) now shows nameserver info again
 - Local oper may now use /TRACE
 - If channel is +m but -t, you now need at least voice (+v) to change the topic.
 - When checking if someone is banned, we now always verify bans against the cloaked host,
   even if the user has a vhost and the cloaked host is not visible / unused.
 - Extra binary compatibility checks: (gcc) compiler version
 - Allow /*LINE'ing of literalident@* (eg: gline clones@*). Things like *clones@* are
   still denied though, and this will not be changed. Use services AKILL instead.
 - Command aliases: made empty parameters work if the alias allows it (eg, the alias
   uses .* as a regex and not .+)
 - Moved another 2K lines from core to modules, this means 31K lines are now in modules
   and can be upgraded on the fly.
 - Real Command Aliases: This makes it possible to, for example, alias '/GLINEBOT' to
   'GLINE <param> 2d Bots are not permitted on this network, etcetc'. For more information,
   see the docs on the alias block and/or search for "glinebot" in doc/example.conf.
 - /etc/hosts is no longer checked (it never did before 3.2.3 either)

 ==[ MAJOR BUGS FIXED ]==
 - Spamfilter was not always working properly
 - MS Visual studio 2005 (8.x) was unable to compile Unreal and/or caused crashes
 - Certain IPv6 listen blocks could crash the ircd on-boot/on-rehash

 ==[ MINOR BUGS FIXED ]==
 - "Looking up your hostname" message was missing if set::options::show-connect-notice
   was enabled (other messages, like "looking up ident" were shown, however)
 - It was sometimes impossible to update a link { } block: all old settings would still
   be used, this happened if connfreq was low. This might also have caused crashes.
 - Netsynch problem, which could cause the wrong modes to be applied to a channel in
   some rare cases.
 - Setting set::maxdccallow to 0 (or lower) still allowed one entry to be added
 - Spamfilter oversized-checking is no longer done when removing a spamfilter
 - Operator count bug (there might still be others...)
 - Some chinese-* charsets could not be selected individually
 - No longer requiring a C++ compiler (was caused by resolver in 3.2.4)
 - Added workaround for "make: Permission denied" bug in some FreeBSD's

 ==[ REMOVED ]==
 - MS Visual Studio 6 support, but this did not work anymore anyway...

 ==[ KNOWN ISSUES ]==
 - Windows 2003: Crashes directly on-boot have been reported, while other W2003 servers
   work perfectly fine (including the one we used for testing). No pattern in this has
   been found yet, but the bug is somewhere in the resolver (c-ares).
 - 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.
 - Regexes: Possessive quantifiers such as, for example, "++" (not to be confused with "+")
   are not safe to use, they can easily freeze the IRCd.
 - Windows: The /RESTART command will work, but the second time you do a /RESTART the
   IRCd will "crash" with a dialogbox.

 ==[ CHANGELOG ]==
 Changes since 3.2.4:
 - Updated autoconf/configure.in to make newer autoconf's work (developers only), reported
   and patch provided by Xuefer (#0002798). Also rebuilt ./configure from configure.in with
   autoconf 2.59 from my own machine.
 - Updated autoconf/configure.in again (does not produce different ./configure output)
 - When set::options-show-connect-notice was enabled the "*** Looking up your hostname..."
   message was not being shown (all others were). Reported by fbi (#0002820).
 - Updated win32 compiling instructions; mention the free MS stuff that can be used to compile
   UnrealIRCd (untested though).
 - Added CGI:IRC host spoofing support. This means you can mark specific CGI:IRC gateways as
   "trusted" and the IRCd will show the users' _real_ host/ip everywhere on IRC, instead of the
   host/ip of the CGI:IRC-gateway.
   To do so you must set 'realhost_as_password' to 1 in your cgiirc.conf. And add the
   CGI:IRC gateway(s) you fully trust to set::cgiirc::hosts.
 - Fixed win32 compile problem due to CGI:IRC support, reported by therock247uk (#0002821).
 - Redid whole CGI:IRC support. Configuration is now moved to cgiirc { } blocks.
   We now support the webirc ('webirc_password' in CGI:IRC) method, which is kinda superior
   to the older method ('realhost_as_password').
   See the Unreal documentation (section '4.36 - Cgiirc Block') for details on how to configure.
 - Changed quoting color in unreal32docs.. looks better now IMO (only English docs updated).
 - Fixed *BSD compile problem caused by changes of above, reported by 3rror (#0002823).
 - Added error message if c-ares failed to initialize, might help in case something is buggy
   (either with Unreal or the OS/environment).
 - Fixed (serious) bug in CGI:IRC code, IP's were often not right, reported by 3rror (#2824).
 - Fixed bug in currently unused code, reported by DeadNotBuried (#0002835).
 - Modulized NAMES command (can now be upgraded on the fly, if ever needed).
 - Added NAMESX support, seeing both mIRC (6.17) and XChat support this. What this does is
   send all rights of all users on the channel in the NAMES reply (eg: @+Syzop if the user is +ov)
   instead of only the highest one (@Syzop in previous example). We only do so if the client
   explicitly requested this via a NAMESX in a PROTOCTL message (eg: 'PROTOCTL NAMESX').
   Note that there is a glitch: since most clients only send the PROTOCTL NAMESX after they
   see NAMESX listed in the 005 announce message this has the effect that if there are
   set::auto-join channels present (where users are automatically joined to by the server) the
   extended NAMES reply will not be sent for those channels, because from the IRC server' point
   of view the join happened before the PROTOCTL and hence it does not know the client wanted
   NAMESX at that point (the result is not catastrophic: the old-style NAMES is sent for those
   channels). Anyway, for all non-autojoin channels this works great. So still worth adding IMO.
   Originally suggested in #0000606.
   Side note: this does not mean we dropped the idea of (also) having a challenge-response
   system for good ;).
 - Updated win32 makefile due to m_names modulization, reported by Trocotronic (#0002838).
 - Actually committed src/modules/m_names.c... This tends to help with the compiling process.
 - Fixed possible netsplit problem (#0002790).
 - Partially redid m_message, moved some stuff to a subroutine, etc to avoid duplicate code
 - Rephrased/editted part of example.conf and unreal32docs to make it a littttttle bit easier
   for beginners / try to mention the FAQ a bit more explicitly.
 - CGI:IRC: gzlines, zlines, throttling, and unknown connect floods are now all checked for
   clients connecting trough a CGI:IRC gateway that is in cgiirc { }. This might also fix a bug
   where (g)zlines were not applied to CGI:IRC clients, reported by devil (#0002850).
 - Changed default PREFIX_AQ behavior to ON instead of OFF. Since basically all major IRC
   clients support it now (mIRC, xchat, epic, eggdrop, Klient, PJIRC, irssi, CGI:IRC, etc).
   It has always been weird that win32 had it ON by default and *NIX OFF, anyway.
   Naturally this change will be mentioned clearly in next release notes.
 - Fixed (unimportant) DNS resolver problem if using some LAN domains with digits at end,
   reported by Bock (#0002843).
 - Added minidump support for crashes to aid debugging a bit.
 - Added chained SSL certificates support, patch provided by justdave (#0002848).
 - Local opers may now use /TRACE (local only), suggested by GSF19 (#0002365).
 - Removed some odd code causing a 'my port is' message to appear in (f.e.) syslog, reported
   by rsc (#0002853).
 - Fixed CHROOTDIR compilation problem, reported by toshio (#0002854).
 - Improved CHROOTDIR documentation in include/config.h
 - Added error if CHROOTDIR is defined but IRC_UID isn't (in include/config.h).
 - Hide stats request if requested by an U-lined client. Suggested by vonitsanet (#0002865).
 - Made it so if the channel is +m but -t, you need at least voice (+v) to change the topic.
   Reported by aquanight (#0002233).
 - Made the windows installer better compress things (SolidCompression=true), suggested
   by Trocotronic (#0002877).
 - Added support for URL redirections in curl (if version >=7.15.1), suggested by Trocotronic
   (#0002879).
 - Made doc/compiling_win32.txt a bit more ugly (mention that only vstudio 7.x actually works
   at this moment).
 - c-ares (currently, a forked off version) enhancements:
   - '/quote dns i' now shows the nameserver settings (which is taken from /etc/resolv.conf
     on *NIX, and from the registry on Windows)
   - We no longer depend on a C++ compiler (was useless c-ares dependency caused by libtool)
   - '/REHASH -dns' now rereads the resolver data from resolv.conf/registry, no IRCd restart
     needed anymore. It's currently kinda experimental however, but I *think* it will work ok.
   Unfortunately the above features required some ugly hacks if curl was enabled, so if you
   use curl (Remote includes), feel free to test on your OS (Linux, but especially FreeBSD
   and the other *NIXes) to see if things still compile (make clean; ./Config && make).
 - Made the IRCd calculate the cloaked host only once upon connect, and store (cache) it.
 - When checking if a user is banned, we always check the cloakhost too. Previously we could
   not do this if the user had a /VHOST (=a minority of the cases, but still...). In short,
   this is some extra protection to combat ban evasion.
 - Performance of is_banned() *slightly* improved (just 1-2 usec, but 7 usec if no bans).
 - [Module coders] For extban routines, we now offer a routine extban_is_banned_helper(buf)
   which can be used instead of the ban_realhost/etc static chars stuff, see
   extban_modeq_is_banned for a (real-life) example of how this is used.
 - [Services coders!] Added PROTOCTL CLK (requires NICKv2) which adds an extra field in the
   NICK command (when a user connects) right before the infofield (gecos).
   The added field contains the cloaked host, that is: the masked host if +x would have been
   set. This field is ALWAYS sent, regardless of whether the user is actually +x or not.
   Services can then store this field in memory, to know the host of the user if the user
   is set +x (+x-t). This is a (better) alternative to PROTOCTL VHP, with no race conditions,
   and avoids some other VHP problems.
   VHP will stay supported though... so it's not mandatory to switch over.
 - Fixed set::maxdccallow setting to <=0 still allowing one entry to be set, reported by
   RSCruiser (#0002883).
 - Fixed Microsoft Visual Studio 2005 (8.x) unable to compile, and, after fixing that, causing
   a lot of crashes. Both are now fixed. Reported by Zell, Yamake, and others (#2875, #2704).
   Fix provided by Xuefer. This also gets rid of some annoying and useless compile warnings
   as well. Also thanks to Zell for his help.
 - Fixed null pointer config parser crash, reported by alkalinex (#0002894).
 - Added compiler version checking to "module binary incompatability"-check. This should fix
   some more odd problems from people (eg: people switching from GCC 3.x to 4.x and wondering
   why they are crashing or getting other errors).
 - Module coders: For cloaking, added a new callback type CALLBACKTYPE_CLOAK_EX (which is an
   enhanced version of CALLBACKTYPE_CLOAK). This passes 'aClient *sptr, char *host' instead
   of only 'char *host' to the cloaking module, which can be useful if you need to cloak on
   something other than IP/host. Suggested by fez (#0002275).
   Module may still provide only CALLBACKTYPE_CLOAK though, in fact this is what the official
   cloaking module does. So no updating of cloaking modules needed.
   If you do write a module with the new *_EX callback, you only need the *_EX one and not
   the CALLBACKTYPE_CLOAK as well (though it's currently np if both are present).
   A side-effect of this "extra cloaking" callback is that we needed to change make_virthost()
   which now has an extra parameter in front, and another side-effect is that calling the
   CALLBACKTYPE_CLOAK may not work since only *_EX might be available. To my knowledge there
   are very few modules (only 1 I know) that will have a problem due to this, so sounds like
   an affordable tradeoff.
 - Updated sendnotice() so it sends a proper notice if the user is in pre-connect stage.
 - Fixed bug with chinese-* charsets not getting detected properly by config parser.
   Reported and patch provided by Xuefer (#0002891).
 - Made it so me::numeric can be changed (when not linked to any servers) so no server restart
   is needed anymore (#0002896).
 - set::ssl::egd does not require a parameter per-se (bug caused few days ago), reported
   by Trocotronic (#0002899).
 - (multiple?) IPv6 listen blocks could cause a crash in config parser. Reported by Robby22
   (#0002868).
 - Added error checking to (main) setuid/setgid calls.
 - Fixed implicit declaration compiler warning if compiling for ipv6.
 - Fixed some small memory leak on rehash.
 - Removed spamfilter-oversized-checking when trying to REMOVE one.. duh.. reported by satmd
   (#00029160).
 - Allow *lining of literalident@* such as clones@* (but not *clones@*), this is also as
   far as we want to go with regards to relaxing "too broad" checking... Just continue to use
   services AKILL for (other) "too broad cases", as many people (correctly) do. Change
   suggested by salama (#0002911).
 - Made empty command aliases work (no more "no text to send" error) if the alias finds it ok,
   which basically means if it allows .*. If you want to require a parameter, use .+ (or
   anything other in regex that requires at least one character). Suggested and patch provided
   by Nazzy (#0002722).
 - Fixed oper count bug which happened on /mode, this was our fault (can't blame services in
   this case ;p). Reported by KnAseN and many others (#0002581).
   There might still be other operator count bugs, but these are triggered by a different bug
   and may or may not be caused by services.
 - Added MINIMAL time synchronization support. This is enabled by default and will try to
   synchronize the IRCd clock (TSOffset) with a few good time servers. It currently only does
   this on-boot, but it will hopefully help a lot of people with most of their time differences.
   I still keep recommending anyone who can to run proper time-synchronization software such as
   ntpd/ntpdate on their servers.
   To disable time synchronization (eg: because you are already running ntp), you can simply
   set set::timesynch::enabled to no.
   The boot timeout for the timeserver response (=causes boot delay) can be configured via
   set::timesynch::timeout and is set to 3 seconds by default (range is 1s-5s), there should
   be no reason to change this.
   The time server can be configured by setting set::timesynch::server, the default is to
   use 3 time servers on 3 continents (US, EU, AU) which should be sufficient for anyone but
   if you got a good one near you you can use that one instead.
   The time protocol we use is (S)NTP v4.
 - Fixed some compile warnings for Windows
 - Updated windows compile instructions again.
 - Updated release notes
 - Added 'real' aliases, this are aliases that map to real commands, so you can for example
   map the command '/GLINEBOT <x>' to 'GLINE <x> 2d Bots are not allowed on this server, blabla'.
   See the documentation on the alias block for more information. doc/example.conf contains an
   example as well (search for "glinebot").
 - Modulized: badwords system (src/badwords.c is now gone) and StripColors/StripControlCodes
   to m_message, multiple netsynch routines to m_server, send_list to m_list, a certain mode
   routine to m_svsmode, all /MSG IRC.. webtv stuff to src/modules/webtv.c which is compiled
   with m_message.
   This means another ~1500 lines of code are now in modules (and thus can be upgraded on
   the fly), which brings the total of modulized lines at 32K.
 - Fixed compilation error on FreeBSD and others caused by timesynch, reported by tigra
   (#0002921).
 - Fixed win32 compile problem cause by timesynch.
 - Updated release notes: more modulization and real command alias support.
 - Fixed crash in /STATS Z (possibly rare), reported by yasinbey (#0002929).
 - Win32 makefile/installer updates for new curl/ssl
 - Updated versions everywhere, bumped protocol to 2308
 ** 3.2.5-rc1 release **
 - Added doc/example.ru.conf, translated by Bock.
 - Deal with unsupported regexes added by remote servers (possible crash otherwise)
 - Fixed crash problem on win32 if TKL times were <0. Obviously it's hard to protect from such
   invalid server traffic, but figured in this case it might be a good idea since *NIX does
   not crash.
 - Made a note about possessive quantifiers, they are scary :P.
 - Made the "voice needed when channel is +m but -t" actually work, reported by Trystan and
   Ron2K (#0002940).
 - #undef STRIPBADWORDS did not work, reported by penna (#0002944).
 - Made the resolver no longer check /etc/hosts, since that's how it used to be and should be.
   Saves some useless file reads.
 - Fixed compile (well, configure) problem on FreeBSD if compiling with remote includes
   enabled. Reported by psadi (#0002941).
 - Added translated Turkish docs (doc/unreal32docs.tk.html), translated by tt` and Timaeus.
 - Fixed problem with IRCd using old link block settings if using a low connfreq, this made it
   for example near-impossible to remove autoconnect for such a server. Reported by mixx941
   (#0002836).
 - Fixed problem if c-ares library is already installed system-wide, reported by Trystan.
 - Updated release notes a bit (will be updated more later): backrefs (\1) in regexes are
   kinda scary, or at least at the moment.
 - Removed PATCH5 from module version incompatibility system, so it can be used if we ever
   need to update stuff and not enforce modules to recompile.. Might be useful one day ;p
 - Updated list of donators
 ** 3.2.5-rc2 release **
 - Updated release notes, bleh.. I forgot :P
 - Got rid of qline notice that could happen if using services holds (semi-race condition),
   reported and bugfix provided by tabrisnet (#0002950).
 - Made opers with can_override able to change the topic again if not chanop and banned/+m-t,
   reported by vonitsanet (#0002952).
 - Disable /RESTART if running chrooted since that won't work anyway, reported by kayelem
   (#0002956).
 - On certain (newer?) FreeBSD's you get "make: Permission denied" after ./Config, but when
   you do 'cd ..' and then 'cd -' again, make works just fine. This is going to be the most
   stupid workaround in history... Reported by vonitsanet and others (#0002926).
 ** 3.2.5-rc3 release **
 - Updated doc/technical/005.txt
 - Mass version change (no code changes)
 ** 3.2.5 release **

As usual, you can get it from http://www.unrealircd.com/

All our releases are PGP signed (well, with GPG) with our releases key:
rel...@un... [0x1C8A554E] which you can grab from
http://www.unrealircd.com/pgp/release_key.asc
This is the same release key that was used for signing 3.2.3 and 3.2.4.
More info about this is shown when downloading.

We no longer provide MD5/SHA1 checksums because we feel they are too insecure.

Thank you for using UnrealIRCd!

	The UnrealIRCd Team.

- --
Bram Matthys
Software developer/IT consultant        sy...@vu...
PGP key:                       www.vulnscan.org/pubkey.asc
PGP fp: 8DD4 437E 9BA8 09AA 0A8D  1811 E1C3 D65F E6ED 2AA2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFElGvU4cPWX+btKqIRAmZ1AJ44Mp0/Mndp3639zDySnd8TPL7T9QCfQW8Q
qKImAnOUCdt5b21TM8eM/yk=
=O1P3
-----END PGP SIGNATURE-----

[Unreal-users] (no subject)

[Robert T. <mo...@ms...>]

ok my names robert and i have a small issue with linking that i cant seem to 
solve no matter what i try each general time i try to connect to his server 
it says no response from blah blah w/e
the firewall is open for those ports his ip is on the allow list what are 
some possible reasons for this and is it fixable lol??

[Unreal-users] Unreal3.2.4 re-released

[Bram M. <sy...@un...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I regret to inform you that we had to re-release 3.2.4 because the
'?' wildcard was not working (in for example bans).
Apparently despite numerous testing and hundreds of downloads of the last
release candidate, this bug simply slipped trough.

All files on unrealircd.com and it's mirrors have been replaced with the fixed
version.

If you have downloaded 3.2.4 before Sunday February 5 18:00 GMT, then you
probably have the broken version without the fix.

To check if you are using the old version, type '/quote INFO' on IRC and pay
attention to the numbers in the ReleaseId line (=almost the last line):
1.1.1.1.2.21 = bad version (*NIX)
1.1.1.1.2.22 = fixed version (*NIX)
1.1.1.1.2.1.2.1.2.2234.2.449 = bad version (Windows or *NIX CVS)
1.1.1.1.2.1.2.1.2.2234.2.454 = fixed version (Windows or *NIX CVS)

*NIX people: warning regarding version numbers:
 If someone applied the patch for *NIX (see below) the version number will not
 change. So basically if you have .22 you know you are ok, but if you get .21
 then you are either not ok or the admin patched it already.
 In that case, you can try this to determine if you have the fix or not:
 1. go to your Unreal3.2 directory
 2. type: grep -F "(*m != '?')" src/match.c
 3. if it returns 2 lines then you got the fix, if it returns 1 then not.

For everyone who already downloaded the old 3.2.4:
Windows:
 redownload from http://www.unrealircd.com/?page=downloads
*NIX:
 Either redownload it too, OR (much faster) do this:
 1. go to your Unreal3.2 directory
 2. download http://www.unrealircd.com/downloads/324.wildcard.patch
 3. type: cat 324.wildcard.patch|patch -p0
 4. type: make && make install
 5. restart the ircd

 Or, all in two lines (except the restart), from your Unreal3.2 directory:
 wget http://www.unrealircd.com/downloads/324.wildcard.patch
 (cat 324.wildcard.patch|patch -p0) && make && make install

 This should only take a few seconds, but the main annoyance is that
 you will have to restart the ircd in order for the fix to take effect.

We did not change the version number, so people will not have to recompile
their modules. I understand this has it's own advantages/disadvantages.

We are really sorry for all the inconvenience.

	The UnrealIRCd Team.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFD5lGo4cPWX+btKqIRAi+wAJ99UycY9iTEBnq1UauOrwBVIBFQJwCeOFun
nOkWCEoaYlht36bsyBPkF2w=
=avn1
-----END PGP SIGNATURE-----

[Unreal-users] Unreal3.2.4 released

[Bram M. <sy...@un...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Finally, after 11 months, there's a new 3.2* stable release: 3.2.4

Our previous release, 3.2.3, was a successful one and has in fact been
downloaded over 130.000 times. However, as usual, new bugs are
discovered and other (older) issues needed to be corrected.

This new release comes with tons of bugfixes (of which some major),
and is a RECOMMENDED upgrade. Besides all the bugfixes, there are
also a few new features.

We've been experimenting with public Release Candidates (RC's);
there have been 3 rc's before this 3.2.4 release, and the rc's
have been downloaded ~1700 times total.
We would like to thank both our Unreal Testers Team and everyone
of the public that tested the 3.2.4-rc's for helping us to make
this a stable release.

If you wonder about future UnrealIRCd development (like Unreal3.3*):
another mail will be sent out about that in a few weeks, presenting
our future plans for UnrealIRCd, and and how people (coders, doc
writers, etc) can contribute.
Unfortunately we've simply been too busy with the current release
to finish off our (revised) development plan at the same time as
this release. Anyway, more info on that soon.

For now, happy upgrading! ;)

Unreal3.2.4 Release Notes
==========================

==[ GENERAL INFORMATION ]==
- - If you are upgrading on *NIX, make sure you run 'make clean' and './Config'
  first before doing 'make'
- - The official UnrealIRCd documentation is doc/unreal32docs.html
  online version at: http://www.vulnscan.org/UnrealIrcd/unreal32docs.html
  FAQ: http://www.vulnscan.org/UnrealIrcd/faq/
  Read them before asking for help.
- - Report bugs at http://bugs.unrealircd.org/
- - When upgrading a network, we assume you are upgrading from the previous
  version (3.2.3). If you have a network running with servers that are several
  versions behind (eg: 3.2.1) then you might experience (desynch) problems.
  Please also minimize the time you have multiple versions running, several days
  is not a problem, but having mixed versions on a network for weeks or months
  is not recommended.

==[ NEW ]==
- - Spamfilter: Added 'warn' target which is basically the same as 'block' except it
  does not block ;). It simply sends a numeric to the user saying the command has been
  processed, but a copy has been sent to ircops (which receive a spamfilter notice).
  Example usage: /spamfilter add p warn - Testing_mirc_decode_filter \$decode\(.*\)
- - Spamfilter: an option to apply spamfilters to aliases as well. To do so, you have
  to put 'spamfilter yes;' in every alias block you want to get filtered.
  The /MS and /MEMOSERV aliases in aliases/*.conf have been updated to have
  spamfiltering enabled by default.
- - The "max bans per channel" setting can now be changed trough the config file by
  setting set::maxbans. Note that you probably also want to enlarge set::maxbanlength
  then as well (see docs!) or else you will hit that limit first. Note that the max ban
  length setting has been slightly relaxed in 3.2.4, see the CHANGED section further down.
- - Nick Character System: new languages/character sets are added: 'danish',
  'belarussian-w1251' and 'ukrainian-w1251'.
- - ExtBan ~c now accepts wildcards, such as: "+b ~c:#*xxx*" (don't forget the "#")
- - Banned users can no longer change the topic
- - Made it so you no longer can change your nick TO a banned one in a channel.
  This option can be turned off by setting set::check-target-nick-bans to "no".
- - Translations: Added a Bulgarian example.bg.conf, a Russian help.ru.conf, and a Dutch
  unreal32docs.nl.html
- - For services coders: Added doc/technical/serverprotocol.html

==[ CHANGED ]==
- - Changed the MAXBANLENGTH (now set::maxbanlength) from 1K to 2K. This means users can now
  set more bans and actually reach the 60 MAXBANS (now set::maxbans) limit in practice.
- - Added several indicators to the "detect binary incompatible modules"-system, such as
  a module compiled with ziplinks support on a non-ziplinks ircd (*NIX only), nospoof
  mismatches, etc. Hopefully this will help some people preventing odd crashes when
  they forgot to recompile everything.
- - More modulizing: another 200 lines of code / 20 functions have been moved to modules.
- - Multiple allow channel::channel items are now permitted again
- - Redid glob matching. Escaping is now ripped out for normal bans (as it should be), this
  means no longer weird issues with +b *\* etc not banning nicks with \ in it.
  ExtBan ~c/~r get special treatment and will use our match_esc [match with escaping]
  routine, you can escape via \, so \* will match * (an asterisk), \? will match a
  questionmark (?), and \\ will match a \ (backslash). This way you can ban channels
  such as "#f*ck" via "+b ~c:#f\*ck". So, take note, if you want to ban for example a
  channel with a backslash in it, such as "#bl\ah", then you do "+b ~c:#bl\\ah".
  Again, for any bans other than ~c/~r this does not apply.
- - Spamfilter: regexes and reasons are now more limited in size, this is to combat the
  "I set a spamfilter, but cannot remove it" problem. In practice this means - depending
  on the length of the spamfilter reason - that spamfilter will max ~300 characters.
  Note that spamfilters in the config file can still be larger (since they cannot be
  removed on the command line anyway, it doesn't matter that they are cut off on /stats F).
- - CMDLINE_CONFIG behavior change: specifying a config file on the command line is now
  permitted as long as the ircd isn't suid/sgid.
- - set::channel-command-prefix now defaults to ".`!" instead of "`"
- - When OPEROVERRIDE_VERIFY is enabled, we now allow opers to still join any channels listed
  in set::auto-join or set::oper-auto-join, even if they are +s/+p.
- - Made it so co-admins can /ADCHAT. They were already receiving them anyway...
- - ./Config: the script now actually stops upon the error, making it more clear what is wrong.
- - Global opers on quarantined servers will now be KILL'ed. So link::options::quarantine now
  actually does what it should, even if it's not in the most elegant way.
- - Empty (but existing) include files no longer cause an error.
- - We now properly error if someone tries to /(G)ZLINE *@hostmask (should be *@ipmask) or
  /(G)ZLINE usermask@something (should be *@something). Both forms are illegal because
  (G)ZLINES are processed before dns and ident lookups. If you require a ban on a hostmask
  or a usermask, simply use a KLINE or GLINE.
- - For users using remote includes w/ssl (https, ftps): the CA certificates are now stored
  in curl-ca-bundle.crt (shipped with Unreal) which contains most major CA's plus CACert.

==[ MAJOR BUGS FIXED ]==
- - Two issues with an incorrect badword { } block in the config file causing a crash.
- - Incorrect TKL/*LINE causing a crash
- - Complete resolver recode: now using c-ares + caching to fix some (rare?) crash bugs and
  to make our code much more cleaner.
- - Using GCC4 caused a crash on-link.
- - Crash when a class block was removed and had any other blocks were referencing it.
- - OpenBSD crash on /REHASH.
- - Several AMD64 crash issues.
- - Sometimes a serious flood of notices was generated if link::options::nodnscache was used.
- - Spamfilter: action 'viruschan' combined with target 'user' caused crashes.
- - chinese-* nick characters support caused memory corruption.
- - Crash issue regarding SSL and junk snomask.

==[ MINOR BUGS FIXED ]==
- - Now properly resolves hostnames again that use CNAME delegation (got broken in 3.2.3).
- - Fedora Core w/IPv6 failed to compile.
- - A few read-after-free bugs that could have caused crashes.
- - ./Config was not loading the settings properly on Solaris 10
- - Crash if high ascii in set::network-name
- - Fixed advanced channel aliases not working properly
- - Fixed \* and \? escaping not always working properly (for example in ~r/~c bans).

==[ REMOVED ]==
- - Windows 9X/ME are no longer supported (it might work, but we won't support them).

==[ CHANGELOG ]==
Changelog since 3.2.3:
- - Fixed incorrect badword { } in conf causing a crash (should give an error).
- - spamfilter.conf Gaggle worm sigs were broken causing odd things to match, this is because
  \\ now needs to be escaped as \\\\ due to the 3.2.3 conf change... didn't think of updating sigs.
- - Clarified some nickchar stuff in the docs
- - Added 'danish' nickchars, supplied by klaus (#0002436).
- - Module coders: Added HOOKTYPE_LOCAL_SPAMFILTER: catches (local) spamfilter matches.
- - Fixed chanmode G showing up twice in 005, reported by Snake (#0002466).
- - Fixed a TKL crash on incorrect *line, reported by nanookles1234 (#0002524).
- - Redid include dependencies in Makefile, this makes things safer because on any .h change it
  would force a recompile of all files, but it could mean things will be a bit slower for us
  coders unless we tweak it later on.
- - Changed whois a bit to print less useless results.
- - Added several indicators to the "detect binary incompatible modules"-system such as detecting
  of a ziplinks module on non-ziplinks (on windows this is ok however), nospoof module on a
  a server without nospoof server, etc. Hopefully this will help some people preventing odd
  crashes because they did not recompile or (re)install modules properly.
- - Added './unreal backtrace', so far this has only been tested on Linux and FreeBSD.
- - Fixed a bug making ./Config not load the previously stored settings on Solaris 10 and
  probably other Unixes, reported by lion-o (#0002474).
- - Cosmetic bug in set::modes-on-join: now rejecting +I in it. Reported by Ron2K (#0002508).
- - Moved all TKL code and register_user to modules (using efuncs), that means 20 functions
  and 2000 lines total that can be hotfixed if needed ;). The effort involved in moving all
  this sucks a lot though :/. This might need some more testing to make sure it doesn't break
  anything.
- - Updated support OS list in documentation.
- - Fixed various major bugs due to TKL move from 13h ago.
- - Fixed 2 problems caused by TKL move: 1 windows crash, 1 problem with loading m_*.so,
  reported by Trocotronic (#0002553, #0002554).
- - Added some TSCTL logging (this reminds me we need to add new log levels for 3.3 ;p).
- - Attempt to fix bug #2431: 3.2.3 broke CNAME delegation for reverse dns. I'm sorry it took
  so long, but this stuff just plain sucks...
- - Made '?*' work correctly in wildcard matches ('1 or more characters'), reported by
  Bugz (#2585).
- - Added -fno-strict-aliasing.. this might well be temporary, but we get tons of strict-
  aliasing warnings, so it sounds good to disable this type of optimization for now.
- - Fixed problem with crash-on-link if compiled with GCC 4, reported by jonneyboy (#2573)
  and PHANTOm (#2590).
- - IPv6: Added configure check for in6addr_any to fix Fedora Core 4 compile problem,
  reported by wheatie80 (#2594).
- - Added -Wno-pointer-sign (if available) to get rid of those stupid warnings that are
  enabled by default even without -Wall (!?) on GCC4.
- - Fixed a bug where allow channel::channel generated a warning when specified multiple times
  (#0002427) reported by matridom.
- - Fixed ~c not working properly with * and ?'s in channel names.. Now you just need to
  escape them like in all bans (eg: to ban #* you need to +b ~c:#\*). As an additional
  bonus, real wildcards are now accepted and processed (eg: +b ~c:#*sex*, just don't
  forget to specify the #). Reported by PhantasyX (#2605).
- - Sidenote on above: ~c:*chan* is not supported (use ~c:#*chan* instead) because it would
  cause "hidden bans", therefore it now prints a message (which is useful anyway), but
  does accept such remote bans. In 3.2.5 or so we could enable support for it, it's
  not that important though... ;)
- - Added ifdefs for mass closing of file descriptors on start, can now be disabled by
  adding -DNOCLOSEFD as a compile option. Useful for valgrind w/--db-attach=yes, mpatrol,
  and some other debugging tools (not useful for anyone normally running a server).
- - Fixed a read-after-free: sptr->serv->aconf was freed but not NULL'ed in exit_client,
  causing close_connection to read from it (when deciding on doing a quick reconnect).
  Could have caused a crash, although nobody ever reported one...
- - Removed useless strncpyzt with dest==src.
- - Temporary workaround for spamfilter bug: action 'viruschan' in combination with the
  'u' (user) target can cause severe problems (crashes, etc). For now, we have disabled
  'viruschan' in combination with 'u'. A real fix will require quite some work, sorry.
- - Fixed crash with invalid set::network-name (eg: high ascii), reported by galahad
  (#0002584), now printing an error instead (the network name is limited by the 005 spec).
- - Added Bulgarian example.bg.conf, translated by Peace.
- - Spamfilter: regexes (and reasons) are now more limited in size, this is to combat "I set
  a spamfilter, but cannot remove it" problems. In practice this means - depending on the
  length of your spamfilter reason - regexes will be max ~300 characters.
  Spamfilters set in the .conf can be slightly longer (which still causes them to be
  truncated in '/stats f', but they don't have to be removed anyway so it's kinda
  acceptable if it's really needed). This should fix bug #2083, reported by White_Magic.
- - Fixed a bug where an invalid /*line could cause a crash, reported by Gilou (#2629).
- - (5 minutes later..) Small update for above, fix was incorrect for ipv6.
- - CMDLINE_CONFIG behavior change: command line configuration is now still permitted
  if #undef'ed (which is the default) if uid==euid && gid==egid, since it doesn't make
  any sense to disable it then and is in fact just plain annoying.
- - Added FAKELAG_CONFIGURABLE option in include/config.h, this enables an option called
  class::options::nofakelag, which disables "fake lag" for a certain class (that is:
  the artificial delay introduced by the ircd to prevent flooding is turned off,
  allowing the user to flood at full speed).
  IT'S USE IS DISCOURAGED UNLESS YOU REALLY KNOW WHAT YOU ARE DOING.
  Sorry, option is not in ./Config -advanced since I don't get autoconf working, but it's
  such a scary option that this might as well be a good idea to keep in config.h anyway.
  This feature has been suggested for several years (and refused), but the final
  suggestion (with implementation specific hints) came from Gilou in bug #0002207.
- - Fixed win32 makefile, now compiles fine.
- - Fixed (important?) reference count bug regarding sptr->serv->conf. I don't know what
  effects this caused (memory corruption?), but it didn't look good ;).
- - Fixed an invalid badword block in the conf causing a crash, reported by Monk (#2639).
- - [Internal] Code cleanup for spamfilter target/bantype routines
- - Added 'warn' target which is basically the same as 'block' except it does not block ;).
  It also sends a numeric to the user saying the command has been processed, but a copy
  has been sent to ircops. I feel this is a good idea for privacy reasons (anti-spy),
  though I don't know how users will react to this. If you are using this on your network
  and get users bothering you about it (or before that ;p), it's probably a good idea
  to explain it somewhere on your site or FAQ :).
  Example usage:
   /spamfilter add p warn - Testing_mirc_decode_filter \$decode\(.*\)
  [WARNING] The numeric text is likely to change in the next few weeks (early-cvs-commit).
- - If a class block was removed and any other blocks would be referencing the class block
  (such as: allow::class, oper::class, link::class), then this would cause a crash.
  Reported by Mike_ (#0002646).
- - Changed the way we build most of the .so's: the .o files of individual modules that were
  generated (for linkage by commands.so), are now used to generate the .so files of the
  individual modules as well (eg: m_setname.o -link-> m_setname.so). This reduces compile
  time ('make') on my machine by 33%, so it's quite noticable ;).
- - Added doc/technical/serverprotocol.html created by aquanight (updates will follow soon).
- - Documented set::channel-command-prefix a bit more, and also changed the default from
  "`" to "`!." which seems much more reasonable / widespread :).
- - Some m_restart cleanups, suggested by w00t (#2652).
- - Removed all old resolver code and switched over to c-ares (+our caching routines).
  This should get rid of some annoying untracable (and usually rare) crashbugs in the
  old resolver. Besides that, it makes things look more clean and understandable.
  This should be the fix for the following bugids (all the same issue): #2499, #2551, #2558,
  #2559, #2603, #2642, #2502, #2501, #2618, #2616.
  Feedback and testing is very much welcomed (sy...@un...).
- - Fixed SSL + new resolver problem, would cause an "interesting flood" of messages / 100% CPU.
  Reported by Trocotronic (#0002659).
- - Fixed a problem with entries in the hosts file (such as, usually, localhost), this would
  cause an unresolved host and a 30s delay for the user, even though resolving succeeded.
- - When OPEROVERRIDE_VERIFY is enabled, we now allow opers to still join any channels listed
  in set::auto-join or set::oper-auto-join, even if they are +s/+p. Suggested by ultrotter
  (#0002644).
- - Added 4 UNREAL_VERSION_* macro's that can be useful for 3rd party modules to find out the
  unreal version that the user is using. I presume this can be helpful (although nobody ever
  suggested it ;p). The macros (#define's) are:
  UNREAL_VERSION_GENERATION    The generation version number        eg: 3 for 3.2.4
  UNREAL_VERSION_MAJOR         The major version number             eg: 2 for 3.2.4
  UNREAL_VERSION_MINOR         The minor version number             eg: 4 for 3.2.4
                               This can be negative for unstable,
                               alpha and beta versions.
  UNREAL_VERSION_TIME          Year + week of the day (starting     eg: 200541
                               on Monday), this is updated on
                               the CVS server every week.
  The first 3 are for nicely identifiying the version, the 4th can be useful in case
  you want to support CVS and/or want some more control.
- - Fixed crash bug (due to new resolver) if not using 1 general *@* / *@* allow block,
  reported by Daniel.
- - Fixed issue that could cause an alias to be added that would override a command.
- - Fixed OpenBSD crash on /REHASH. Thanks to Peter Laur (OpenBSD.se) for providing us
  a shell account to trace this issue down.
- - Couple of source code cleanups (svsnick, a *line msg, kill, and some useless l_commands
  code), suggested by Nazzy and Requi3m.
- - Fixed extbans no longer working properly in CVS, fix provided by Nazzy (#0002681).
- - Made it so you no longer can change your nick to a banned one in a channel, suggested
  by vonitsanet (#0002388), partial patch provided by Nazzy.
  This option can be turned off by setting set::check-target-nick-bans to 'no'.
- - Removed useless (unused) WATCH code that was still present in the core.
- - Made it so coadmins can use /ADCHAT (makes sense, since they already *received*
  adchats). Reported by RandomNumber (#0002557).
- - Fixed serious flood of notices to opers if link::options::dnscache was present.
  Reported by firstof9.
- - Added proper "not enough parameters" message for /SETNAME and cleaned up some whitespace
  in the function, reported by Robby22 (#0002696).
- - Fixed set::static-part set to 'no' not working properly. Reported by Robby22 (#0002698).
- - Fixed crash in new resolver, reported by firstof9.
- - [CVS Only] Refixed name<->ip mapping check in new resolver, reported by Darko.
- - Reverting "Changed the way we build most of the .so's" feature, this caused m_*.so
  to be build incorrectly. So now back at normal compile speed :p.
- - Added option to apply spamfilters to aliases as well (such as /MS, etc). To do so,
  you have to put 'spamfilter yes;' in every alias block you want to get filtered.
  This is so you can have for example /MS filtered (due to heavy spam), while keeping
  /NS and /CS unfiltered. Reported by Homer (#0002496).
- - The memoserv aliases (/MS and /MEMOSERV) now have spamfiltering enabled by default.
- - Made the "strict aliasing"-warning-disabler use $CC instead of gcc.
- - Made ./Config better react to errors (no longer print a "everything is a big success"
  kind of message when in fact everything went wrong).
- - Made ./Config (configure) exit on openssl or zlib not found errors, instead of
  silently continueing and then causing trouble later on. Also now printing _a bit_
  more helpful error message.
- - Made the link::options::quarantine actually do something... People that get global
  oper privileges on quarantined servers will be instantly killed. Bit ugly perhaps, but
  then it actually does what it should (prevent opers on quarantine from getting GLOBAL
  oper privileges). This "fixes" #2510, #2163 and #1968.
- - Fixes for an amd64 crash problem, reported by Peter Laur (OpenBSD.se).
- - Redid some net synching code to make it more efficient (#2716).
- - Fixed spamfilter crash problem: the action 'viruschan' is now no longer incompatible
  with target 'user'. Reported by Monk (#0002570).
- - Fixed invalid servername in quarantine kill, reported by pinstrate (#0002743).
- - Fixed bug in chinese-* charset implementation that would cause crashes, reported
  and patch supplied by Xuefer (#0002744).
- - Added new charsys languages: belarussian-w1251 and ukrainian-w1251. Patch provided
  by Bock (#0002724).
- - Fixed memory leak in new resolver.
- - Made the charsys mismatch during linking a warning instead of an error (temp. fix,
  until a good solution is implemented without false positives).
- - Crashbug fix for above
- - Fixed some more memleaks, thanks to valgrind.
- - Updated the list of donators.
- - Fixed (well, workaround) win32 /RESTART bug that caused it to popup a window instead
  of actually restarting the server properly (#0002734).
- - If you now use /(G)ZLINE usermask@something instead of /(G)ZLINE *@something you get
  an error, since specifying usermask should not be done and is useless, since a (G)ZLINE
  takes place BEFORE ident lookups.
- - Did the same for /(G)ZLINE *@hostmask (should be *@ipmask), this already was a warning
  in 3.2.3, and is an error now in 3.2.4.
- - Little /STATS v tweak: should display 'v' in output, not 'V'. Reported by Robby22 (#2700).
- - Fixed complex command aliases not working properly, patch from Nazzy (#2722).
- - Made it so banned users cannot change the topic, suggested by aquanight and Stealth (#2233).
- - Made the "max bans per channel" setting dynamic. This can be changed by setting
  set::maxbans in the configfile, note that you probably also want to enlarge set::maxbanlength
  as well (see docs) or else you will hit that limit first.
- - Changed the default maxbanlength from 1K to 2K, which means people can set more bans because
  in pracitce the 60 (maxbans) limit was never met because the maxbanlimit was set so low.
- - Empty (but existing) include files no longer cause an error. Reported by w00t (#0002460).
- - Nick Character System: Silently not advertising danish if using latin1, circumventing link
  problems if using latin1.
- - Removed small comment from docs, which no longer applies (sorry translators ;p).
- - Updated /CREDITS (forums/mainsite hosting and update of current active supporters).
- - Updated makefile.win32: apparently libcurl.dll is now libcurl_imp.dll (import library)
- - Updated unrealinst.iss: made it easier for me to have 2 curl versions, this is so we can
  ship the SSL version of unreal with a curl that supports SSL (https, etc).
- - Preperations for pre-1 (version change, etc)
- - Updated wircd.def (for developers).
- - Added doc/help.ru.conf, translated by Slyder.
** internal 3.2.4-pre1 release **
- - set::maxbans / set::maxbanlength were reported as duplicates when they were not, reported
  by Jason and trystanscott (#0002753).
- - Made it so bans on normal users will prevent them from speaking with +mu, reported by Nazzy.
- - Made set::maxbanlength also count the "to be set" ban in, otherwise you could exceed the
  limit by (max) NICKLEN+USERNAME+HOSTNAME+2, reported by Trocotronic (#0002762).
- - Switched over to an older match() routine based on hybrid, this one is a bit less optimized
  but is actually understandable and has less bugs. This fixes +b ~c:#c\*t not properly
  matching #c*t, reported by Jason (#0002752). Initial results look good, but this needs
  some good testing ;).
- - Removed some old config.h stuff + clarified some text, reported by Jason (#2765, #2766).
** internal 3.2.4-pre2 release **
- - Made it so a set::maxbanlength and/or set::maxbans of 0 denies all bans properly, and
  fixes the first-ban-can-be-as-long-as-you-want bug, both reported by Trocotronic (#2762).
- - Fixed SVS2SNO not always notifying the user of the snomask change, reported by decoder
  (#0002767).
- - Curl users using https/ftps/etc: UnrealIRCd now ships with a 'curl-ca-bundle.crt' which
  contains the (root) certificates of most major Certificate Authorities. It is basically
  the default curl ca-bundle.crt plus cacert's certificates.
  The 'curl-ca-bundle.crt' will be copied to the installation dir if needed.
  It will from now on be used by Unreal for all remote includes (curl) related certificates.
  If you want to use https but don't want to buy a certificate, we suggest you to apply for
  a free certificate at CACert (www.CACert.org). Or, alternatively, add your own certificate
  (PEM encoded) to curl-ca-bundle.crt, see 'SSLCERTS' in the curl package for more info.
** public 3.2.4-rc1 release **
- - Fixed(?) bug due to match() rewrite: we now use our old rules with escaping again, due to
  the switchover we were accidently using different ones which caused funny kill messages
  like "You were killed by a.b.c (a!a.b.c (SOMENICK[N\A](?) <- d.e.f))." This also broke
  some bans in pre2/rc1. Bug reported by HERZ (#0002772).
- - Fixed localhost crash (if no dns record for 127.0.0.1), reported by Trocotronic (#2773).
** public 3.2.4-rc2 release **
- - Sometimes if an oper was connected trough SSL and had the junk snomask (+s +j) set it
  would cause a crash. Reported by chasingsol (#0002777).
- - Updated help.ru.conf (corrections by CS-Help / Bock)
- - Updated example.bg.conf (by Peace)
- - Added Dutch unreal32docs.nl.html, translated/maintained by Mark.
- - Redid glob matching. Escaping is now ripped out for normal bans (as it should be), this
  means no longer weird issues with +b *\* etc not banning nicks with \ in it.
  ExtBan ~c/~r get special treatment and will use our match_esc [match with escaping]
  routine, that way you can ban channels such as "#f*ck" via "+b ~c:#f\*ck".
  Fix triggered by bugreport of vonitsanet (#0002782).
** public 3.2.4-rc3 release **
- - No changes (except version number)
** 3.2.4 release **

As usual, you can get it from http://www.unrealircd.com/

All our releases are PGP signed (well, with GPG) with our releases key:
rel...@un... [0x1C8A554E] which you can grab from
http://www.unrealircd.com/pgp/release_key.asc
This is the same release key that was used for signing 3.2.3.
More info about this is shown when downloading.

We no longer provide MD5/SHA1 checksums because we feel they are
too insecure.

Thank you for using UnrealIRCd!

	The UnrealIRCd Team.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFD45JZ4cPWX+btKqIRAvk5AKCXTBVtv2MAg5yGHfslL+y2utTvkQCgruoL
fl7UHfEMf3gllUW1i775SN4=
=yz15
-----END PGP SIGNATURE-----

Re: [Unreal-users] Bogus Server Name

[Steve <l1...@ve...>]

----- Original Message ----- 
From: "ace" <ac...@fr...>
To: <unr...@li...>
Sent: Tuesday, November 22, 2005 10:28 PM
Subject: [Unreal-users] Bogus Server Name


> Hello,
>
> [10:21 pm] -hub.tx.us.freedomchat.org- WARNING: Bogus server name 
> (Tigersturf) from [@63.229.210.1.1303] (maybe just a fishy client)
>
> What is this and how might I get rid of it?  It's starting to become 
> extremely annoying.  Thanks, everyone.
>
> ace
>
>
>
try config ban the server from tryin to connect read the docs on how to do 
that 

Re: [Unreal-users] Bogus Server Name

[tabris <ta...@ta...>]

ace wrote:
> Hello,
>
> [10:21 pm] -hub.tx.us.freedomchat.org- WARNING: Bogus server name
> (Tigersturf) from [@63.229.210.1.1303] (maybe just a fishy client)
>
> What is this and how might I get rid of it?  It's starting to become
> extremely annoying.  Thanks, everyone.
>
> ace
Check if you have any users on that IP. if not, zline the IP. if you do,
find the person and strangle them. if they don't respond, zline the IP.

[Unreal-users] Bogus Server Name

[ace <ac...@fr...>]

Hello,

[10:21 pm] -hub.tx.us.freedomchat.org- WARNING: Bogus server name 
(Tigersturf) from [@63.229.210.1.1303] (maybe just a fishy client)

What is this and how might I get rid of it?  It's starting to become 
extremely annoying.  Thanks, everyone.

ace

Re: [Unreal-users] Kick Reasons

[MrStatic <st...@ta...>]

You would want to post this on the bugtracker as a request.

MrStatic
----- Original Message ----- 
From: "ace" <ac...@fr...>
To: <unr...@li...>
Sent: Tuesday, October 25, 2005 9:48 PM
Subject: [Unreal-users] Kick Reasons


> Hello all,
> 
> Is it possible to have a flag for spamfilter for kick reasons?
> I am running a network with users who are using speech software for 
> visually-impaired people and there are certain words which need to be 
> blocked in everything.
> 
> ace
> irc.freedomchat.org
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Unreal-users mailing list
> Unr...@li...
> https://lists.sourceforge.net/lists/listinfo/unreal-users
> 
>

[Unreal-users] Kick Reasons

[ace <ac...@fr...>]

Hello all,

Is it possible to have a flag for spamfilter for kick reasons?
I am running a network with users who are using speech software for 
visually-impaired people and there are certain words which need to be 
blocked in everything.

ace
irc.freedomchat.org

[Unreal-users] Banned file: "message.txt .pif" in mail from you

[MAILER D. <>]

QkFOTkVEIEZJTEVOQU1FIEFMRVJUCgpZb3VyIG1lc3NhZ2UgdG86IHNpdGVz
YWxlc0BhY2RzeXN0ZW1zLmNvbQp3YXMgYmxvY2tlZCBieSBvdXIgU3BhbSBG
aXJld2FsbC4gVGhlIGVtYWlsIHlvdSBzZW50IHdpdGggdGhlIGZvbGxvd2lu
ZyBzdWJqZWN0IGhhcyBOT1QgQkVFTiBERUxJVkVSRUQ6CgpTdWJqZWN0OiBS
ZTogUmU6IGNvcnJlY3RlZAoKQW4gYXR0YWNobWVudCBpbiB0aGF0IG1haWwg
d2FzIG9mIGEgZmlsZSB0eXBlIHRoYXQgdGhlIFNwYW0gRmlyZXdhbGwgaXMg
c2V0IHRvIGJsb2NrLgoKCg==

[Unreal-users] a ?

[Paul M. <Pau...@ho...>]

how i be  founder of a server?
and Services are currently down. Please try again later.

[Unreal-users] cconnection limit

[Mehmet K. <me...@at...>]

How can i set max connection for a specified IP to 10 but let the
standard limit to 3 for exaple?


thanx

Re: [Unreal-users] help

[NightStorm <un...@is...>]

The unrealircd.conf file is 'commented' out so that certain sections are =
not read.
What this is telling you, is that a commented section is started, but =
not properly ended.
All commented sections start with a /*
And end with a */
Look for where the 'explaination' section at the beginning of your =
config file ends, and the actual values start... between the 2, place a =
*/ and then try booting the server again.
.
  ----- Original Message -----=20
  From: Paul Musick=20
  To: unr...@li...=20
  Sent: Monday, September 05, 2005 6:32 PM
  Subject: *****SPAM***** LOW * [Unreal-users] help


  i need help  but i dk what to do * Loading IRCd configuration ..
  [error] unrealircd.conf:1 Comment on this line does not end
  [error] Could not load config file unrealircd.conf
  [error] IRCd configuration failed to load

[Unreal-users] Allow Block (I:Line)

[Luniz <gl...@lu...>]

Just curious, but does anyone have any idea what the max length the password
can be in the Allow Block?

Re: [Unreal-users] IP cloaking

[tabris <ta...@ta...>]

On Thursday 14 July 2005 3:01 pm, tabris wrote:
> 	I realize that this would be a module question, and that it likely
> would not be recommended. However, I think there is a sufficient use
> for a IP cloaking method that would keep the first 2 or 3 octets
> uncloaked, as it would be easier to recognize people.
>
	I should probably amend this posting, to mention that I know that you=20
don't just cloak using the lat octet, as that would then make a simple=20
lookup table for which of 256 values it is. the entirety of the IP=20
would be used as input for the cloaked-portion, same as normal=20
host-cloaking does.
> 	I remember that the last time this proposal came up, there were a
> couple objections.
> a)	security. 255 possibilities is supposedly sufficiently trivial to
> attack.
> b)	IRC Clients not handling it correctly. This is a possibility that
> is harder to trivialize. However, I remember ConferenceRoom 1.8.x
> doing this (and 2.x as well), and IRC clients handled it just fine.
> istr they having an IP cloak like so (this is an actual cloak pulled
> from my logs from a ConferenceRoom server I went to back in 2003):
> 4.18.44.KU929=3D
>
> 	This is NOT to mean that I want to remove the MD5 cloaking algo. I
> just want to modify the IPv6 and IPv4 cloaking to make it easier to
> identify which network/ISP that a user is connecting from, thus
> making it easier to identify a user on-sight.
>
> 	I would have checked the forums, but they appear to be missing/down.
> I have also considered coding this myself, but I am insufficiently
> sure that I understand the algorithm in use, as well as being not
> confident in my ability to do so. Won't necessarily stop me from
> trying, if I get enough time.
>
> 	Anyway, does anybody else want this? Would anybody else use it?
> --
> tabris
> -
> Q:	Why is Poland just like the United States?
> A:	In the United States you can't buy anything for zlotys and in
> 	Poland you can't either, while in the U.S. you can get whatever
> 	you want for dollars, just as you can in Poland.
> 		-- being told in Poland, 1987

=2D-=20
	"Sheriff, we gotta catch Black Bart."
	"Oh, yeah?  What's he look like?"
	"Well, he's wearin' a paper hat, a paper shirt, paper pants and
paper boots."
	"What's he wanted for?"
	"Rustling."

[Unreal-users] IP cloaking

[tabris <ta...@ta...>]

	I realize that this would be a module question, and that it likely=20
would not be recommended. However, I think there is a sufficient use=20
for a IP cloaking method that would keep the first 2 or 3 octets=20
uncloaked, as it would be easier to recognize people.

	I remember that the last time this proposal came up, there were a=20
couple objections.=20
a)	security. 255 possibilities is supposedly sufficiently trivial to=20
attack.=20
b)	IRC Clients not handling it correctly. This is a possibility that is=20
harder to trivialize. However, I remember ConferenceRoom 1.8.x doing=20
this (and 2.x as well), and IRC clients handled it just fine. istr they=20
having an IP cloak like so (this is an actual cloak pulled from my logs=20
from a ConferenceRoom server I went to back in 2003): 4.18.44.KU929=3D

	This is NOT to mean that I want to remove the MD5 cloaking algo. I just=20
want to modify the IPv6 and IPv4 cloaking to make it easier to identify=20
which network/ISP that a user is connecting from, thus making it easier=20
to identify a user on-sight.

	I would have checked the forums, but they appear to be missing/down. I=20
have also considered coding this myself, but I am insufficiently sure=20
that I understand the algorithm in use, as well as being not confident=20
in my ability to do so. Won't necessarily stop me from trying, if I get=20
enough time.

	Anyway, does anybody else want this? Would anybody else use it?
=2D-
tabris
=2D
Q:	Why is Poland just like the United States?
A:	In the United States you can't buy anything for zlotys and in
	Poland you can't either, while in the U.S. you can get whatever
	you want for dollars, just as you can in Poland.
		-- being told in Poland, 1987

Re: [Unreal-users] How can I disable message-rate-limiting?

[tabris <ta...@ta...>]

On Thursday 14 July 2005 2:00 am, Eric Mayers wrote:
> I'm using irc (and the unrealirc server) to do some collaboration and
> I've built a bot that runs various commands and dumps some output
> into a channel (10-50 lines per command generally).  The problem is
> that I want the bot to be able to dump data more quickly than is
> occurring.
>
> More specifically, the bot writes 20 lines without delay.  In the
> channel, 5 lines appear almost instantly then the next 15 get doled
> out at what appears to be 1 per second.

	Not including your client/script limiting you (which, for example,=20
irssi does), the best method to handle this probably is to give your=20
bot a limited oper. HOWEVER, I have been told that this is a 'dumb=20
idea' as supposedly there is no such thing as a 'powerless oper' and=20
they're probably at least partly right.

	However, I have found it to be possible to make an oper that has no=20
real flags. Just GH for flags. That's get_host and can_globalnotice.=20
You may want can_setq as well, to prevent users from kicking your bot.=20
As far as I can tell, this oper does NOT allow KILL, KLINE, etc. Thus,=20
in theory, it should be safe.

	An alternative is to consider server-protocol coding and make it into a=20
services-server. But this is not a project for the faint-of-heart.

	Meanwhile, I don't believe that this will prevent excess-floods, but=20
DOES greatly up the limit on how much you can send before getting=20
killed for flooding.

	I'd only recommend this if Chris's suggestions don't work. And of=20
course, the bot would have to be owned by a staffer.
>
> I realize if I write even more (e.g. 100) lines that I get an 'excess
> flood' message and get kicked.  I can handle this limit.
>
> Users are trusted on the server so I'm not really worried about
> flooding (I'm ok modifying the behavior for all users and all
> channels as well).
>
> So my question is : How can I allow this 'user' to write to a channel
> more quickly?
>
> Thanks!
> Eric
>
>
=2D-=20
  I don't think anyone should write their autobiography until after
  they're dead. -Samuel Goldwyn

[Unreal-users] $BL5NA$G$G$-$kA4$F$r5M$a9~$_$^$7$?(B

[<in...@qs...>]

$BDL>o$NM-NA7O$N%5%$%H$G$b9b3[$J@A5a$r$5$l$kD>EE!&D>%a$N8r49$b$3$3$G$OL5NA!*(B
$B$b$A$m$s<L%a!<%kBP1~$@$7!"CO0h$d%W%m%U%#!<%k$GAj<j$r8!:w$9$k$N$b40A4L5NA!*(B
$B$7$+$bCK@-2q0w$N2r6XA0$K=w@-2q0w$r@h9TEPO?$9$k$3$H$K$h$j8=:_CK=wHf$,(B2$B!'(B8$B!*(B
$B$@$+$i$[$H$s$IF~$l?)$$>uBV!*!*$I$s$I$sD>EE!&D>%a#G#E#T$7$A$c$C$F$/$@$5$$!*(B
$B%5%$%H$O$3$A$i$+$i"-(B
http://www.ya2dic.com?num=8416

Re: [Unreal-users] How can I disable message-rate-limiting?

[Christian 'H. M. <ad...@in...>]

Message Rate Limiting is not limited by UnrealIRCD.

Unrealircd just limit the send and receive queue time in bytes.
See your class <name> sendq <send-queue>; recvq <recv-queue>;
block.

Mostly Bots example Eggdrop is sending limited
Message to Server to avoid Excess flood by Server.

Just look in the eggdrop.conf:
>> / ---- cut from eggdrop.conf ---- />>/
# Set here the maximum number of lines to queue to the server. If
you're />>/
# going to dump large chunks of text to people over IRC, you will
probably />>/
# want to raise this. 300 is fine for most people though. />>/
set max-queue-msg 300

-- 
kind Regards

Christian 'HERZ' Makowski
-----------------------------------------------------------------
insiderZ.DE - GERMAN IRC NETWORK - Networkadmin Executive (CEO)
URL.: http://www.insiderz.de    eMail:    admin(at)insiderZ.org
Protect your IRC Network:  http://unrealworld.insiderz.de
-----------------------------------------------------------------
Key/Fingerprint: 19C 8C25 D3EA DEEF 1BA4 DB8B A4BE 52B9 9D1F 9612





Eric Mayers wrote:

> I'm using irc (and the unrealirc server) to do some collaboration
> and I've built a bot that runs various commands and dumps some
> output into a channel (10-50 lines per command generally). The
> problem is that I want the bot to be able to dump data more quickly
> than is occurring.

[Unreal-users] How can I disable message-rate-limiting?

[Eric M. <em...@gm...>]

I'm using irc (and the unrealirc server) to do some collaboration and
I've built a bot that runs various commands and dumps some output into
a channel (10-50 lines per command generally).  The problem is that I
want the bot to be able to dump data more quickly than is occurring.

More specifically, the bot writes 20 lines without delay.  In the
channel, 5 lines appear almost instantly then the next 15 get doled
out at what appears to be 1 per second.

I realize if I write even more (e.g. 100) lines that I get an 'excess
flood' message and get kicked.  I can handle this limit.

Users are trusted on the server so I'm not really worried about
flooding (I'm ok modifying the behavior for all users and all channels
as well).

So my question is : How can I allow this 'user' to write to a channel
more quickly?

Thanks!
Eric

Re: [Unreal-users] supplying ssl passphrase on reboot?

[Bram M. (Syzop) <sy...@vu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rick Millar wrote:
> I am running urealircd on linux using ssl.  I want to be able to have it
> start automatically when the machine reboots. However, my startup script
> fails because an ssl passphrase is required to start the server.  Is
> there a way to programmatically provide the passphrase to unrealircd?

The question is: What use would that have?
The password would have to be - in whatever way - able to be decoded; so
either as plaintext or with "fake/stupid encryption"[1].
If you want it to be started automatically on boot without user
intervention then you shouldn't use an encrypted cert.

	Syzop.

[1] which is, in fact, dangerous because it gives a false sense
    of security.

- --
Bram Matthys
Software developer/IT consultant        sy...@vu...
PGP key:                       www.vulnscan.org/pubkey.asc
PGP fp: 8DD4 437E 9BA8 09AA 0A8D  1811 E1C3 D65F E6ED 2AA2

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFCxW7d4cPWX+btKqIRAgxxAKC5S9IgXH14MjAY+qEPczeua9Gx3wCff2Z8
uRRsSNRJxTwIIFdc75Xnwmw=
=SjFU
-----END PGP SIGNATURE-----

[Unreal-users] supplying ssl passphrase on reboot?

[Rick M. <rm...@ll...>]

I am running urealircd on linux using ssl.  I want to be able to have it =
start automatically when the machine reboots. However, my startup script =
fails because an ssl passphrase is required to start the server.  Is =
there a way to programmatically provide the passphrase to unrealircd?

TIA,

Rick Millar

Re: [Unreal-users] Unreal IRC without DNS

[tabris <ta...@ta...>]

On Tuesday 28 June 2005 2:53 am, Giacomo A. Catenazzi wrote:
> ""G=F6hler wrote:
> > Hello @ all!
> >
> > I want to run Unreal IRC in a LAN without Internet. There is no
> > DNS-Server in this LAN. When i connect to the IRC-Server, it takes
> > about 30 seconds till my nick will be accepted by the server. I
> > think in this time the server is locking for my DNS-Name. How can i
> > solf this problem?
> >
> > Thanks for help!
>
> Use the old way: put all names in /etc/hosts, so that the name
> resolver can find the ip from names.
set::options::dont-resolve
set it to on.

it's in the docs.
>
> cate
>

=2D-=20
  I marvel at the strength of human weakness.

Re: [Unreal-users] Unreal IRC without DNS

[Giacomo A. C. <ca...@pi...>]

""G=F6hler wrote:
> Hello @ all!
> 
> I want to run Unreal IRC in a LAN without Internet. There is no 
> DNS-Server in this LAN. When i connect to the IRC-Server, it takes abo=
ut 
> 30 seconds till my nick will be accepted by the server. I think in thi=
s 
> time the server is locking for my DNS-Name. How can i solf this proble=
m?
> 
> Thanks for help!

Use the old way: put all names in /etc/hosts, so that the name resolver
can find the ip from names.

cate