+ngIRCd Release 19.2 (2012-06-19)
+
+ - doc/Capabilities.txt: document "multi-prefix" capability
+
+ ngIRCd 19.2~rc1 (2012-06-13)
+ - New configuration option "CloakHostModeX" to configure the hostname
+ that gets used for IRC clients which have user mode "+x" enabled.
+ Up to now, the name of the IRC server itself has been used for this,
+ which still is the default when "CloakHostModeX" isn't set.
+ - Correctly handle asynchronously re-established server links: a race
+ condition could let the daemon loose track of an already re-established
+ incoming server link while preparing its own outgoing connection.
+ Peers that both try to connect each other could have been affected.
+ - Log a debug message when SIGUSR2 is handled in debug mode.
+ - Only allow alphanumeric characters in user-supplied user names of
+ USER command and IDENT replies.
+ - Change wording of "TLS initialized" message to make it more consistent.
+ - Don't leak file descriptors on error path when creating "PID files".
+ - Add missing mode "r" to CHANMODES in 005 "ISUPPORT" numeric.
+ - Update doc/Modes.txt and doc/Platforms.txt documents.
+ - contrib/platformtest.sh: correctly detect Open64 C compiler and handle
+ "CC=xxx MAKE=yyy ./platformtest.sh" calling convention.
+ - Add instructions for setting up Atheme IRC services.
+ - Implement support for IRC capability handling, the new "CAP" command,
+ and capablity "multi-prefix" which allows both the NAME and WHO command
+ handlers to return more than one "class prefix" to the client.
+ - Update Xcode project files: reference missing documentation files.
+ - Fix: Don't ignore "permission denied" errors when enabling chroot.
+ - FAQ: enhance description of chroot setup.
+
+ngIRCd Release 19.1 (2012-03-19)
+
+ - Fix gcc warning (v4.6.3), initialize "list" variable to NULL.
+ - Fix typos: "recieved" -> "received", "Please not" -> "Please note",
+ and fix lintian(1) warning ""hyphen-used-as-minus-sign", too.
+ - Really include _all_ patches to build the Anope module into the
+ distribution archive ... ooops!
+ - getpid.sh: Fix test case error for Debian using sbuild(1).
+ - Don't log "ngIRCd hello message" two times when starting up.
+
+ngIRCd Release 19 (2012-02-29)
+
+ - Update build system: bump config.guess and config.sub files used by
+ GNU autoconf/automake to recent versions.
+ - Fix configuration file parser: don't accept "[SSL]" blocks in the
+ configuration file when no SSL support is built in ngIRCd.
+ - Fix building ngIRCd with old gcc versions (e. g. 2.7.2).
+ - Correctly re-open syslog logging after reading of configuration
+ file: Syslog logging has been initialized before reading the
+ configuration, so ngIRCd always used the default facility and ignored
+ the "SyslogFacility" configuration option ...
+ Thanks to Patrik Schindler for reporting this issue!
+
+ ngIRCd 19~rc1 (2012-02-12)
+ - Enhance command limits for server links: the limit now is dependent
+ on the number of users connected in the network and higher while
+ servers are joining the network to make the login of servers faster.
+ - Log more information about server synchronization.
+ - Update preliminary ngIRCd protocol module for Anope 1.9.6, which now
+ is the only supported version.
+ - New numeric RPL_WHOISHOST_MSG(378), which returns the DNS host name
+ (if available) and the IP address of a client in the WHOIS reply.
+ Only the user itself and local IRC operators get this numeric.
+ - Implement channel exception list (mode 'e'). This allows a channel
+ operator to define exception masks that allow users to join the
+ channel even when a "ban" would match and prevent them from joining:
+ the exception list (e) overrides the ban list (b).
+ - PRIVMSG and NOTICE: Handle nick!user@host masks case-insensitive.
+ - Implement user mode 'C': If the target user of a PRIVMSG or NOTICE
+ command has the user mode 'C' set, it is required that both sender
+ and receiver are on the same channel. This prevents private flooding
+ by completely unknown clients.
+ - New RPL_WHOISREGNICK_MSG(307) numeric in WHOIS command replies: it
+ indicates if a nick name is registered (if user mode 'R' set).
+ - Limit channel invite, ban, and exception lists to 50 entries and fix
+ duplicate check and error messages when adding already listed entries
+ or deleting no (longer) existing ones.
+ - Fix both ERR_SUMMONDISABLED(445) and ERR_USERSDISABLED(446) replies.
+ - MODE command: correctly return ERR_UNKNOWNMODE(472) numeric for
+ unknown channel modes, instead of ERR_UMODEUNKNOWNFLAG(501).
+ - ISUPPORT(005) numeric: add "O", "R", and "z" modes to "CHANMODES",
+ add "EXCEPTS=e" and "INVEX=I", add "MAXLIST=beI:50".
+ - Limit the number of list items in the reply of LIST (100), WHO (25),
+ WHOIS (10), and WHOWAS (25) commands.
+ - LIST command: compare pattern case insensitive.
+ - Limit the MODE command to handle a maximum number of 5 channel modes
+ that require an argument (+Ibkl) per call and report this number
+ in the ISUPPORT(005) numeric: "MODES=5".
+ - Fix handling of channel mode sequence with/without arguments.
+ For example, don't generate wrong error messages when handling
+ "MODE #chan +IIIIItn *!aa@b *!bb@c *!cc@d *!dd@e *!ee@f".
+ - When sending data on a connection, only try to get the type of
+ the client if there still is one assigned. This could trigger an
+ assertion and end the daemon in some error paths.
+ - Don't try to close already closed/invalid sockets to forked child
+ processes. This could potentially crash the daemon in some cases
+ with IDENT lookups enabled.
+ - WHOIS command: make sure that the reply ends with RPL_ENDOFWHOIS,
+ don't answer queries for IRC servers, make sure mask matching is
+ case-insensitive, and that RPL_ENDOFWHOIS numeric is sent with the
+ unmodified mask (like it has been received from the client).
+ - LINKS command: support <mask> parameter to limit the reply.
+ - Add 1 second penalty for every further target on PRIVMSG/NOTICE
+ commands: this reduces the possibility of flooding channels with
+ commands like "PRIVMSG/NOTICE #a,#n,#c,... :message" a little bit.
+ Problem noticed by Cahata, thanks!
+ - Display correct error message when "Server{UID|GID}" variable in the
+ configuration file is invalid (not a number and no existing user).
+ - Update Copyright notices for 2012 :-)
+ - JOIN command: don't stop handling of channel lists when a single
+ channel cannot be joined (because of bad name, wrong key or channel
+ limit reached), but report an error and continue. And don't check
+ the channel limit and don't report with "too many channels" when
+ trying to join a channel that the client already is a member of.
+ - ISON command: reply with the correct upper-/lowercase nick names.