https://github.com/solanum-ircd/solanum https://cgit.space/~irc/github.com/solanum-ircd/solanum.git/atom/NEWS.md?h=amdj%2Fmodules 2024-06-12T19:35:19Z 2024-06-12T19:35:19Z Aaron Jones 2024-03-16T15:24:27Z urn:sha1:484fd9051ec93a86e48371ac4e0eec690b99ee48 2022-10-06T21:06:28Z Ed Kellett 2021-10-16T23:00:55Z urn:sha1:06c53095343c2756208f6398bb7e00fb2cbe46dd This doesn't make sense in a world where post-registration SASL is allowed, and should fix one case of an annoying login desync that's seen in the real world. Specifically, when a client sends its final AUTHENTICATE and Atheme receives it, it sends an SVSLOGIN for that client. If the client sends us its CAP END *before* we see the SVSLOGIN, the implicit abort will try to abort the SASL session that's already succeeded. Atheme interprets this as an instruction to forget about the successful SASL session; you'll connect unidentified. But it's already sent SVSLOGIN, which will log the client in ircd-side, causing ircd and services views to differ until the user authenticates again manually. I think allowing a SASL session to be aborted when it has already succeeded is an Atheme bug, and it can still be triggered without this change. But our behaviour here seems silly anyway. 2021-01-28T14:09:31Z Taavi Väänänen 2021-01-28T14:09:31Z urn:sha1:d04ed5c53f54a506ca695d8da33c21bedb82b921 Split oper:wallops right from oper:mass_notice. Update documentation and examples to grant oper:wallops everywhere oper:mass_notice was granted. closes #103 2020-11-04T18:08:56Z Ed Kellett 2020-11-04T11:16:03Z urn:sha1:faf98b8e2040271c523a09ccba009ee320b6b848 2020-10-28T15:32:35Z Ed Kellett 2020-10-28T13:28:55Z urn:sha1:6ec9c49fc3d71caeda6bb0fe90758e30356ee610 2019-08-31T20:14:27Z Simon Arlott 2019-08-31T20:14:27Z urn:sha1:9ac03907343abe6c55c93e2afc48f3ff7566f4bb 2019-08-31T20:12:44Z Simon Arlott 2019-08-31T20:12:44Z urn:sha1:efe1f312b5e7e7fab9f713b92a96d7a2b14a5b64 2018-08-15T22:12:38Z Simon Arlott 2018-08-15T22:12:38Z urn:sha1:ac5a5a0cfabf7db7a24641b4bc9a94e4d849d94d 2018-08-15T22:03:50Z Simon Arlott 2018-08-15T22:00:26Z urn:sha1:17776e527456014d892124fbb4e4f1ebe58c1353 2018-01-18T21:45:32Z Simon Arlott 2018-01-18T21:45:32Z urn:sha1:fd668f9d9ee1c2caf34e704d9b72cbb691d3b728