Changelog for ngircd-24-2.29.i586.rpm :

* Wed Jan 24 2018 9+suseAATTcirno.systems- Do not restart on update There is no support for retaining state across restarts and a restart will cause service interruption, so it is better to handle this manually via zypper ps -s.
* Tue May 09 2017 vodooAATTvakw.ch- Upgrade to version 24
* Sat Feb 13 2016 vodooAATTvakw.ch- Upgrade to version 23
* Thu Jan 22 2015 vodooAATTvakw.ch- In ngircd.conf disabled use of ident by default
* Thu Jan 22 2015 vodooAATTvakw.ch- Updated systemd service file for service invocation to make it more systemd compatible. Forking => simple- Update of cipher list in ngircd.conf
* Mon Jan 19 2015 vodooAATTvakw.ch- Upgrade to version 22 Match all list patterns case-insensitive: this affects the invite-, ban-, and except lists, as well as G-Lines an K-Lines.
* Sun Jun 22 2014 vodooAATTvakw.ch- Upgrade to release 21.1- Differences to version 20.x:
* Starting with ngIRCd 21, the ciphers used by SSL are configurable and default to HIGH:!aNULL:AATTSTRENGTH (OpenSSL) or SECURE128 (GnuTLS). Previous version were using the OpenSSL or GnuTLS defaults, DEFAULT and NORMAL respectively.
* When adding GLINE\'s or KLINE\'s to ngIRCd 21 (or newer), all clients matching the new mask will be KILL\'ed. This was not the case with earlier versions that only added the mask but didn\'t kill already connected users.
* Tue Sep 10 2013 vodooAATTvakw.ch- Use openssl instead of gnutls
* Fri Aug 23 2013 vodooAATTvakw.ch- Upgrade to bugfix release 20.3 (2013-08-23)- Upstream changes:
* Security: Fix a denial of service bug (server crash) which could happen when the configuration option \"NoticeAuth\" is enabled (which is NOT the default) and ngIRCd failed to send the \"notice auth\" messages to new clients connecting to the server (CVE-2013-5580).
* Fri Feb 15 2013 vodooAATTvakw.ch- Upgrade to bugfix release 20.2 (2013-02-15)- Upstream changes:
* Security: Fix a denial of service bug in the function handling KICK commands that could be used by arbitrary users to to crash the daemon (CVE-2013-1747).
* WHO command: Use the currently \"displayed hostname\" (which can be cloaked!) for hostname matching, not the real one. In other words: don\'t display all the cloaked users on a specific real hostname!
* configure: The header file \"netinet/in_systm.h\" already is optional in ngIRCd, so don\'t require it in the configure script. Now ngIRCd can be built on Minix 3 again :-)
* Return better \"Connection not registered as server link\" errors: Now ngIRCd returns a more specific error message for numeric ERR_NOTREGISTERED(451) when a regular user tries to use a command that isn\'t allowed for users but for servers.
* Don\'t report ERR_NEEDMOREPARAMS(461) when a MDOE command with more modes than nicknames is handled, as well as for channel limit and key changes without specifying the limit or key parameters. This is how a lot (all?) other IRC servers behave, including ircd2.11, InspIRCd, and ircd-seven. And because of clients (tested with Textual and mIRC) sending bogus MODE commands like \"MODE -ooo nick\", end-users got the expected result as well as correct but misleading error messages ...
* Correctly detect when SSL subsystem must be initialized and take outgoing connections (server links!) into account, too.
* autogen.sh: Enforce serial test harness on GNU automake >=1.13. The new parallel test harness which is enabled by default starting with automake 1.13 isn\'t compatible with our test suite. And don\'t use \"egrep -o\", insetead use \"sed\", because it isn\'t portable and not available on OpenBSD, for example.