~steering/inspircd++.git, branch v2.0.25 Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/?h=v2.0.25 2017-11-12T15:55:01Z Release v2.0.25 2017-11-12T15:55:01Z Peter Powell 2017-11-12T15:55:01Z urn:sha1:53d822a7d19aded988ee74eb05437e587cb1ac92 Don't mess with the encoding of extras modules in modulemanager. 2017-11-12T14:33:08Z Peter Powell 2017-11-12T14:33:08Z urn:sha1:c2f9865bb8807c006b5ab12ff7a051168bda9047 This fixes installing extras modules such as m_qrcode which contain characters from outside of the Unicode Basic Multilingual Plane. Various minor documentation fixes. 2017-11-12T12:24:57Z Peter Powell 2017-11-12T11:58:49Z urn:sha1:a137eb1c2649e702efee7cb1a50b4da467f9d4bd - Remind admins that not setting a DIE/RESTART password does not disable use of those commands. - Remove references to 1.2 and modules being able to create custom logging methods. This was never implemented in the 2.0 branch. - Remove references to an SASL improvement that was reverted. - Update various InspIRCd website links to use HTTPS over HTTP. - Update a link to the IRCv3 website to point to the new website. Work around removing shuns on nicks when the nick is online. 2017-11-09T11:16:32Z Peter Powell 2017-11-07T18:18:35Z urn:sha1:f57dbb6dbe0a49b0f0aa80c327904d4273a76b55 Revert the code changes to m_sasl made in commit 9d4b4344b4. 2017-11-09T11:11:14Z Peter Powell 2017-11-09T11:04:52Z urn:sha1:e83506b7abde9fdd628b9065fb3b6c01d370808f This is causing problems such as duplicate 904 messages. Merge pull request #1255 from genius3000/insp20+timedbans 2017-11-07T14:15:50Z Peter Powell 2017-11-07T14:15:50Z urn:sha1:8f83c6709fa531e4d1ff323eb35cd6d394419b17 2.0: Fix various inconsistencies in m_timedbans. Improve (synchronize) the notices in m_timedbans 2017-11-07T05:27:14Z genius3000 2016-11-22T05:00:27Z urn:sha1:3eefb336c670d5b2f39696913717e0c47b75232c * Send to remote servers upon setting * Send to halfop if available upon expiry Merge pull request #1359 from genius3000/insp20+sasl_no_server 2017-11-06T11:11:22Z Peter Powell 2017-11-06T11:11:22Z urn:sha1:9375c633371ee8d25adc5cf756590077e5100bb5 2.0: Inform the client when a SASL message cannot be sent Inform the client when a SASL message cannot be sent 2017-11-06T02:51:22Z genius3000 2017-07-27T09:05:44Z urn:sha1:9d4b4344b49de3c474302e8316576b759249c409 When SASL is properly configured with a 'target' server, we are able to inform the client when the message fails to send. Currently if a target is configured and it is offline, no response is sent. This can cause some clients to time out while waiting for a response. If a target isn't configured, behaviour will not change with this commit. The default of '*' will still send to all servers. Updated example config with 'target' variable. Use InvalidateCache in the sockaddrs overload of OnSetClientIP. 2017-11-05T23:05:24Z Peter Powell 2017-10-22T22:51:15Z urn:sha1:52de083afcd1608f030551f532bdcdb1f45f1513 This was done to the string variant in d3b82b2f7f.