[ircd-ratbox] ircd-ratbox-2.0.2 released

Lee H lee at leeh.co.uk
Tue Aug 31 21:10:44 EDT 2004

md5sum: 542e81eb42cfbf9dcbb452c77a3c4d26

This is the current release version of the 'testing' tree of ircd-ratbox.

NOTE: Whilst every effort has been made to make sure this code is usable, it
      is still not classified as a stable release.  You assume full
      responsibility for running this on a production network.

doc/whats-new.txt contains important lists of changes between 2.0 and 1.5 -
it is important you read this file before upgrading.

-- ircd-ratbox-2.0.2
- fix a possible overflow with SJOIN when converting nicks -> ids
- new flags in shared {};, tkline, txline and tresv, allowing temp only of
  kline, xline and resv respectively.
- new flags in cluster {}; tkline, txline and tresv which will cluster
  only the temp of each type.  kline, xline and resv will now *only*
  cluster the permanent ones of each type.
- enforce top-down ordering of shared {}; blocks.  The first one that
  matches on server and user at host will be used.  The users access will then
  depend on that shared blocks privs and we will NOT fallback to another
  that matches and has the right privs.
- cluster {}; no longer allows remote opers to apply remote klines etc, it
  simply dictates who we send our bans to.  To allow remote servers to
  cluster to a server it must have its own shared {}; block.
- fix possible server exists issue whilst waiting for connect callback
- exempt users messaging themselves from +g
- fix a core with removing accepts
- fix connect {}; to refcount classes properly
- memleak fixes with operator {}; passwords, conf parser and dns code
- fix some padding issues with ipv6
- added umode +C, an extended version of +c thats machine parsable and gives
  the two other fields given in the USER command
- add some debugging code to help track down a problem with the abort_list
- fix a problem with --with-nicklen in configure


BUGS: Major bugs in this release are listed in BUGS

BUG REPORTS: If you run this code and encounter problems, you must report
the bug by EMAIL to ircd-ratbox at lists.ratbox.org

Please include a gdb backtrace and keep the core file, binaries and 
modules in case the developers need them.

DISCUSSION: There is a mailing list for discussion of ratbox issues,
 To subscribe, visit:

You may also (if youre lucky) find us on #ratbox at EFNet

Other files recommended for reading: BUGS, README.FIRST, INSTALL

$Id: RELNOTES,v 2004/09/01 00:50:06 leeh Exp $

Lee H

More information about the ircd-ratbox mailing list