ngIRCd - Next Generation IRC Server
- (c)2001,2002 by Alexander Barton,
+ (c)2001-2003 by Alexander Barton,
alex@barton.de, http://www.barton.de/
ngIRCd ist freie Software und steht unter
more secure functions strlcpy(), strlcat() and snprintf(). On systems
that don't support strlcpy() and strlcat(), these functions are included
in the libngportab now (with prototypes in portab.h).
- - Fixed KILL: you can't crash the server by killing yourself any more;
- and ngIRCd no longer sends a QUIT to other servers after the KILL.
+ - Fixed KILL: you can't crash the server by killing yourself any more,
+ ngIRCd no longer sends a QUIT to other servers after the KILL, and you
+ can kill only valid users now.
+ - If the server can't close a socket, it panics now. This is an error that
+ can't occure during normal operation so there is something broken.
+ - The order of log messages during disconnects is more "natural" now ;-)
+ - Cleaned up handling of server configuration structures: modifying and
+ removing servers during runtime works more reliable now.
+ - Compression code from "conn.[ch]" is now found in new "conn-zip.[ch]"
+ - Moved some connection functions from "conn.[ch]" to "conn-func.[ch]".
+ - New command CONNECT to enable and add server links. The syntax is not
+ RFC-compatible: use "CONNECT <name> <port>" to enable and connect an
+ configured server and "CONNECT <name> <port> <host> <mypwd> <peerpwd>"
+ to add a new server (ngIRCd tries to connect new servers only once!).
+ - Added DISCONNECT command ("DISCONNECT <name>") to disable servers.
+ - The server no longer forwards commands to ordinary users, instead it
+ answers with the correct error message ("no such server") now.
+ - WHOIS commands weren't always forwarded as requested.
+ - The server sets a correct default AWAY message now when propagating
+ between servers.
Older changes (sorry, only available in german language):
--
-$Id: ChangeLog,v 1.155 2002/12/26 18:47:01 alex Exp $
+$Id: ChangeLog,v 1.163 2003/01/02 17:58:31 alex Exp $