+ngIRCd Release 19
+
+ - 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
+ user name. See "man 5 ngircd.conf" for details.
+ - Fixed handling of WHO commands. This fixes two bugs: "WHO <nick>"
+ returned nothing at all if the user was "+i" (reported by Cahata,
+ thanks) and "WHO <nick|nickmask>" returned channel names instead
+ of "*" when the user was member of a (visible) channel.
+ - LUSERS reply: only count channels that are visible to the requesting
+ client, so the existence of secret channels is no longer revealed by
+ using LUSERS. Reported by Cahata, thanks!
+ - Unknown user and channel modes no longer stop the mode parser, but
+ are simply ignored. Therefore modes after the unknown one are now
+ handled. This is how ircd2.10/ircd2.11/ircd-seven behave, at least.
+ 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)
+ - 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
+ be set and unset by IRC services like Anope.
+ - 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.
+ These channel user modes aren't used for anything at the moment,
+ but ngIRCd knows that these three modes are "channel user modes"
+ and not "channel modes", that is that these modes take an "nick name"
+ argument. Like unknown user and channel modes, these modes are saved
+ and forwarded to other servers, but ignored otherwise.
+
+ngIRCd Release 18 (2011-07-10)
+
+ - Add preliminary ngIRCd protocol module for Anope 1.9 to contrib/Anope/.
+
+ ngIRCd 18~rc2 (2011-06-29)
+ - GnuTLS: use 1024 bits as minimum size of the DH prime. This enables
+ ngIRCd to accept incoming connections from other servers and clients
+ that "only" use at least 1024 bits again, like ngIRCd 17 did (and no
+ longer requires 2048 bits for incoming connections).
+
+ ngIRCd 18~rc1 (2011-06-27)
+ - New configuration option "MorePrivacy" to "censor" some user information.
+ When enabled, signon time and idle time is left out. Part and quit
+ messages are made to look the same. WHOWAS requests are silently dropped.
+ All of this is useful if one wish to conceal users that access the ngircd
+ servers from TOR or I2P.
+ - New configuration option "ScrubCTCP" to scrub incoming CTCP commands. If
+ activated, the server silently drops incoming CTCP requests from both
+ other servers and from users. The server that scrubs CTCP will not forward
+ the CTCP requests to other servers in the network either, which can spell
+ trouble if not every oper knows about the CTCP-scrubbing. Scrubbing CTCP
+ commands also means that it is not possible to send files between users.
+ There is one exception to the CTCP scrubbing performed: ACTION ("/me
+ commands") requests are not scrubbed.
+ - Restructure ngIRCd configuration file: introduce new [Limits], [Options],
+ and [SSL] sections. The intention of this restructuring is to make the
+ [Global] section much cleaner, so that it only contains variables that
+ most installations must adjust to the local requirements. All the optional
+ variables are moved to [Limits], for configurable limits and timers of
+ ngIRCd, and [Options], for optional features. All SSL-related variables
+ are moved to [SSL] and the "SSL"-prefix is stripped. The old variables in
+ the [Global] section are deprecated now, but are still recognized.
+ => Don't forget to check your configuration, use "ngircd --configtest"!
+ - New documentation "how to contribute": doc/Contributing.txt.
+ - Avoid needlessly scary 'buffer overflow' messages: When the write buffer
+ space grows too large, ngIRCd has to disconnect the client to avoid
+ wasting too much memory, which is logged with a scary 'write buffer
+ overflow' message. Change this to a more descriptive wording.
+ - New configuration option "RequireAuthPing": PING-PONG on login. When
+ enabled, this configuration option lets ngIRCd send a PING with an numeric
+ "token" to clients logging in; and it will not become registered in the
+ network until the client responds with the correct PONG.
+ - New configuration option "NoticeAuth": send NOTICE AUTH on connect. When
+ active, ngircd will send "NOTICE AUTH" messages on client connect time
+ like e.g. snircd (QuakeNet) does.
+ - Add support for up to 3 targets in WHOIS queries, also allow up to one
+ wildcard query from local hosts. Follows ircd 2.10 implementation rather
+ than RFC 2812. At most 10 entries are returned per wildcard expansion.
+ - ngircd.conf(5) manual page: describe types of configuration variables
+ (booleans, text strings, integer numbers) and add type information to each
+ variable description.
+ - Terminate incoming connections on HTTP commands "GET" and "POST".
+ - New configuration option "CloakHost": when set, this hostname is used for
+ every client instead of the real DNS hostname (or IP address).
+ - New configuration option "CloakUserToNick": when enabled, ngIRCd sets
+ every clients' user name to their nick name and hides the user name
+ supplied by the IRC client.
+ - Make write buffers bigger, but flush early. Before this change, a client
+ got disconnected if the buffer flushing at 4k failed, now regular clients
+ can store up to 32k and servers up 64k even if flushing is not possible at
+ the moment. This enhances reliability on slow links.
+ - Allow "Port = 0" in [Server] blocks. Port number 0 marks remote servers
+ that try to connect to this daemon, but where this daemon never tries to
+ establish a connection on its own: only incoming connections are allowed.
+ - Enable WHOIS command to return information about services.
+ - Implement channel mode 'O': "IRC operators only". This channel mode is
+ used on DALnet (bahamut), for example.
+ - Remove support for ZeroConf/Bonjour/Rendezvous service registration
+ including the "[No]ZeroConf" configuration option.
+ - Deprecate NoXX-Options in ngircd.conf and move new variants into our new
+ [Options] section: 'NoDNS=no' => 'DNS=yes', 'NoIdent=no' => 'Ident=yes',
+ 'NoPAM=no' => 'PAM=yes', and 'NoZeroConf=no' => 'ZeroConf=yes' (and
+ vice-versa). The defaults are adjusted accordingly and the old variables
+ in [Global] are still accepted, so there is no functional change.
+
+ngIRCd Release 17.1 (2010-12-19)
+
+ - Don't log critical (or worse) messages to stderr
+ - Remove "error file" when compiled with debug code enabled
+ - New numeric 329: get channel creation time on "MODE #chan" commands
+
+ngIRCd Release 17 (2010-11-07)
+
+ - doc: change path names in sample-ngircd.conf depending on sysconfdir
+
+ ngIRCd 17~rc2 (2010-10-25)
+ - Generate ngIRCd version number from GIT tag.
+ - Make sourcecode compatible with ansi2knr again. This allows to compile
+ ngIRCd using a pre-ANSI K&R C compiler again.
+
+ ngIRCd 17~rc1 (2010-10-11)
+ - New configuration option "NoZeroConf" to disable service registration at
+ runtime even if ngIRCd is compiled with support for ZeroConf (e.g. using
+ Howl, Avahi or on Mac OS X).
projects / ngircd-alex.git / blobdiff