-- NEWS --
-ngIRCd Release 19
+ngIRCd Release 19.1 (2012-03-19)
+
+ - Really include _all_ patchtes to build the Anope module into the
+ distribution archive ... ooops!
+
+ngIRCd Release 19 (2012-02-29)
+
+ ngIRCd 19~rc1 (2012-02-12)
+ - 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 hostname
+ (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).
+ - 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.
+ - Limit the number of list items in the reply of LIST (100), WHO (25),
+ WHOIS (10), and WHOWAS (25) commands.
+ - 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".
+ - 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!
- New configuration option "PAMIsOptional": when set, clients not
sending a password are still allowed to connect: they won't become
"identified" and keep the "~" character prepended to their supplied
Reported by Cahata, thanks!
- Implement IRC commands "GLINE" and "KLINE" to ban users. G-Lines are
synchronized between server on peering, K-Lines are local only.
- - Xcode: update project file for Xcode 4.2.
- - Only close "unrelated" sockets in forked child processes: This fixes
- the problem that ngIRCd can't do any IDENT lookups because of the
- socket has already been closed in the child process.
- The bug has been introduced starting with ngIRCd 17 ... :-(
- (commit ID 6ebb31ab35e)
+ If you use "*!<user>@<host>" or "*!*@<host>" masks, these connections
+ are blocked even before the user is fully logged in (before PASS,
+ NICK, and USER commands have been processed) and before the child
+ processes for authentication are forked, so resource usage is smaller.
- Added doc/Modes.txt: document modes supported by ngIRCd.
- Implement user mode "R": indicates that the nick name of this user
is "registered". This mode isn't handled by ngIRCd itself, but must
- Implement channel mode "R": only registered users (having the user
mode "R" set) are allowed to join this channel.
- Test suite: bind to loopback (127.0.0.1) interface only.
- - Disconnect directly linked servers sending QUIT. Without this,
- the server becomes removed from the network and the client list,
- but the connection isn't shut down at all ...
- Handle unknown user and channel modes: these modes are saved and
forwarded to other servers, but ignored otherwise.
- Handle channel user modes 'a', 'h', and 'q' from remote servers.
ngIRCd 0.0.1, 31.12.2001
- erste oeffentliche Version von ngIRCd als "public preview" :-)
-
-
---
-$Id: NEWS,v 1.88 2008/02/26 22:05:42 fw Exp $