unreal-notify Mailing List for UnrealIRCd
Status: Beta
Brought to you by:
wildchild
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2002 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2004 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
(4) |
| 2016 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(3) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
(2) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(3) |
| 2019 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(1) |
| 2020 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2021 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
(3) |
Nov
(4) |
Dec
(3) |
| 2022 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
| 2023 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(4) |
Nov
|
Dec
(4) |
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2025 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
(2) |
| 2026 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
(4) |
Dec
|
|
From: Bram M. <sy...@un...> - 2026-11-14 12:22:26
|
Hi everyone, Last weekend was quite an event! Having to do an upgrade as an admin, with a tight deadline, is never fun but everyone I spoke to was very understanding. In this new era of AI every project has to deal with urgent security releases. I want to thank everyone for their kind words, donations even, and spreading the word about the hot-patch and 6.2.7.1 upgrade. First things first: the webpanel <https://www.unrealircd.org/docs/UnrealIRCd_webpanel> had a security release today. That's not UnrealIRCd itself, but a separate project, and only a few dozen people use it. If you do use it, please upgrade the webpanel <https://github.com/unrealircd/unrealircd-webpanel/releases> to v1.1.1. And now what this e-mail is actually about: the Release Candidate for future version 6.2.8 is available for testing! You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/. We hope to do a 6.2.8 stable release at the end of this month. On *NIX you can use ./unrealircd upgrade --rc to upgrade to this Release Candidate. You can download releases from unrealircd.org <https://www.unrealircd.org>. IMPORTANT: If you use a webchat that connects directly to UnrealIRCd with websockets then you MUST add it to set::websocket::allowed-origins. See the first item under /Changes/. Enhancements: * Automatic server bans now have a "source", which shows up in the log, like: |[source: blacklist]|. * A |WHOIS| by an IRCOp now shows the websocket origin and WEBIRC gateway * A ton of spamreport <https://www.unrealircd.org/docs/Spamreport_block> changes: o A spamreport block can now report automatically, via the new option spamreport::auto-report <https://www.unrealircd.org/docs/Spamreport_block>. The main sources are: + |spamfilter|: when a spamfilter kills or *LINEs a user. The spamfilter itself is included in the report. + |antimixedutf8|: when antimixedutf8 takes action, eg blocks a message. + |server-ban|: when an online user is banned (eg /GLINE by an oper) [*] + |kill|: when a user is killed (eg /KILL by an oper) [*] For Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> all four on by default. For other spamreport blocks it is off by default. To turn it off, you put in the spamreport block: |auto-report { }|. You can exempt specific users from being auto reported at all through set::spamreport::auto-report::except <https://www.unrealircd.org/docs/Set_block#set::spamreport>. [*]: Not all server bans and kills are sent in, only if the ban or kill reason contains the word "spam". This can be configured via set::spamreport::auto-report::ban-or-kill-filter <https://www.unrealircd.org/docs/Set_block#set::spamreport>. o The |SPAMREPORT| command now has an optional reason: |SPAMREPORT <nick|ip> [name-of-spamreport-block|all] [reason]| o For spamreport blocks of type simple you can now use |$source|, |$reason| and |$spamfilter_id| in the URL. Changes: * Websocket connections from browsers are now refused, unless the website is listed in set::websocket::allowed-origins <https://www.unrealircd.org/docs/Set_block#set::websocket>. o If you have a webchat that connects directly to UnrealIRCd using websockets, then be sure to add it through: |set { websocket { allowed-origins { webchat.example.net; } } }| o If the websocket module is loaded but no allowed-origins are configured we print out a warning. o Clients that are rejected show up in the log at a rate of max 1/min. o Clients that do not send an Origin header are still allowed in (non-browsers). o We always block |Origin: null|, eg when testing from a file:// page. * The per-listen block |listen::options::websocket::allow-origin| moved to this new setting. The old setting gives a config error. * Link blocks with |link::outgoing| that use a password (not spkifp/certfp/cert) will now raise a warning. We have already been warning about this since 2017 at link time so this should not be a surprise for anyone. In Q1 2027 this will become an error. o Link blocks without spkifp/certfp/cert allow a man-in-the-middle attack <https://en.wikipedia.org/wiki/Man-in-the-middle_attack>. o Please refer to our linking guide <https://www.unrealircd.org/docs/Linking_servers_(genlinkblock)> on how to link two unrealircd servers securely. It's very simple. o Link blocks without an outgoing section, or link blocks that link to localhost, are exempt. You can also manually exempt a link block via link::options::no-certificate-verification. Only do so if you insist to link without cert validation, for example when you are linking over a VPN. * JSON-RPC: a connection from an IP that does not match any rpc-user block <https://www.unrealircd.org/docs/Rpc-user_block> is now closed immediately, even before the TLS handshake starts. This means |rpc-user::match| may only contain |ip| or |mask| items. * We continue the gradual transition from |geoip_classic| to |geoip_mmdb|. Now also for |./Config -quick| (and thus |./unrealircd upgrade|). This because we will stop database updates for classic in mid-2027. * You now get a config error if you use |action { gline; report; }|. This because |report| (and |set|) cannot happen after a user is killed. The correct syntax is: |action { report; gline; }| * Update shipped libs: PCRE2 (10.49) * The tkldb database now saves ban sources. The downside is that you cannot downgrade to 6.2.7.1 or older without losing your tkldb. Fixes: * Crash with an alias of |type channel| (we don't ship with any by default) * Crash in JSON-RPC |whowas.get| with an |ip| filter * Crash with certain empty config values, eg |match { country ""; }| * |./unrealircd hot-patch| could fail after a distro upgrade that came with a newer compiler. We now always compile with |-std=gnu17| if the compiler supports it. * On FreeBSD |./unrealircd hot-patch| did not work and (even worse) it reported success. * Aliases like |NS| which have |type services| could deliver to an ordinary user if they were called |NickServ|. Note that this was only possible if Services were down and you had no Q-lines for such nicks. Anope adds such Q-lines automatically. * If sending a DNS query failed (eg no route to the DNS server), a client would hang and time out after 40 seconds. This would be rare. Normal DNS failures, like a timeout or NXDOMAIN, were unaffected. * Channel messages to a prefix were sent to the wrong users. For example, |~#channel| messages were delivered to +vhoaq, and messages to |+#channel| were delivered to +hoaq. * Extended server bans <https://www.unrealircd.org/docs/Extended_server_bans> did not work if the value contained a |@| (eg |~realname:*@*|) or when the value was an actual IP address (eg |~realname:1.2.3.4|). Note that if you add such bans now, they won't work on 6.2.7 or older servers that are linked. * Clients on a UNIX socket listener (eg for Tor or I2P) never got a registration timeout, keeping many unregistered connections open. * In 6.2.x every server ban was accidentally reported to all spamreport blocks (including Central Spamreport). That could have been especially bad if you had a spamreport block with type |dronebl|. Developers and protocol: * Numeric 350 (RPL_WHOISGATEWAY) now shows the websocket origin and WEBIRC gateway to IRCOps, similar to InspIRCd: |:irc.example.net 350 x whoisuser * * :is connecting from WebSocket origin webchat.example.net| |:irc.example.net 350 x whoisuser gw.example.org 192.0.2.1 :is connecting via WebIRC gateway kiwiirc| * JSON-RPC: o An exception in spamfilter objects previously showed as |match| (which is super confusing). It is now under |except|. o TKL entries now have a |source| for automatic server bans. * In JSON-logging with DEBUGMODE, the file field in the log is now |source_code| instead of |source|. This so it does not conflict with the TKL |source|. * New hook |HOOKTYPE_KILLED_CLIENT|, called when a local user is killed. * In |HOOKTYPE_BANNED_CLIENT| there is now a |TKL *tkl| parameter (this is NULL when a ban is not a TKL, such as a realname ban). * The function |take_action()| changed and has two more parameters. And, |take_action_ex()| which was added in 6.2.6 is removed again. * New functions that may be useful for module coders: |find_user_on_server()|, |read_name_list_file()|, |cleanline()|, |strip_trailing_whitespace()|, |str_is_all_digits()|, |unreal_encodespace_r()| and |unreal_decodespace_r()|. * S2S: the websocket origin and the WEBIRC gateway name, IP and host are synced via (early) moddata. * S2S: we now communicate the TKL source through the |s2s-tkl/source| message tag. |
|
From: Bram M. <sy...@un...> - 2026-11-08 11:33:40
|
We are seeing bad guys exploiting this issue on the internet right now. Hopefully everyone has hot-patched or updated their server, or at the very least has the spamfilter workaround deployed. If not, do so ASAP! I have tried hard to reach everyone: the pre-announcement 4 days ago, making clear it is a critical issue and getting everyone ready for Saturday. Then the easy workaround and patching without restart (below). Plus e-mailing admins of hundreds of UnrealIRCd servers directly, both before the release and two hours after. If you know other people who run UnrealIRCd, please forward this message to them. Thanks! On Sat 07-11-2026 15.57, Bram Matthys wrote: > > Hi everyone, > > During an internal audit, with the help of AI, several important > security issues were found in UnrealIRCd. > > The critical issue (CVE-2026-114713) allows normal users to execute > commands with server/IRCOp authority. This means any ordinary user can > KILL, GLINE, and do many more bad things. This is the most critical > issue found in UnrealIRCd in the past 15 years. The other security > issues are crashes, hangs, DoS and there is also an issue fixed which > allows any ordinary user to "decloak" a user (reveal the IP address of > the victim). > > As promised, on almost all UnrealIRCd 6 networks all these security > issues can be hot-patched without restart (no downtime). > > If you are running UnrealIRCd versions that are end of life: > UnrealIRCd 3.2.x, 4 or 5 then see the section near the end. > > _IMPORTANT: Please do *step 1 first*, it gives you some protection > right away. Then proceed to step 2a or 2b._ > > *Step 1: First, apply the workaround right now* > > Before you do anything, run the following as an IRCOp on the network: > > /SPAMFILTER add -regex T block - Invalid_label ^label=(?![^\r\n;\x20]*\z) > > This protects all linked servers on the IRC network against the > critical issue, but only if all your servers are on 6.0.4 or newer. > Even so, you still need to fix the other 8 security issues, so don't > just stop here, see next. > > Now go to step 2a (hot-patch) or if that is not for you then use step > 2b (upgrade to 6.2.7.1) instead. > > *Step 2a: Fix the issues without restart* > > If you are on Windows, or you are on *NIX but hot-patching below > fails, then go to step 2b (upgrade). > > Run the following command on every UnrealIRCd server. This works on > UnrealIRCd 6.0.0 - 6.2.7: > > ./unrealircd hot-patch bundle-20261107 > > When you run that command, the last sentence you should see on that > screen should be "Patch installed and server rehashed correctly. All > should be good now!" or in older versions "Done! All should be good now". > > If something went wrong (you did not get that output) then please > check out FAQ: Hot-patching failed > <https://www.unrealircd.org/docs/FAQ#hot-patch-failed>. It contains > answers for several scenarios, including a distro upgrade case which > can break the build. > > Now, you still want to verify that you are really patched. To do so, > you can run this on the same shell (this only works on 6.0.2 and later): > > ./unrealircd module-status|grep labeled-response > > Then check the output: > > * This means the hot-patch is properly installed (server is safe): > labeled-response *5.0-hot-patch-bundle-20261107* > * If it says 6.2.7.1 then the server was not hot-patched but is > running the fixed version 6.2.7.1 (server is also safe) > * If it says only 5.0 (without the patch bundle) then the hot-patch > was NOT applied. > * If you get no output at all then try the IRC method, see next. > > You can check the same on IRC through "MODULE -all" as an IRCOp and > then CTRL+F on labeled-response > You can also check remote IRC servers (again, as IRCOp), through: > MODULE -all remote.server.name > > If the verification failed, check out the FAQ: Hot-patching failed > <https://www.unrealircd.org/docs/FAQ#hot-patch-failed> or simply do > step 2b (upgrade instead). > > *Step 2b: OR, upgrade to 6.2.7.1 (with restart)* > > If using the hot-patch is not possible or didn't work, then upgrade to > 6.2.7.1: > > On *NIX you can simply run: ./unrealircd upgrade > And after that, restart the IRC server. > > Windows users, or anyone else who prefers doing so, can also download > the 6.2.7.1 release from www.unrealircd.org <https://www.unrealircd.org/>. > > *Full list of fixed issues* > > For completeness, here are the 9 issues that are fixed through the > hot-patch and in 6.2.7.1: > > 1. A CRITICAL issue that can be abused by any normal user to execute > commands with server or IRCOp authority. This means any ordinary > user can KILL, GLINE, and do many more bad things. (CVE-2026-114713) > 2. A normal user could "decloak" another user, revealing the IP > address of the victim. > 3. Another leak of the IP address > 4. Blacklist recheck could hang the server > 5. Crash on CHGIDENT from Services, which a normal user can trigger > 6. Counting error which could cause a "This server is full" message > to every new connect, until the server is restarted. > 7. Limit the number of bans Services can set, to 2x set::maxbans > 8. Potential flood issue with TLS renegotiations > 9. Possible crash on whowasdb > > *Note to UnrealIRCd 5 and other EOL versions* > > UnrealIRCd 5 is similarly affected by the critical issue (so any > regular user can execute commands as server/IRCOp). Note that > UnrealIRCd 5 has been End of Life since 2023-07-01. Nobody should be > running this version. > If you do use UnrealIRCd 5, the workaround is adding this to your > configuration file on all your servers AND restarting them (NOT > rehash): blacklist-module "labeled-response"; > > Other End of Life UnrealIRCd versions have not been checked. It is > likely that several bugs that are fixed in 6.2.7.1 go all the way back > to 3.2.x. > > Please read the next section as well, as you are _not safe_ if you run > an EOL version. You are not safe at all. > > *Final words: the danger of AI is real* > > I have been doing security audits on UnrealIRCd for decades now. Back > in 2001 I was using static code analyzer tools and found a bunch of > crashes. Later on in the 2010's fuzzing was the new big thing and when > I used it on UnrealIRCd it found lots of issues again. Then AI came. > First the quality of AI was not so good but things improved and > improved. Since Feb 2026 I have spent about 100 hours with AI doing > security audits and to improve the quality of the codebase. Especially > the last month things have been wild. The things AI can find nowadays > are amazing. > > I genuinely think that, if you are running any network daemon that has > not seen any major security fixes in the past couple of months, then > nobody has been poking at that daemon with AI. Or some bad guy did but > did not report back. This is also true for people running End of Life > UnrealIRCd releases: you think your 3.2.x has no vulnerabilities? It > is only because bad guys haven't been looking at exploiting your > servers. You should not be running EOL software. Upgrade to UnrealIRCd > 6. It's a modern IRC server, it's worth it. > > *Updates* > > Any updates to this advisory will be posted in this thread on the > forums <https://forums.unrealircd.org/viewtopic.php?t=9487>. > > Best regards and thank you for using UnrealIRCd, > > Bram Matthys > > |
|
From: Bram M. <sy...@un...> - 2026-11-07 14:57:18
|
Hi everyone, During an internal audit, with the help of AI, several important security issues were found in UnrealIRCd. The critical issue (CVE-2026-114713) allows normal users to execute commands with server/IRCOp authority. This means any ordinary user can KILL, GLINE, and do many more bad things. This is the most critical issue found in UnrealIRCd in the past 15 years. The other security issues are crashes, hangs, DoS and there is also an issue fixed which allows any ordinary user to "decloak" a user (reveal the IP address of the victim). As promised, on almost all UnrealIRCd 6 networks all these security issues can be hot-patched without restart (no downtime). If you are running UnrealIRCd versions that are end of life: UnrealIRCd 3.2.x, 4 or 5 then see the section near the end. _IMPORTANT: Please do *step 1 first*, it gives you some protection right away. Then proceed to step 2a or 2b._ *Step 1: First, apply the workaround right now* Before you do anything, run the following as an IRCOp on the network: /SPAMFILTER add -regex T block - Invalid_label ^label=(?![^\r\n;\x20]*\z) This protects all linked servers on the IRC network against the critical issue, but only if all your servers are on 6.0.4 or newer. Even so, you still need to fix the other 8 security issues, so don't just stop here, see next. Now go to step 2a (hot-patch) or if that is not for you then use step 2b (upgrade to 6.2.7.1) instead. *Step 2a: Fix the issues without restart* If you are on Windows, or you are on *NIX but hot-patching below fails, then go to step 2b (upgrade). Run the following command on every UnrealIRCd server. This works on UnrealIRCd 6.0.0 - 6.2.7: ./unrealircd hot-patch bundle-20261107 When you run that command, the last sentence you should see on that screen should be "Patch installed and server rehashed correctly. All should be good now!" or in older versions "Done! All should be good now". If something went wrong (you did not get that output) then please check out FAQ: Hot-patching failed <https://www.unrealircd.org/docs/FAQ#hot-patch-failed>. It contains answers for several scenarios, including a distro upgrade case which can break the build. Now, you still want to verify that you are really patched. To do so, you can run this on the same shell (this only works on 6.0.2 and later): ./unrealircd module-status|grep labeled-response Then check the output: * This means the hot-patch is properly installed (server is safe): labeled-response *5.0-hot-patch-bundle-20261107* * If it says 6.2.7.1 then the server was not hot-patched but is running the fixed version 6.2.7.1 (server is also safe) * If it says only 5.0 (without the patch bundle) then the hot-patch was NOT applied. * If you get no output at all then try the IRC method, see next. You can check the same on IRC through "MODULE -all" as an IRCOp and then CTRL+F on labeled-response You can also check remote IRC servers (again, as IRCOp), through: MODULE -all remote.server.name If the verification failed, check out the FAQ: Hot-patching failed <https://www.unrealircd.org/docs/FAQ#hot-patch-failed> or simply do step 2b (upgrade instead). *Step 2b: OR, upgrade to 6.2.7.1 (with restart)* If using the hot-patch is not possible or didn't work, then upgrade to 6.2.7.1: On *NIX you can simply run: ./unrealircd upgrade And after that, restart the IRC server. Windows users, or anyone else who prefers doing so, can also download the 6.2.7.1 release from www.unrealircd.org <https://www.unrealircd.org/>. *Full list of fixed issues* For completeness, here are the 9 issues that are fixed through the hot-patch and in 6.2.7.1: 1. A CRITICAL issue that can be abused by any normal user to execute commands with server or IRCOp authority. This means any ordinary user can KILL, GLINE, and do many more bad things. (CVE-2026-114713) 2. A normal user could "decloak" another user, revealing the IP address of the victim. 3. Another leak of the IP address 4. Blacklist recheck could hang the server 5. Crash on CHGIDENT from Services, which a normal user can trigger 6. Counting error which could cause a "This server is full" message to every new connect, until the server is restarted. 7. Limit the number of bans Services can set, to 2x set::maxbans 8. Potential flood issue with TLS renegotiations 9. Possible crash on whowasdb *Note to UnrealIRCd 5 and other EOL versions* UnrealIRCd 5 is similarly affected by the critical issue (so any regular user can execute commands as server/IRCOp). Note that UnrealIRCd 5 has been End of Life since 2023-07-01. Nobody should be running this version. If you do use UnrealIRCd 5, the workaround is adding this to your configuration file on all your servers AND restarting them (NOT rehash): blacklist-module "labeled-response"; Other End of Life UnrealIRCd versions have not been checked. It is likely that several bugs that are fixed in 6.2.7.1 go all the way back to 3.2.x. Please read the next section as well, as you are _not safe_ if you run an EOL version. You are not safe at all. *Final words: the danger of AI is real* I have been doing security audits on UnrealIRCd for decades now. Back in 2001 I was using static code analyzer tools and found a bunch of crashes. Later on in the 2010's fuzzing was the new big thing and when I used it on UnrealIRCd it found lots of issues again. Then AI came. First the quality of AI was not so good but things improved and improved. Since Feb 2026 I have spent about 100 hours with AI doing security audits and to improve the quality of the codebase. Especially the last month things have been wild. The things AI can find nowadays are amazing. I genuinely think that, if you are running any network daemon that has not seen any major security fixes in the past couple of months, then nobody has been poking at that daemon with AI. Or some bad guy did but did not report back. This is also true for people running End of Life UnrealIRCd releases: you think your 3.2.x has no vulnerabilities? It is only because bad guys haven't been looking at exploiting your servers. You should not be running EOL software. Upgrade to UnrealIRCd 6. It's a modern IRC server, it's worth it. *Updates* Any updates to this advisory will be posted in this thread on the forums <https://forums.unrealircd.org/viewtopic.php?t=9487>. Best regards and thank you for using UnrealIRCd, Bram Matthys |
|
From: Bram M. <sy...@un...> - 2026-11-04 09:09:05
|
Hi everyone, On Sat 7 November 2026 at 15:00 UTC we will release UnrealIRCd 6.2.7.1 along with a hot-patch for UnrealIRCd 6 (no restart needed). This fixes multiple security issues in UnrealIRCd, including one issue rated as CRITICAL. We will send an announcement to the mailing list <https://sourceforge.net/projects/unreal/lists/unreal-notify>, do a post on the forums <https://forums.unrealircd.org/viewforum.php?f=1> and put it on the frontpage of unrealircd.org <https://www.unrealircd.org/>. Below is additional information, such as: how important it is to be around and who does not get the hot-patch. We also recommend today to run a hot-patch test (see below under "Recommended today: try a test hot-patch beforehand"). This way you can check if hot-patching works on your server. Installing the test hot-patch and how to verify installation is very similar to what needs to be done on Saturday with the real security patch so this also makes you familiar with the procedure. Should I be around that day, and what will I have to do? Yes, please be around at Saturday 7 November 2026 at 15:00 UTC. We HIGHLY recommend you do everything in the advice DIRECTLY after the announcement. Do not wait for hours or days. In the announcement there will be a workaround for the 1 critical issue and an ./unrealircd hot-patch command that you should run immediately after the workaround. The hot-patch can be used to fix all issues without restarting UnrealIRCd, with no impact on your users or uptime. Who will NOT get the hot-patch? Windows users: there will be no hot patch. You will have to install UnrealIRCd 6.2.7.1. This means on Windows you will have to restart your IRC server. If you are using git: you should know that we only support releases and the hot-patches are made for releases. If you cloned your git at a release point then hot patching may work, but if the git version you are using is like halfway between version X and Y then hot patching may fail. In that case either install 6.2.7.1 or do a git pull right after the release and recompile. Both require a restart. If you run a -rc/-beta version: this is similar to a git version. Hot-patching may fail, then you will need to install 6.2.7.1 and restart the server. Recommended today: try a test hot-patch beforehand All fixes come out as one hot-patch which works without a restart. A great mechanism, I even published an article on my blog <https://www.vulnscan.org/why-hot-patching-is-awesome/> about this, but this aside. However, in some semi-rare cases the hot-patch command may fail, such as after a distro upgrade. This is why we have published a TEST hot-patch. This hot-patch does not fix any particular bug. It just changes a version field in the "eos" module. To test, you run: ./unrealircd hot-patch hot-patch-test-6 When you run that command, the last sentence you should see on that screen should be "Patch installed and server rehashed correctly. All should be good now!" or in older versions "Done! All should be good now". If something went wrong (you did not get that output) then please check out FAQ: Hot-patching failed <https://www.unrealircd.org/docs/FAQ#hot-patch-failed>. It contains answers for several scenarios, including the distro upgrade and compiler case. Now you can verify that the module is actually the hot patched version. You have two options (pick one): * On the shell you can run: ./unrealircd module-status|grep -i eos * On IRC you can do "/MODULE -all" as an IRCOp. This outputs many lines, you will have to search for the line with /eos/ in it (hint: use CTRL+F if your client supports it). This means the test-patch is properly installed: eos *5.0-hot-patch-test-6* This means the test-patch is NOT installed: eos *5.0* If you use the IRC command then note that only IRCOps can see the version field and the "5.0" versus "5.0-hot-patch-test-6" difference. So be sure to run that command as an IRCOp. Perhaps good to know, you can also check remote servers: /MODULE -all irc2.example.net Updates / Questions Any updates to this pre-announcement will be done in this forum post <https://forums.unrealircd.org/viewtopic.php?t=9486>. Do you still have questions after reading this post then you can ask them there. Unfortunately more details about the security issues will not be provided, eg: the nature, area, exact affected version range, etc. But if you have a problem or question with the test hot-patch or something else about the procedure, then feel free to ask. Best regards, Bram Matthys (Syzop), UnrealIRCd. |
|
From: Bram M. <sy...@un...> - 2026-09-12 13:41:23
|
Hi everyone, This UnrealIRCd 6.2.7 release fixes multiple issues in the webserver module which allow an attacker to consume a lot of memory and stall the IRCd. If you use Websockets <https://www.unrealircd.org/docs/WebSocket_support> or JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC> then we recommend to either upgrade or *hot-patch*. A good strategy may be to hot-patch now to fix the most urgent issues and plan an upgrade to 6.2.7 at a more convenient time somewhere in the upcoming weeks. Fix without restart (hot-patch) The hot-patch allows you to update the server *without a restart* on UnrealIRCd 6.2.x and may also work on older (unsupported) versions. To do so, run: |./unrealircd hot-patch webserver-header-dos| Upgrade to the complete 6.2.7 release (with restart) Note that the hot-patch /only/ fixes the issues mentioned above. This release contains other fixes and enhancements. You can read all about it in the release notes below. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade to 6.2.7 (if you are ok with an ircd restart) with the command: ./unrealircd upgrade Enhancements: * New set::anti-flood <https://www.unrealircd.org/docs/Anti-flood_settings#max-processing-time> setting |max-processing-time|: this limits how much time we spend on a particular client in the I/O engine. This gives other clients a more fair chance to get their commands read and processed. Defaults to 25ms for unknown-users and 50ms for known-users. * IRCOps can use |WHO| with Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> for things like |WHO ~asn:64496|, |WHO ~country:NL| and |WHO ~security-group:unknown-users|. Changes: * Update shipped libs: c-ares (1.34.8, security fixes) * The GeoIP <https://www.unrealircd.org/docs/GeoIP> engine was already switched to |geoip_mmdb| in 6.2.4 for new installations. We now change the default for existing installations as well. The old engine |geoip_classic| is now deprecated and we will stop database updates for classic somewhere in 2027. * Added minimal self-check for Argon2 (fail early instead of crashing) Fixes: * Resource exhaustion attack in the webserver. Previously we had no restriction on HTTP request headers, so a client could make a big request which would consume a lot of memory and stall the IRCd. This only affects servers with a listen block with |listen::options::websocket| (for Websockets <https://www.unrealircd.org/docs/WebSocket_support>) or |listen::options::rpc| (for JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>). See the top of these release notes, especially the hot-patch. * Websocket pings were limited in size but not throttled * Crash when using crule functions <https://www.unrealircd.org/docs/Crule> |match_asname()| or when using |unicode_count('Nonexistent Block')|. * Crash with JSON-RPC method |rpc.del_timer| * Crash with |REHASH -dns| if linking to a server (race condition) * AntiMixedUTF8 <https://www.unrealircd.org/docs/Set_block#set::antimixedutf8> gave some emoji a way too high score. * Race condition in server linking. If a server was trying to link to multiple servers at once, then the servers could clash causing a connect+split. This could happen in the non-standard configuration where set::server-linking::autoconnect-strategy <https://www.unrealircd.org/docs/Set_block#set::server-linking> was set to |parallel| instead of the default |sequential|. This change means that |parallel| should now be safe to use. * The memory log, that JSON-RPC log.getall uses, was cleaned up too much. * Channel mode |+f| type |r| (repeat) has normalization (like ignoring upper/lowercase and color), but this normalization was accidently ignored. Developers and protocol: * New wiki articles: Dev:Coding guidelines <https://www.unrealircd.org/docs/Dev:Coding_guidelines> and Dev:Visual Studio Code <https://www.unrealircd.org/docs/Dev:Visual_Studio_Code>. * After more than 25 years, the entire source code has been reformatted in one big clang-format commit ('make format'), giving the whole tree a single consistent style. Git blame on github.com is unaffected thanks to |.git-blame-ignore-revs|. For local |git blame| to benefit as well, run this once in your working copy: |git config blame.ignoreRevsFile .git-blame-ignore-revs|. If you maintain a fork or local patches, then read the migration instructions in this commit message <https://github.com/unrealircd/unrealircd/commit/e77eb9e923e84853c0fb2a154150f401a9602e0b>. * All C code must now be formatted with clang-format version 21: run |make format| *before committing* (or use clang-format in your editor). CI will check for this and fail a PR containing unformatted code. * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC:Security_group> |security_group.list| and |security_group.get|: we now consistently have |builtin| on all built-in security groups, and a fix for missing |public| in unknown-users. Best regards, Bram Matthys, UnrealIRCd |
|
From: Bram M. <sy...@un...> - 2026-09-06 08:02:36
|
Hi everyone, On Saturday 12 September 2026 at 14:00 UTC we will release UnrealIRCd 6.2.7 along with a hot-patch for UnrealIRCd 6.2.x. This fixes a Denial of Service issue in a significant number of servers that was recently discovered during an internal audit. We will send an announcement to the mailing list <https://sourceforge.net/projects/unreal/lists/unreal-notify>, do a post on the forums <https://forums.unrealircd.org/> and put it on the frontpage of unrealircd.org <https://www.unrealircd.org/>, as usual with every release. It would be good to be around at that time. The hot-patch can then be used to fix the issue without restarting UnrealIRCd, with no impact on your users or uptime. Best regards, Bram Matthys, UnrealIRCd |
|
From: Bram M. <sy...@un...> - 2026-07-03 04:34:14
|
UnrealIRCd 6.2.6 enables multiline by default, adds TKL IDs and tracking of hit counts on *LINES/Spamfilter. New crule functions were added to fetch server flood counts. Guidance to admins for server linking with 'spkifp' has been improved. A crash bug in the multiline implementation in 6.2.4/6.2.5/6.2.6-rc1 has been fixed as well. Note that multiline was not enabled by default in 6.2.4/6.2.5. If you /only/ want to fix that issue then it is possible to run the following command on *NIX to patch it without a server restart: |./unrealircd hot-patch multiline-62x-crash| As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade to 6.2.6 with the command: ./unrealircd upgrade Enhancements: * IRCv3 draft/multiline <https://ircv3.net/specs/extensions/multiline> is now enabled by default. See the UnrealIRCd 6.2.4 release <https://github.com/unrealircd/unrealircd/blob/2475f2559623148cc2fa39ba7ceafb29b8b05904/doc/RELEASE-NOTES.md#unrealircd-624> for all information on what this feature does, the default limits, etc. To turn it off completely you can use: |blacklist-module multiline;| * Server bans and Spamfilters now have a unique ID, like |G7K2MP9WQX3|: o The first letter denotes the type: |G| for gline, |K| for kline, |Z| for (g)zline, |H| for shun. Spamfilter IDs start with |SPAM|. o The ID is shown to the affected user, so they can paste the ID back to network staff. It is |$banid| in set::reject-message <https://www.unrealircd.org/docs/Set_block#set::reject-message> and included by default. If you have a custom set::reject-message in your config file then you will have to add it in manually. o IRCOps see the ID in |STATS gline| and similar and can search for it with e.g. |STATS gline +i G7K2MP9WQX3|. o Spamfilters also have an ID, and we already had something similar that could be used for |SPAMFILTER del <id>| that was only local-server. For new spamfilters this is now a network wide ID. o When a server ban was placed by a spamfilter, |STATS gline| shows the originating spamfilter's ID, so it can be traced back. o The TKL ID and related Spamfilter ID (if any), also appear in log messages |TKL_ADD|, |TKL_DEL|, |TKL_EXPIRE| and |SPAMFILTER_MATCH|. o The |STATS gline| and other TKL stats changed format, see /Developers and protocol/ if you use scripts or your client depends on the exact numeric format. o For TKL IDs to reach all servers, all servers need to be on 6.2.6 or later, especially the hubs. If there is one server in-between that is older, then TKL IDs don't propagate properly and the ID will be empty. * Server bans and Spamfilters now track how often they are hit and the time of the last hit, eg in |STATS gline| for GLINEs. These counts happen on each individual server and are not network-wide. This allows IRCOps to see which entries never get any hits and can potentially be removed. o Important exception: config-based spamfilters/bans lose their counters on restart. o For non-config TKLs, the hit count and last hit timestamp are preserved across reboots (via tkldb). o Again, see /Developers and protocol/ for the exact STATS field. * New crule functions <https://www.unrealircd.org/docs/Crule> that return the number of times a flood was blocked for a user. o |server_flood_count('..setting..')| returns the number of times set::anti-flood settings were exceeded by that user. Available are: |away|, |nick|, |join|, |invite|, |knock|, |vhost| and |conversations|. Plus, there is |all| for the sum of all items. o |total_channel_flood_count('..setting..')| returns the number of times |+f|/|+F| limits were exceeded by that user in all channels the user is or was in. Available are: |nick|, |join|, |knock|, |msg|, |ctcp|, |text|, |repeat| and |paste| (and |all| for the sum). o All these are counted for the duration of the session (user connection). o These can be used in a security-group::rule or spamfilter::rule. Eg: |spamfilter { rule "server_flood_count('nick')>4"; reason "Nick flood"; action gline; ban-time 1h; }| * Central Spamreport now also receives those flood counters. Changes: * Server linking and certificates: we now treat listener blocks that are |serversonly| (such as port 6900 in the example.conf) and link { } blocks in a different way than regular listen { } blocks: o If there are different certificates used in the serversonly listen block vs link blocks, then this is almost always means server linking is broken, so we now print a warning on boot and rehash. o We also print an 'advice' if any of these are not using (long-lived) self-signed certificate. This is because CA issued certificates are typically not suitable because they typically rotate keys and thus change the |spkifp|. Changing spkifp breaks server linking. We will now print an advice along with command and config block instructions to fix it. o We now use |set::server-linking::tls-options| for link { } blocks and listen { } blocks that are |serversonly|. All the rest uses the |set::tls| settings by default (eg the regular listen { } block on 6697). + This means our guide on Using Let's Encrypt with UnrealIRCd <https://www.unrealircd.org/docs/Using_Let's_Encrypt_with_UnrealIRCd> and generic usage is more intuitive. You just set both set settings and then no longer need to use any tls-options in listen blocks or link blocks. The example conf has also been updated with this. + If |set::server-linking::tls-options| is not configured, it defaults to |set::tls|, so there is no unexpected behavior change for anyone. o In a future release we will make server linking with |spkifp| mandatory, so all of this helps with getting people ready for that, making such a future transition smooth. o The command |./unrealircd genlinkblock| now also deals with ECC + ML-DSA where you have multiple |password ".." { spkifp; }| entries. * Spamfilter regexes now use more sensible defaults in terms of "max effort", similar to what PHP has been using for years. This means very slow regexes will now raise a |SPAMFILTER_REGEX_ERROR| warning during execution if this happens (should be extremely rare). * The UnrealIRCd base directory (eg |~/unrealircd/|) is now created with 0700 permissions, just like most subdirectories were. * We now have |./unrealircd mkcert| which replaces |make pem| certificate/key generation. * Translation updates: |help.fr.conf| * CHATHISTORY now sends a |draft/chathistory-end| if the end of history has been reached (a recent spec improvement <https://github.com/unrealircd/unrealircd/pull/337>). * The IRCv3 reply <https://ircv3.net/specs/client-tags/reply> client tag and no-implicit-names <https://ircv3.net/specs/extensions/no-implicit-names> extensions have been ratified. During the transition period we support both. Fixes: * The following config items previously raised a config error: allow channel::except, deny channel::except and spamfilter::except. * deny channel::mask with a Mask item <https://www.unrealircd.org/docs/Mask_item> caused a config error. * Long multiline messages could be cut off when sent to clients that do not support multiline. * Hardening of the built-in HTTPS client * JSON-RPC: Remote RPC was broken and causing "not authorized" error messages. This was used by |server.rehash| and |server.module_list|. Plus, this release |user.get| under some circumstances. This is now fixed but requires the target server to be on UnrealIRCd 6.2.6. If the target server does not meet this condition then we error telling the server "does not support remote JSON-RPC". Developers and protocol: * If you use |CAP LS| instead of |CAP LS 302| then you will now miss various capabilities. We had to trim it down because only 302 and later allow responses that span multiple lines. If your client is still not using 302 then please do so soon (the IRCv3 spec is from Nov'2017). For this first change, you won't miss out much, but somewhere in the future this can become a real problem for you. * URL API: The OutgoingWebRequest |max_size| (introduced last release) now also caps file-backed downloads. Default for file-backed when left at 0 is 50MB (|DOWNLOAD_MAX_SIZE_FILE_BACKED|). For memory-backed, it stays at 1MB like in 6.2.5 (|DOWNLOAD_MAX_SIZE_MEMORY_BACKED|). * The |unreal_match()| function now has a 3rd argument |const char **error| for communicating regex errors back. Just set to |NULL| if you don't care. * Similarly, |unreal_create_match()| last argument is now |const char **error| (const was added). So when callers use that, their variable |char *err| needs to become |const char *err|. * If you do something to a user that would (potentially) move the user from |unknown-users| to |known-users| (or vice versa) then you should call |update_known_user_cache(client);| to update the known users cache. For example, if you have some authentication module that marks a user as IsLoggedIn. * TKL entries can now use message tags to carry extra data, similar to how |s2s-md| worked for early moddata, we have |s2s-tkl|. We have two at the moment: o |s2s-tkl/id|: network-wide unique ID for the TKL entry o |s2s-tkl/spamfilter_id|: for server bans, if they were set by spamfilter, the spamfilter TKL ID. o Example: |@s2s-tkl/id=xxxx;s2s-tkl/spamfilter_id=yyyy :server TKL .....| o Older servers will not pass these along, so for this functionality to work all servers need to be on latest version, especially your hub. * The TKL |STATS| numerics has more fields now, they are added right before last (so before the |:reason| or |:regex|): o |RPL_STATSGLINE| (223) ends with |hits lasthit spamfilter_id id :reason| o |RPL_STATSQLINE| (217) ends with |hits lasthit id :reason| o |RPL_STATSSPAMF| (229) ends with |lasthit lasthit_except id :regex| (which comes right after |hits hits_except|, which was already there) o |RPL_STATSEXCEPTTKL| (230) ends with |id :reason| o An absent id or spamfilter_id is sent as |-| o The hits/lasthit/lasthit_except show how often the TKL was hit and the timestamp of the last hit (the usual, unix time), or 0 for never. These counts are local to each server. * |banned_client()| has an extra parameter |const char *tklid| for the TKL ID (or NULL if none). * The tkldb database version is now 6260 and stores the id, spamfilter_id and the hit statistics (hit count and last-hit time per ban). Older databases still load. Downside: you cannot downgrade UnrealIRCd. * JSON for TKL entries (server logs and JSON-RPC) now includes |id|, and |spamfilter_id| for spamfilter-created server bans. * JSON-RPC |user.get| can now expose flood counters (see next). * JSON-RPC: We can now route |user.get| requests to the server that user is on. This so we can fetch all fields for that user (including flood counters, idle time, snomask) that are normally not available remotely. o We do this automatically in |user.get| when |object_detail_level| is 5+. o You can force this explicitly with |object_remote_fetch| set to |true|. So you can also use it with detail level 2 if you want, e.g. if you don't need the flood counters but do want the idle time. o When RRPC is not available we answer ourselves (so safe fallback, but you won't have the local-only fields). |
|
From: Bram M. <sy...@un...> - 2026-06-20 09:23:37
|
The Release Candidate for future version 6.2.6 is now available for testing. The stable version is scheduled two weeks from now. This version enables multiline by default, adds TKL IDs and tracking of hit counts on *LINES/Spamfilter. New crule functions were added to fetch server flood counts. Guidance to admins for server linking with 'spkifp' has been improved. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade --rc NOTE: the windows version of rc1 will be out a little later Enhancements: * IRCv3 draft/multiline <https://ircv3.net/specs/extensions/multiline> is now enabled by default. See the UnrealIRCd 6.2.4 release <https://github.com/unrealircd/unrealircd/blob/2475f2559623148cc2fa39ba7ceafb29b8b05904/doc/RELEASE-NOTES.md#unrealircd-624> for all information on what this feature does, the default limits, etc. To turn it off completely you can use: |blacklist-module multiline;| * Server bans and Spamfilters now have a unique ID, like |G7K2MP9WQX3|: o The first letter denotes the type: |G| for gline, |K| for kline, |Z| for (g)zline, |H| for shun. Spamfilter IDs start with |SPAM|. o The ID is shown to the affected user, so they can paste the ID back to network staff. It is |$banid| in set::reject-message <https://www.unrealircd.org/docs/Set_block#set::reject-message> and included by default. If you have a custom set::reject-message in your config file then you will have to add it in manually. o IRCOps see the ID in |STATS gline| and similar and can search for it with e.g. |STATS gline +i G7K2MP9WQX3|. o Spamfilters also have an ID, and we already had something similar that could be used for |SPAMFILTER del <id>| that was only local-server. For new spamfilters this is now a network wide ID. o When a server ban was placed by a spamfilter, |STATS gline| shows the originating spamfilter's ID, so it can be traced back. o The TKL ID and related Spamfilter ID (if any), also appear in log messages |TKL_ADD|, |TKL_DEL|, |TKL_EXPIRE| and |SPAMFILTER_MATCH|. o The |STATS gline| and other TKL stats changed format, see /Developers and protocol/ if you use scripts or your client depends on the exact numeric format. o For TKL IDs to reach all servers, all servers need to be on 6.2.6 or later, especially the hubs. If there is one server in-between that is older, then TKL IDs don't propagate properly and the ID will be empty. * Server bans and Spamfilters now track how often they are hit and the time of the last hit, eg in |STATS gline| for GLINEs. These counts happen on each individual server and are not network-wide. This allows IRCOps to see which entries never get any hits and can potentially be removed. o Important exception: config-based spamfilters/bans lose their counters on restart. o For non-config TKLs, the hit count and last hit timestamp are preserved across reboots (via tkldb). o Again, see /Developers and protocol/ for the exact STATS field. * New crule functions <https://www.unrealircd.org/docs/Crule> that return the number of times a flood was blocked for a user. o |server_flood_count('..setting..')| returns the number of times set::anti-flood settings were exceeded by that user. Available are: |away|, |nick|, |join|, |invite|, |knock|, |vhost| and |conversations|. Plus, there is |all| for the sum of all items. o |total_channel_flood_count('..setting..')| returns the number of times |+f|/|+F| limits were exceeded by that user in all channels the user is or was in. Available are: |nick|, |join|, |knock|, |msg|, |ctcp|, |text|, |repeat| and |paste| (and |all| for the sum). o All these are counted for the duration of the session (user connection). o These can be used in a security-group::rule or spamfilter::rule. Eg: |spamfilter { rule "server_flood_count('nick')>4"; reason "Nick flood"; action gline; ban-time 1h; }| * Central Spamreport now also receives those flood counters. Changes: * Server linking and certificates: we now treat listener blocks that are |serversonly| (such as port 6900 in the example.conf) and link { } blocks in a different way than regular listen { } blocks: o If there are different certificates used in the serversonly listen block vs link blocks, then this is almost always means server linking is broken, so we now print a warning on boot and rehash. o We also print an 'advice' if any of these are not using (long-lived) self-signed certificate. This is because CA issued certificates are typically not suitable because they typically rotate keys and thus change the |spkifp|. Changing spkifp breaks server linking. We will now print an advice along with command and config block instructions to fix it. o We now use |set::server-linking::tls-options| for link { } blocks and listen { } blocks that are |serversonly|. All the rest uses the |set::tls| settings by default (eg the regular listen { } block on 6697). + This means our guide on Using Let's Encrypt with UnrealIRCd <https://www.unrealircd.org/docs/Using_Let's_Encrypt_with_UnrealIRCd> and generic usage is more intuitive. You just set both set settings and then no longer need to use any tls-options in listen blocks or link blocks. The example conf has also been updated with this. + If |set::server-linking::tls-options| is not configured, it defaults to |set::tls|, so there is no unexpected behavior change for anyone. o In a future release we will make server linking with |spkifp| mandatory, so all of this helps with getting people ready for that, making such a future transition smooth. o The command |./unrealircd genlinkblock| now also deals with ECC + ML-DSA where you have multiple |password ".." { spkifp; }| entries. * Spamfilter regexes now use more sensible defaults in terms of "max effort", similar to what PHP has been using for years. This means very slow regexes will now raise a |SPAMFILTER_REGEX_ERROR| warning during execution if this happens (should be extremely rare). * The UnrealIRCd base directory (eg |~/unrealircd/|) is now created with 0700 permissions, just like most subdirectories were. * We now have |./unrealircd mkcert| which replaces |make pem| certificate/key generation. * Translation updates: |help.fr.conf| * CHATHISTORY now sends a |draft/chathistory-end| if the end of history has been reached (a recent spec improvement <https://github.com/unrealircd/unrealircd/pull/337>). * The IRCv3 reply <https://ircv3.net/specs/client-tags/reply> client tag and no-implicit-names <https://ircv3.net/specs/extensions/no-implicit-names> extensions have been ratified. During the transition period we support both. Fixes: * The following config items previously raised a config error: allow channel::except, deny channel::except and spamfilter::except. * deny channel::mask with a Mask item <https://www.unrealircd.org/docs/Mask_item> caused a config error. * Long multiline messages could be cut off when sent to clients that do not support multiline. * Hardening of the built-in HTTPS client * JSON-RPC: Remote RPC was broken and causing "not authorized" error messages. This was used by |server.rehash| and |server.module_list|. Plus, this release |user.get| under some circumstances. This is now fixed but requires the target server to be on UnrealIRCd 6.2.6. If the target server does not meet this condition then we error telling the server "does not support remote JSON-RPC". Developers and protocol: * URL API: The OutgoingWebRequest |max_size| (introduced last release) now also caps file-backed downloads. Default for file-backed when left at 0 is 50MB (|DOWNLOAD_MAX_SIZE_FILE_BACKED|). For memory-backed, it stays at 1MB like in 6.2.5 (|DOWNLOAD_MAX_SIZE_MEMORY_BACKED|). * The |unreal_match()| function now has a 3rd argument |const char **error| for communicating regex errors back. Just set to |NULL| if you don't care. * Similarly, |unreal_create_match()| last argument is now |const char **error| (const was added). So when callers use that, their variable |char *err| needs to become |const char *err|. * If you do something to a user that would (potentially) move the user from |unknown-users| to |known-users| (or vice versa) then you should call |update_known_user_cache(client);| to update the known users cache. For example, if you have some authentication module that marks a user as IsLoggedIn. * TKL entries can now use message tags to carry extra data, similar to how |s2s-md| worked for early moddata, we have |s2s-tkl|. We have two at the moment: o |s2s-tkl/id|: network-wide unique ID for the TKL entry o |s2s-tkl/spamfilter_id|: for server bans, if they were set by spamfilter, the spamfilter TKL ID. o Example: |@s2s-tkl/id=xxxx;s2s-tkl/spamfilter_id=yyyy :server TKL .....| o Older servers will not pass these along, so for this functionality to work all servers need to be on latest version, especially your hub. * The TKL |STATS| numerics has more fields now, they are added right before last (so before the |:reason| or |:regex|): o |RPL_STATSGLINE| (223) ends with |hits lasthit spamfilter_id id :reason| o |RPL_STATSQLINE| (217) ends with |hits lasthit id :reason| o |RPL_STATSSPAMF| (229) ends with |lasthit lasthit_except id :regex| (which comes right after |hits hits_except|, which was already there) o |RPL_STATSEXCEPTTKL| (230) ends with |id :reason| o An absent id or spamfilter_id is sent as |-| o The hits/lasthit/lasthit_except show how often the TKL was hit and the timestamp of the last hit (the usual, unix time), or 0 for never. These counts are local to each server. * |banned_client()| has an extra parameter |const char *tklid| for the TKL ID (or NULL if none). * The tkldb database version is now 6260 and stores the id, spamfilter_id and the hit statistics (hit count and last-hit time per ban). Older databases still load. Downside: you cannot downgrade UnrealIRCd. * JSON for TKL entries (server logs and JSON-RPC) now includes |id|, and |spamfilter_id| for spamfilter-created server bans. * JSON-RPC |user.get| can now expose flood counters (see next). * JSON-RPC: We can now route |user.get| requests to the server that user is on. This so we can fetch all fields for that user (including flood counters, idle time, snomask) that are normally not available remotely. o We do this automatically in |user.get| when |object_detail_level| is 5+. o You can force this explicitly with |object_remote_fetch| set to |true|. So you can also use it with detail level 2 if you want, e.g. if you don't need the flood counters but do want the idle time. o When RRPC is not available we answer ourselves (so safe fallback, but you won't have the local-only fields). |
|
From: Bram M. <sy...@un...> - 2026-05-15 13:29:52
|
This UnrealIRCd 6.2.5 release is mostly about improving IPv6 clone detection. If your IRC network has IPv6 connectivity then hot-patching without restart (see below), or upgrading, is highly recommended. If you don't have IPv6 then this release is less important. Without this, a user with IPv6 connectivity (e.g. a typical residential connection) can connect thousands of clones using their /64 prefix, bypassing per-host limits like |allow::maxperip| and |connect-flood|. If you run UnrealIRCd 6.2.x then you also have the option of using our *hot-patch*, which allows updating the server _without a restart_. To do so, run: |./unrealircd hot-patch ipv6-clones| For UnrealIRCd 6.2.3 and 6.2.4 this gives you nearly the same IPv6 clones protection as this 6.2.5 release. For UnrealIRCd 6.2.0/6.2.1/6.2.2 it will hot-patch only the maxperip /64 issue and not add the new connthrottle functionality. This release has been tested on a couple of networks with hundreds of users, without an impact on regular users, but it is still good to know these new limits. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade Enhancements: * allow::maxperip <https://www.unrealircd.org/docs/Allow_block#maxperip> and connect-flood <https://www.unrealircd.org/docs/Anti-flood_settings#connect-flood> now treat an IPv6 /64 as a single host (set::default-ipv6-clone-mask <https://www.unrealircd.org/docs/Set_block#set::default-ipv6-clone-mask>). Since end users are typically allocated a whole /64, per-/128 counting offered no real clone protection. We previously claimed to be doing this already in the documentation, but in practice the setting was ignored. A related unused option allow::ipv6-clone-mask has been removed and will now raise an error. * ConnThrottle <https://www.unrealircd.org/docs/Connthrottle> now has a set::connthrottle::ipv6-unknown-users-limit (enabled by default). This reduces the effect of an attacker launching many IPv6 clones at a server. Users in the "known-users" security-group are exempt (by default: identified to services, or reputation <https://www.unrealircd.org/docs/Reputation_score> of 25 or more). Also exempt are users matching set::connthrottle::except or an except ban with type maxperip. o Difference from maxperip: maxperip counts everyone per /64. This counts only unknown users and works on wider IPv6 prefixes (/56, /48 and /32). So known users can connect while cloners are limited. * New set::known-cloud-services <https://www.unrealircd.org/docs/Set_block#set::known-cloud-services> (enabled by default) exempts large IRC platforms with stable published IP ranges from allow::maxperip <https://www.unrealircd.org/docs/Allow_block#maxperip> and connect-flood <https://www.unrealircd.org/docs/Anti-flood_settings#connect-flood>. Currently only IRCCloud qualifies. This is more reliable than the |except ban { mask *.irccloud.com; ... }| block that |example.conf| has shipped since 2023, as DNS can fail during outages or restarts. The new maxperip and connthrottle limits make this even more important. To disable, use: |set { known-cloud-services no; }|. * New snomask <https://www.unrealircd.org/docs/Snomasks> |+x| for rejections from allow::maxperip <https://www.unrealircd.org/docs/Allow_block#maxperip> and ConnThrottle <https://www.unrealircd.org/docs/Connthrottle>. Included in the default oper snomask (unless overridden in set::snomask-on-oper <https://www.unrealircd.org/docs/Set_block#set::snomask-on-oper> or oper::snomask <https://www.unrealircd.org/docs/Oper_block#snomask>). * New set::log-throttle <https://www.unrealircd.org/docs/Set_block#set::log-throttle>: suppresses high-rate events. This is on by default for the new |+x| rejections. * ConnThrottle <https://www.unrealircd.org/docs/Connthrottle> now also exempts users with an except ban of type |connect-flood| from the new-users rate limit. Changes: * The maxperip and connthrottle rejection messages were changed to give more information about the IPv6 range limitation and now include the text |[maxperip]| or |[connthrottle]| so you can see which limit is hit. * Update shipped libs: Sodium (1.0.22) * The event names |CONNTHROTLE_*| were renamed to |CONNTHROTTLE_*| as the former was a typo. * |link::verify-certificate| is now deprecated and a config warning is shown when set. It verified the peer certificate against CA trust. However, newly issued certs from CAs (such as Let's Encrypt) tend to no longer have the Client Authentication EKU, so linking with |verify-certificate| often fails nowadays. Admins should switch to |spkifp| for server linking, like everyone else. Fixes: * set::connthrottle::disabled-when::reputation-gathering <https://www.unrealircd.org/docs/Connthrottle> has been set to 1 week in example.conf since 2019, but if you did not have that item it defaulted to 0 (no delay). Now 1 week. * OOB write if a URL callback returns a response that is more than 2GB. This only affects memory-backed callbacks: centralblocklist, spamreport and log with destination webhook. In practice these are likely all trusted servers. * WEBIRC <https://www.unrealircd.org/docs/WebIRC_block>: if you had an |except ban| block with type |connect-flood| for the gateway then we were accidentally also exempting the end-users behind it, rendering connect-flood useless. Developers and protocol: * |OutgoingWebRequest| has a new |max_size| field (in bytes) that caps the response size for memory-backed downloads. It defaults to |DOWNLOAD_MAX_SIZE| (1MB). Ignored for file-backed downloads. This protects against rogue or misbehaving webservers sending huge responses that could otherwise fill server memory. |
|
From: Bram M. <sy...@un...> - 2026-04-17 04:16:08
|
UnrealIRCd 6.2.4 comes with optional multiline support (not loaded by default yet), a lot of new conditional config and crule functions, and a new GeoIP engine. A bug has been fixed that could confuse services with +e/+I extbans and a Windows crash bug has been resolved. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade Enhancements: * Add IRCv3 draft/multiline <https://ircv3.net/specs/extensions/multiline> support with a default max-lines of |15| for |known-users| and |7| for |unknown-users| (with max-bytes |5250| and |1500| respectively). This allows pasting a short snippet of code, config file, text from a site, etc. Multiline guarantees: o You will see the entire text with no delay between lines o You won't see another persons chat half-way through such a paste o For multiline supporting clients it is clear that all the text belongs to each other, which can make selecting/copying easier. This basically means short snippets/pastes like that can be completely on IRC again. No need for a pastebin. Though, you may still need such a service if you are pasting more lines. Only a couple clients support sending multiline at the moment: IRCCloud, WeeChat, ObsidianIRC, Halloy, and the bots BitBot & Limnoria. Incoming lines with multilines are displayed normally in unsupporting clients, using a fallback algorithm. IMPORTANT: This module is *not loaded by default* at the moment. You need a |loadmodule "multiline";| to use it. In a future version of UnrealIRCd we will likely load this module by default, after receiving more feedback. Regarding limits and anti-flood: o This obeys the limit of |+f| subtype |t|: so |+f [5t]:15| (max 5 lines per 15 secs) means multiline max lines is also 5 for that channel. o A new |+f| subtype |p| ("pastes") is introduced. Any multiline of 3 or more lines is considered a paste and something like |+f [2p]:15| then only allows 2 pastes per 15 seconds in the channel. If any user tries to do a 3rd paste within that period it is rejected. o The anti-flood profile <https://www.unrealircd.org/docs/Channel_anti-flood_settings> |normal| has a limit of |[2p]:15|. Only profile |very-relaxed| allows more: |[3p]:15|. Profiles |strict| and |very-strict| use |[1p]:15|. Finally, it is good to know that multiline events are atomic, in chat history too. This means you will either get them in full or not at all. If your channel has |+H 5:60m| and the last message was a multiline event of 15 lines, then we allow to temporarily overshoot and you will see 15 lines (the alternative would be 0 lines, which would be worse). * Conditional config <https://www.unrealircd.org/docs/Defines_and_conditional_config>: o New built-in variables |$CONFDIR|, |$DATADIR|, |$LOGDIR|, |$TMPDIR|, |$DOCDIR|, |$MODULESDIR| and |$MAXCONNECTIONS| are now available for use in the configuration file. o Variable comparisons now support |>|, |>=|, |<|, |<=| in addition to |==| and |!=|. Uses natural ordering, so version strings and numbers compare correctly. Example: |@if $MAXCONNECTIONS >= 1024|. o New |@if minimum-version("6.2.4")| to check if the UnrealIRCd version is at least the specified version. o New |@if module-exists("modulename")| to check if a module exists on disk. You can use this with a subsequent |loadmodule| and config items, this can be handy with 3rd party modules. o New |@if module-version("modulename")| to check or compare the version of a loaded module. Example: |@if module-version("third/something") >= "2.0"|. This obviously only works if the module is loaded. o New |@if file-exists("filename")| to check if a file exists. Paths are relative to the conf directory, or absolute if starting with |/|. o New |@else| support: |@if ... @else ... @endif|. o New |@if environment("VARNAME")| to check if an environment variable is set. Can also be used with comparison operators, e.g., |@if environment("SOMETHING") == "myserver"|. o |@define| can now use value-returning functions, e.g., |@define $ADMIN_EMAIL environment("ADMIN_EMAIL")| to set a variable from an OS environment variable. o New |@error "message"| and |@warning "message"| directives. Eg for |if !environment("ADMIN")| |@error "ADMIN env var not defined"|. * New crule functions <https://www.unrealircd.org/docs/Crule> for use in security groups, match items, spamfilter::rule: o Boolean checks: |is_oper|, |is_local|, |has_swhois| o Match functions: |match_class|, |match_server|, |match_vhost|, |match_realhost|, |match_away|, |match_asname|, |match_operlogin|, |match_operclass|, |match_sni|, |match_tls_cipher| o Numeric counters: |connections_from_ip|, |channel_count|, |channel_member_count|, |idle_time| o Traffic stats: |messages_sent|, |messages_received|, |bytes_sent|, |bytes_received| o Text analysis: |text_byte_count|, |text_character_count|, |word_count|, |uppercase_percentage|, |digit_percentage|, |non_ascii_percentage|, |max_repeat_count|, |mixed_utf8_score|, |unicode_block_count| o The documentation <https://www.unrealircd.org/docs/Crule> also has been rewritten to group the functions for a better overall view. Changes: * GeoIP <https://www.unrealircd.org/docs/GeoIP>: o We now ship with our own mmdb engine and |geoip_mmdb| (replacement for |geoip_maxmind|). o The |./Config| question on GeoIP now defaults to |mmdb|. Existing users who upgrade will keep their current setting (usually |classic|) for now. o Both |geoip_classic| and |geoip_mmdb| now receive automatic updates o You can |@define $NO_DEFAULT_GEOIP "1"| to disable auto configuration and updates. * Errors in TLS certificate/keys are now fatal errors. Fixes: * The Windows version could crash after a few minutes due to missing MODVAR. * Downgrade shipped sodium library to 1.0.20 to fix arm64 compile issue with 1.0.21. * Compile fixes when using OpenSSL 4.0.0 * Named extbans in |+e| and |+I| were supposed to be sent with letters instead of names to servers not supporting them (UnrealIRCd older than 6 and Services), but this was not the case. Is now fixed. This bug caused for example Anope 2.0.x to get confused if |KEEPMODES| was on a channel and you had like |+I ~account:xyz|. Then next time anope relinked it would add |+I *!*@~account:xyz|. This bug is present since 6.0.0 already. It does not affect |+b|. * In some uncommon cases, |X25519MLKEM768| was not negotiated when it could have. So we now try harder. In technical terms we now use tuple syntax for the TLS group to signal that we can afford a Hello Retry Request. Developers and protocol: * If the "multiline" module is loaded then we support |draft/multiline| <https://ircv3.net/specs/extensions/multiline>: o If the client does not support draft/multiline then messages are shown using the fallback implementation, as outlined in that draft (basically just regular PRIVMSGs, nothing weird). o Clients that do support the spec send a BATCH start + PRIVMSGs + BATCH end and are allowed to send that in one go with no delay (no ratelimiting). As long as they obey the advertised limits. They will get fake lag applied /after/ the multiline batch, with an algorithm similar to current fakelag but with a hard cap of maximum 15s fakelag, which means 5s max effective fakelag. o We use different limits for the |unknown-users| and |known-users| security group. Clients will receive their |multiline=max-bytes=xx,maxlines=yy| message that are a hard limit. If a client transitions between security groups, for example because you authenticated to services, you will receive a |CAP NEW| event. o Channels that have +f with subtype 't' set, such as +f |[5t]:15| which means a maximum of 5 lines per 15 seconds, will also enforce that limit for multiline, so max 5 lines in a multiline. If a client hits that limit, and this is possibly since clients usually don't understand +f and only look at the CAP max-lines, then we simply reject the multiline event at BATCH end. o Similarly, we have a new +f subtype 'p' which limits the number of pastes in a channel (which is 3+ line multiline events). For example, |+f [2p]:15| allows two pastes in a channel per 15 seconds. A third one in the same timeframe will result in a rejection after the BATCH end. o In UnrealIRCd we buffer and will only do (nearly) all access checks and such at the BATCH end, and not at the PRIVMSG/NOTICE stage, so only at the BATCH end the client will receive an error message such as cannot send due to |+m|. Since clients will send all events at full speed in one go, this makes sense to do at BATCH end as well. o In UnrealIRCd we do not allow CTCPs in multiline events. These make no sense and also would result in different behavior in multiline vs non-multiline clients. o Multiline events are checked per-line as usual, through spamfilter too, and they are as-a-whole put again through spamfilter to avoid bypassing spamfilters. o Multiline has a slightly odd interaction with |draft/history|: + One multiline event is counted as 1 line. So if you use |CHATHISTORY| to request 5 lines, you could get like 19 lines if one of those "5 lines" is actually a multiline of 15 lines, or even 5*15 lines. + As mentioned, for |+H| we allow to overshoot the max history lines if the latest message was a multiline message. So for |+H 5:1h| and a 15 line multiline batch, we will store 15 lines. Multiline batches are atomic so the alternative would be to store 0 lines, which is worse in terms of functionality than temporarily overshooting the line limit. + The spec requires only the 1st line to have a |msgid| and lines 2-N of a multiline event are forbidden to have a |msgid|. They can have other tags, though. + As expected, we show multiline nested batches in history if |draft/multiline| is supported. * ClientContext now has a new field |fake_lag_added_msec| and there is a new function |subtract_fake_lag()|. This is used by multiline, for example. * We now guard that |CommandOverrideAdd()| is only used in |MOD_LOAD| and not in |MOD_INIT| (otherwise it is too early, commands may not exist yet). Similarly, we ensure |EfunctionAdd()| is used from |MOD_TEST|. Clear errors are logged in both cases if you try to do otherwise. |
|
From: Bram M. <sy...@un...> - 2026-04-04 06:22:23
|
The Release Candidate for future version 6.2.4 is now available for testing. The stable version is scheduled later this month. UnrealIRCd 6.2.4-rc1 comes with optional multiline support and a lot of new conditional config and crule functions, plus a new GeoIP engine. A bug has been fixed that would confuse services with +e/+I extbans. A compile issue on arm64 and a Windows crash bug have been resolved as well. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * Add IRCv3 draft/multiline <https://ircv3.net/specs/extensions/multiline> support with a default max-lines of |15| for |known-users| and |7| for |unknown-users| (with max-bytes |5250| and |1500| respectively). This allows pasting a short snippet of code, config file, text from a site, etc. Multiline guarantees: o You will see the entire text with no delay between lines o You won't see another persons chat half-way through such a paste o For multiline supporting clients it is clear that all the text belongs to each other, which can make selecting/copying easier. This basically means short snippets/pastes like that can be completely on IRC again. No need for a pastebin. Though, you may still need such a service if you are pasting more lines. Only a couple clients support sending multiline at the moment: IRCCloud, WeeChat, ObsidianIRC, Halloy, and the bots BitBot & Limnoria. Incoming lines with multilines are displayed normally in unsupporting clients, using a fallback algorithm. IMPORTANT: This module is *not loaded by default* at the moment. You need a |loadmodule "multiline";| to use it. Regarding limits and anti-flood: o This obeys the limit of |+f| subtype |t|: so |+f [5t]:15| (max 5 lines per 15 secs) means multiline max lines is also 5 for that channel. o A new |+f| subtype |p| ("pastes") is introduced. Any multiline of 3 or more lines is considered a paste and something like |+f [2p]:15| then only allows 2 pastes per 15 seconds in the channel. If any user tries to do a 3rd paste within that period it is rejected. o The anti-flood profile <https://www.unrealircd.org/docs/Channel_anti-flood_settings> |normal| has a limit of |[2p]:15|. Only profile |very-relaxed| allows more: |[3p]:15|. Profiles |strict| and |very-strict| use |[1p]:15|. Finally, it is good to know that multiline events are atomic, in chat history too. This means you will either get them in full or not at all. If your channel has |+H 5:60m| and the last message was a multiline event of 15 lines, then we allow to temporarily overshoot and you will see 15 lines (the alternative would be 0 lines, which would be worse). * Conditional config <https://www.unrealircd.org/docs/Defines_and_conditional_config>: o New built-in variables |$CONFDIR|, |$DATADIR|, |$LOGDIR|, |$TMPDIR|, |$DOCDIR|, |$MODULESDIR| and |$MAXCONNECTIONS| are now available for use in the configuration file. o Variable comparisons now support |>|, |>=|, |<|, |<=| in addition to |==| and |!=|. Uses natural ordering, so version strings and numbers compare correctly. Example: |@if $MAXCONNECTIONS >= 1024|. o New |@if minimum-version("6.2.4")| to check if the UnrealIRCd version is at least the specified version. o New |@if module-exists("modulename")| to check if a module exists on disk. You can use this with a subsequent |loadmodule| and config items, this can be handy with 3rd party modules. o New |@if module-version("modulename")| to check or compare the version of a loaded module. Example: |@if module-version("third/something") >= "2.0"|. This obviously only works if the module is loaded. o New |@if file-exists("filename")| to check if a file exists. Paths are relative to the conf directory, or absolute if starting with |/|. o New |@else| support: |@if ... @else ... @endif|. o New |@if environment("VARNAME")| to check if an environment variable is set. Can also be used with comparison operators, e.g., |@if environment("SOMETHING") == "myserver"|. o |@define| can now use value-returning functions, e.g., |@define $ADMIN_EMAIL environment("ADMIN_EMAIL")| to set a variable from an OS environment variable. o New |@error "message"| and |@warning "message"| directives. Eg for |if !environment("ADMIN")| |@error "ADMIN env var not defined"|. * New crule functions <https://www.unrealircd.org/docs/Security_groups#Rules> for use in security groups, match items, spamfilter::rule: o Boolean checks: |is_oper|, |is_local|, |has_swhois| o Match functions: |match_class|, |match_server|, |match_vhost|, |match_realhost|, |match_away|, |match_asname|, |match_operlogin|, |match_operclass|, |match_sni|, |match_tls_cipher| o Numeric counters: |connections_from_ip|, |channel_count|, |channel_member_count|, |idle_time| o Traffic stats: |messages_sent|, |messages_received|, |bytes_sent|, |bytes_received| o Text analysis: |text_byte_count|, |text_character_count|, |word_count|, |uppercase_percentage|, |digit_percentage|, |non_ascii_percentage|, |max_repeat_count|, |mixed_utf8_score|, |unicode_block_count| o The documentation <https://www.unrealircd.org/docs/Security_groups#Rules> also has been rewritten to group the functions for a better overall view. Changes: * GeoIP <https://www.unrealircd.org/docs/GeoIP>: o We now ship with our own mmdb engine and |geoip_mmdb| (replacement for |geoip_maxmind|). o The |./Config| question on GeoIP now defaults to |mmdb|. Existing users who upgrade will keep their current setting (usually |classic|) for now. o Both |geoip_classic| and |geoip_mmdb| now receive automatic updates o You can |@define $NO_DEFAULT_GEOIP "1"| to disable auto configuration and updates. * Errors in TLS certificate/keys are now fatal errors. Fixes: * Downgrade shipped sodium library to 1.0.20 to fix arm64 compile issue with 1.0.21. * The Windows version could crash after a few minutes due to missing MODVAR. * Named extbans in |+e| and |+I| were supposed to be sent with letters instead of names to servers not supporting them (UnrealIRCd older than 6 and Services), but this was not the case. Is now fixed. This bug caused for example Anope 2.0.x to get confused if |KEEPMODES| was on a channel and you had like |+I ~account:xyz|. Then next time anope relinked it would add |+I *!*@~account:xyz|. This bug is present since 6.0.0 already. It does not affect |+b|. * In some uncommon cases, |X25519MLKEM768| was not negotiated when it could have. So we now try harder. In technical terms we now use tuple syntax for the TLS group to signal that we can afford a Hello Retry Request. Developers and protocol: * If the "multiline" module is loaded then we support |draft/multiline| <https://ircv3.net/specs/extensions/multiline>: o If the client does not support draft/multiline then messages are shown using the fallback implementation, as outlined in that draft (basically just regular PRIVMSGs, nothing weird). o Clients that do support the spec send a BATCH start + PRIVMSGs + BATCH end and are allowed to send that in one go with no delay (no ratelimiting). As long as they obey the advertised limits. They will get fake lag applied /after/ the multiline batch, with an algorithm similar to current fakelag but with a hard cap of maximum 15s fakelag, which means 5s max effective fakelag. o We use different limits for the |unknown-users| and |known-users| security group. Clients will receive their |multiline=max-bytes=xx,maxlines=yy| message that are a hard limit. If a client transitions between security groups, for example because you authenticated to services, you will receive a |CAP NEW| event. o Channels that have +f with subtype 't' set, such as +f |[5t]:15| which means a maximum of 5 lines per 15 seconds, will also enforce that limit for multiline, so max 5 lines in a multiline. If a client hits that limit, and this is possibly since clients usually don't understand +f and only look at the CAP max-lines, then we simply reject the multiline event at BATCH end. o Similarly, we have a new +f subtype 'p' which limits the number of pastes in a channel (which is 3+ line multiline events). For example, |+f [2p]:15| allows two pastes in a channel per 15 seconds. A third one in the same timeframe will result in a rejection after the BATCH end. o In UnrealIRCd we buffer and will only do (nearly) all access checks and such at the BATCH end, and not at the PRIVMSG/NOTICE stage, so only at the BATCH end the client will receive an error message such as cannot send due to |+m|. Since clients will send all events at full speed in one go, this makes sense to do at BATCH end as well. o In UnrealIRCd we do not allow CTCPs in multiline events. These make no sense and also would result in different behavior in multiline vs non-multiline clients. o Multiline events are checked per-line as usual, through spamfilter too, and they are as-a-whole put again through spamfilter to avoid bypassing spamfilters. o Multiline has a slightly odd interaction with |draft/history|: + One multiline event is counted as 1 line. So if you use |CHATHISTORY| to request 5 lines, you could get like 19 lines if one of those "5 lines" is actually a multiline of 15 lines, or even 5*15 lines. + As mentioned, for |+H| we allow to overshoot the max history lines if the latest message was a multiline message. So for |+H 5:1h| and a 15 line multiline batch, we will store 15 lines. Multiline batches are atomic so the alternative would be to store 0 lines, which is worse in terms of functionality than temporarily overshooting the line limit. + The spec requires only the 1st line to have a |msgid| and lines 2-N of a multiline event are forbidden to have a |msgid|. They can have other tags, though. + As expected, we show multiline nested batches in history if |draft/multiline| is supported. * ClientContext now has a new field |fake_lag_added_msec| and there is a new function |subtract_fake_lag()|. This is used by multiline, for example. |
|
From: Bram M. <sy...@un...> - 2026-03-06 08:03:31
|
This release comes with new features such as soft bans in ban user { },
a new setting to allow admins to control SETIDENT and SETNAME usage
(with a saner default), third party modules can build with external
libraries, improved security hardening, EXTJWT is documented now. It
also fixes SASL not working reliably with some clients and has a bunch
of other fixes.
You can download UnrealIRCd from unrealircd.org
<https://www.unrealircd.org/>. On *NIX you can upgrade with the command:
./unrealircd upgrade
Enhancements:
* In ban user { } <https://www.unrealircd.org/docs/Ban_user_block> you
can now use |soft yes;| to make it a Soft ban
<https://www.unrealircd.org/docs/Soft_ban>.
* Two new settings that control the use of |SETIDENT| and |SETNAME|:
o set::allow-setident
<https://www.unrealircd.org/docs/Set_block#set::allow-setident>
now defaults to 'no'. Previously, users were allowed to change
their ident (with allow-userhost-change
<https://www.unrealircd.org/docs/Set_block#set::allow-userhost-change>
restrictions).
o set::allow-setname
<https://www.unrealircd.org/docs/Set_block#set::allow-setname>
has a default of 'yes' which matches older UnrealIRCd versions
(no change). Perhaps some admins who use controlled (web)chats
may want to set this to 'no' if users are not supposed to change
their realname/gecos. This is likely rare.
* The module manager <https://www.unrealircd.org/docs/Module_manager>
now allows 3rd party modules to specify external libraries and build
flags.
* If a recipient has user mode |+D| or |+R| and the sender is not
allowed to send a |PRIVMSG| or |NOTICE| then we will silently drop
|TAGMSG|. This prevents silent discovery of who blocks you. Plus,
you no longer get confusing "cannot send" errors due to typing
indicator, when you have not even sent a message yet.
* DNS caching when using built-in HTTPS, like for Central Blocklist
<https://www.unrealircd.org/docs/Central_Blocklist>. This is
especially important if the server is under a heavy attack.
* Security hardening: we now build with stronger mitigations (full
RELRO, CFI, zero-initialized stack variables, stricter bounds
checking). These are now also verified in BuildBot (CI). Several of
these protections also require support in the OS/distro, CFI even in
the processor, but when supported we will use it.
* The extjwt { } block <https://www.unrealircd.org/docs/Extjwt_block>
is now documented, the code has been updated to use the latest
OpenSSL APIs and is now tested in the test framework.
Changes:
* If SASL authentication is ongoing and a client sends |CAP END|, we
now wait for SASL to succeed/fail/timeout before actually ending the
handshake. This solves a race condition for IRC clients that don't
follow the recommendation in the SASL specification
<https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>.
* Slightly raise default set::handshake-timeout
<https://www.unrealircd.org/docs/Set_block#set::handshake-timeout>
from 30 to 40 seconds.
* |./unrealircd module install| now gives a non-zero exit code on failure
* Update shipped libs: PCRE2 (10.47), Jansson (2.15.0), Sodium (1.0.21)
* Small updates to |HELPOP|.
Fixes:
* Crash when using Extended Server Bans
<https://www.unrealircd.org/docs/Extended_server_bans> with invalid
syntax in the configuration file.
* Crash on malicious server-to-server traffic (OOB write), bug
introduced in 6.2.2.
* Linking could cause splitting the wrong server when a duplicate link
was detected.
* Don't show confusing |CENTRAL_BLOCKLIST_TIMEOUT| message when user
is shunned by CBL.
* Various memory leaks were fixed. Mostly a couple of bytes on
|REHASH| in some specific configurations such as tld::channel
(harmless), but a bigger one was with blacklists using soft bans,
where it could leak memory if an IP had hits from multiple blacklist
blocks.
* In JSON-RPC |user.part| the oper-only-viewable message tag
unrealircd.org/issued-by <https://www.unrealircd.org/issued-by> was
missing.
* Building UnrealIRCd failed if DNS was not working. Obviously
building should never fail if internet or our infra is unreachable.
Additionally, we now skip over the module upgrade step (and fetching
the module repository) if there are no 3rd party modules installed.
Removed:
* set::restrict-extendedbans has been removed because it didn't work
since UnrealIRCd 6.0.0. If you don't want a particular extended ban
to be used then simply don't load the module or use blacklist-module
<https://www.unrealircd.org/docs/Blacklist-module_directive>. For
example, assuming you include |modules.default.conf| and you don't
want the |~quiet| extban then add |blacklist-module
"extbans/quiet";| to your |unrealircd.conf|.
Developers and protocol:
* We now compile with |-fstrict-flex-arrays=3| which means strict
bounds checking on structs is possible. This also means you should
no longer use tricks like |struct { char name[1]; }| and then alloc
with size |sizeof(struct)+strlen(name)|, instead you should use
|char name[]| and alloc |sizeof(struct)+strlen(name)+1|. Or just use
a fixed value like |char name[32]|, of course.
* We now compile with |-ftrivial-auto-var-init=zero| which helps
against use of uninitialized variables on the stack. This is a
safety net only, you should still initialize variables.
* Third party modules can now set module::compile-flags in the module
manager block
<https://www.unrealircd.org/docs/Special_module_manager_block_in_source_file>.
This allows linking with libraries for that specific module, or any
other custom compile flags.
* All 3rd party modules are now compiled via the modulemanager,
including unmanaged ones. This also means that modules that do not
exist in any repository, can still use a module manager block to
specify compile flags.
* Setting ChanMode |+l| with a value of zero or less will cause an
|ERR_INVALIDMODEPARAM| message, instead of transforming it to |1|.
* In |HOOKTYPE_CAN_SEND_TO_USER| you can now choose not to set
|*errmsg| to silently drop a message. Generally you should set the
message, though. This is used now by +D/+R if user is blocked and it
is a TAGMSG.
* Calling |register_user()| more than once for the same user should
never be done (causes a desync). We now guard against this in the
function. Similarly, we guard against allowing shunned users in.
* As mentioned under "Changes": if SASL authentication is ongoing and
a client sends |CAP END|, we now wait for SASL to
succeed/fail/timeout before actually ending the handshake. This
solves a race condition for IRC clients that don't follow the
recommendation in the SASL specification
<https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>.
Our approach would be problematic for clients who deliberately
wanted to abort SASL due to a timeout but UnrealIRCd already handles
SASL timeout via set::sasl-timeout
<https://www.unrealircd.org/docs/Set_block#set::sasl-timeout> which
is 15 seconds by default, so that's fine.
* Changes in JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>:
o Mask/match items and security groups now get expanded in the
same way. All properties are expanded properly. Extended fields
like |account| and |country| are expanded directly under, just
like any other items.
o |security_group|
<https://www.unrealircd.org/docs/JSON-RPC:Security_group>: Uses
the new style output (see previous).
o |server_ban|
<https://www.unrealircd.org/docs/JSON-RPC:Server_ban> and
|server_ban_exception|
<https://www.unrealircd.org/docs/JSON-RPC:Server_ban_exception>
now show the expanded mask items in |match| rather than
|"name":"<match item>"|. This does mean that |name| will be
missing if it is a |match| item.
o |spamfilter|
<https://www.unrealircd.org/docs/JSON-RPC:Spamfilter>: here too,
mask item is expanded if it is used in spamfilter.except. so it
actually works now.
* We now consistently enforce |MAXBANLEN|, which is the same as
|MODEBUFLEN| (200) throughout the code. Only when unsetting we allow
to exceed this. Third party extended bans should obey this limit and
use something quite a bit lower (due to potential stacking). In our
own code, the highest final-element-without-stacking extban is
|~text| with 150 bytes.
* Regular bans on |nick!user@host| can now be 106 bytes
(|NICKLEN+USERLEN+HOSTLEN+3|) rather than 79 (|USERLEN+HOSTLEN+6|).
It should be noted that in extbans, such as |~quiet| you could
already use 106+.
|
|
From: Bram M. <sy...@un...> - 2026-02-25 07:48:29
|
The second Release Candidate for future version 6.2.3 is now available for testing. The stable version is still scheduled for somewhere in March 2026. UnrealIRCd 6.2.3-rc2 comes with a couple of new features, improved security hardening and has quite a number of bug fixes. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ What changed between -rc1 and -rc2 are mostly improved security hardening, a new SETIDENT restriction, memory leak fixes and the removal of set::restrict-extendedbans. The reason for this second RC is to make sure those changes don't mess anything up. Especially on systems or configurations that we don't test on, or with 3rd party modules. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * In ban user { } <https://www.unrealircd.org/docs/Ban_user_block> you can now use |soft yes;| to make it a Soft ban <https://www.unrealircd.org/docs/Soft_ban>. * Two new settings that control the use of |SETIDENT| and |SETNAME|: o set::allow-setident <https://www.unrealircd.org/docs/Set_block#set::allow-setident> now defaults to 'no'. Previously, users were allowed to change their ident (with allow-userhost-change <https://www.unrealircd.org/docs/Set_block#set::allow-userhost-change> restrictions). o set::allow-setname <https://www.unrealircd.org/docs/Set_block#set::allow-setname> has a default of 'yes' which matches older UnrealIRCd versions (no change). Perhaps some admins who use controlled (web)chats may want to set this to 'no' if users are not supposed to change their realname/gecos. This is likely rare. * The module manager <https://www.unrealircd.org/docs/Module_manager> now allows 3rd party modules to specify external libraries and build flags. * If a recipient has user mode |+D| or |+R| and the sender is not allowed to send a |PRIVMSG| or |NOTICE| then we will silently drop |TAGMSG|. This prevents silent discovery of who blocks you. Plus, you no longer get confusing "cannot send" errors, due to typing indicator, when you have not even sent a message yet. * DNS caching when using build-in HTTPS. * Security hardening: we now build with stronger mitigations (full RELRO, CFI, zero-initialized stack variables, stricter bounds checking). These are now also verified in BuildBot (CI). Several of these protections also require support in the OS/distro, CFI even in the processor, but when supported we will use it. Changes: * If SASL authentication is ongoing and a client sends |CAP END|, we now wait for SASL to succeed/fail/timeout before actually ending the handshake. This solves a race condition for IRC clients that don't follow the recommendation in the SASL specification <https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>. * Slightly raise default set::handshake-timeout <https://www.unrealircd.org/docs/Set_block#set::handshake-timeout> from 30 to 40 seconds. * |./unrealircd module install| now gives a non-zero exit code on failure * Update shipped libs: PCRE2 (10.47), Jansson (2.15.0), Sodium (1.0.21) * Small updates to |HELPOP|. Fixes: * Crash when using Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> with invalid syntax in the configuration file. * Linking could cause splitting the wrong server when a duplicate link was detected. * Don't show confusing |CENTRAL_BLOCKLIST_TIMEOUT| message when user is shunned by CBL. * Various memory leaks were fixed. Mostly a couple of bytes on |REHASH| in some specific configurations such as tld::channel (harmless), but a bigger one was with blacklists using soft bans, where it could leak if an IP had hits from multiple blacklist blocks. * In JSON-RPC |user.part| the oper-only-viewable message tag unrealircd.org/issued-by <https://www.unrealircd.org/issued-by> was missing. Removed: * set::restrict-extendedbans has been removed because it didn't work since UnrealIRCd 6.0.0. If you don't want a particular extended ban to be used then simply don't load the module or use blacklist-module <https://www.unrealircd.org/docs/Blacklist-module_directive>. For example, assuming you include |modules.default.conf| and you don't want the |~quiet| extban then add |blacklist-module "extbans/quiet";| to your |unrealircd.conf|. Developers and protocol: * We now compile with |-fstrict-flex-arrays=3| which means strict bounds checking on structs is possible. This also means you should no longer use tricks like |struct { char name[1]; }| and then alloc with size |sizeof(struct)+strlen(name)|, instead you should use |char name[]| and alloc |sizeof(struct)+strlen(name)+1|. Or just use a fixed value like |char name[32]|, of course. * We now compile with |-ftrivial-auto-var-init=zero| which helps against use of uninitialized variables on the stack. This is a safety net only, you should still initialize variables. * Third party modules can now set module::compile-flags in the module manager block <https://www.unrealircd.org/docs/Special_module_manager_block_in_source_file>. This allows linking with libraries for that specific module, or any other custom compile flags. * All 3rd party modules are now compiled via the modulemanager, including unmanaged ones. This also means that modules that do not exist in any repository, can still use a module manager block to specify compile flags. * Setting ChanMode |+l| with a value of zero or less will cause an |ERR_INVALIDMODEPARAM| message, instead of transforming it to |1|. * In |HOOKTYPE_CAN_SEND_TO_USER| you can now choose not to set |*errmsg| to silently drop a message. Generally you should set the message, though. This is used now by +D/+R if user is blocked and it is a TAGMSG. * Calling |register_user()| more than once for the same user should never be done (causes a desync). We now guard against this in the function. Similarly, we guard against allowing shunned users in. * As mentioned under "Changes": if SASL authentication is ongoing and a client sends |CAP END|, we now wait for SASL to succeed/fail/timeout before actually ending the handshake. This solves a race condition for IRC clients that don't follow the recommendation in the SASL specification <https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>. Our approach would be problematic for clients who deliberately wanted to abort SASL due to a timeout but UnrealIRCd already handles SASL timeout via set::sasl-timeout <https://www.unrealircd.org/docs/Set_block#set::sasl-timeout> which is 15 seconds by default, so that's fine. * Changes in JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: o Mask/match items and security groups now get expanded in the same way. All properties are expanded properly. Extended fields like |account| and |country| are expanded directly under, just like any other items. o |security_group| <https://www.unrealircd.org/docs/JSON-RPC:Security_group>: Uses the new style output (see previous). o |server_ban| <https://www.unrealircd.org/docs/JSON-RPC:Server_ban> and |server_ban_exception| <https://www.unrealircd.org/docs/JSON-RPC:Server_ban_exception> now show the expanded mask items in |match| rather than |"name":"<match item>"|. This does mean that |name| will be missing if it is a |match| item. o |spamfilter| <https://www.unrealircd.org/docs/JSON-RPC:Spamfilter>: here too, mask item is expanded if it is used in spamfilter.except. so it actually works now. * We now consistently enforce |MAXBANLEN|, which is the same as |MODEBUFLEN| (200) throughout the code. Only when unsetting we allow to exceed this. Third party extended bans should obey this limit and use something quite a bit lower (due to potential stacking). In our own code, the highest final-element-without-stacking extban is |~text| with 150 bytes. * Regular bans on |nick!user@host| can now be 106 bytes (|NICKLEN+USERLEN+HOSTLEN+3|) rather than 79 (|USERLEN+HOSTLEN+6|). It should be noted that in extbans, such as |~quiet| you could already use 106+. |
|
From: Bram M. <sy...@un...> - 2026-01-31 09:04:14
|
The Release Candidate for future version 6.2.3 is now available for testing. The stable version is scheduled for March 2026. UnrealIRCd 6.2.3-rc1 comes with a few enhancements and has quite a number of bugfixes. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/>. On *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * In ban user { } <https://www.unrealircd.org/docs/Ban_user_block> you can now use |soft yes;| to make it a Soft ban <https://www.unrealircd.org/docs/Soft_ban>. * DNS caching when using build-in HTTPS. * If a recipient has user mode |+D| or |+R| and the sender is not allowed to send a |PRIVMSG| or |NOTICE| then we will silently drop |TAGMSG|. This prevents silent discovery of who blocks you. Plus, you no longer get confusing "cannot send" errors, due to typing indicator, when you have not even send a message yet. * The module manager <https://www.unrealircd.org/docs/Module_manager> now allows 3rd party modules to specify external libraries and build flags. Changes: * Small updates to |HELPOP|. * |./unrealircd module install| now gives a non-zero exit code on failure * If SASL authentication is ongoing and a client sends |CAP END|, we now wait for SASL to succeed/fail/timeout before actually ending the handshake. This solves a race condition for IRC clients that don't follow the recommendation in the sasl specification <https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>. * Slightly raise default set::handshake-timeout <https://www.unrealircd.org/docs/Set_block#set::handshake-timeout> from 30 to 40 seconds. * Update shipped libs: PCRE2 (10.47), Jansson (2.15.0), Sodium (1.0.21) Fixes: * Crash when using Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> with an invalid syntax in the configuration file. * Don't show confusing CENTRAL_BLOCKLIST_TIMEOUT message when user is shunned. Developers and protocol: * Third party modules can now set module::compile-flags in the module manager block <https://www.unrealircd.org/docs/Special_module_manager_block_in_source_file>. This allows linking with libraries for that specific module, or any other custom compile flags. * All 3rd party modules are now compiled via the modulemanager, including unmanaged ones. This also means that modules that do not exist in any repository, can still use a module manager block to specify compile flags. * Setting ChanMode |+l| with a value of zero or less will cause an |ERR_INVALIDMODEPARAM| message, instead of transforming it to |1|. * In |HOOKTYPE_CAN_SEND_TO_USER| you can now choose not to set |*errmsg| to silently drop a message. Generally you should set the message, though. This is used now by +D/+R if user is blocked and it is a TAGMSG. * Calling |register_user()| more than once for the same user should never be done (causes a desync). We now guard against this in the function. Similarly, we guard against allowing shunned users in. * As mentioned under "Changes": if SASL authentication is ongoing and a client sends |CAP END|, we now wait for SASL to succeed/fail/timeout before actually ending the handshake. This solves a race condition for IRC clients that don't follow the recommendation in the sasl specification <https://ircv3.net/specs/extensions/sasl-3.1#the-authenticate-command>. Our approach would be problematic for clients who deliberately wanted to abort SASL due to a timeout but UnrealIRCd already handles SASL timeout via set::sasl-timeout <https://www.unrealircd.org/docs/Set_block#set::sasl-timeout> which is 15 seconds by default, so that's fine. * Changes in JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: o Mask/match items and security groups now get expanded in the same way. All properties are expanded properly. Extended fields like |account| and |country| are expanded directly under, just like any other items. o |security_group| <https://www.unrealircd.org/docs/JSON-RPC:Security_group>: Uses the new style output (see previous). o |server_ban| <https://www.unrealircd.org/docs/JSON-RPC:Server_ban> and |server_ban_exception| <https://www.unrealircd.org/docs/JSON-RPC:Server_ban_exception> now show the expanded mask items in |match| rather than |"name":"<match item>"|. This does mean that |name| will be missing if it is a |match| item. o |spamfilter| <https://www.unrealircd.org/docs/JSON-RPC:Spamfilter>: here too, mask item is expanded if it is used in spamfilter.except. o |connthrottle| <https://www.unrealircd.org/docs/JSON-RPC:Connthrottle>: In |connthrottle.status| the |state| value |active| was changed to |monitoring| (module is enabled but not actively intervening). Also, the items under config.except are now an expanded mask item (consistent with the rest). Plus, |connthrottle.set| was fixed so it actually works now. |
|
From: Bram M. <sy...@un...> - 2025-12-26 10:41:17
|
Good morning, I made a forum post here https://forums.unrealircd.org/viewtopic.php?t=9458. I'll share it here: *Initial spam wave on Dec 24/25* Central Block List (CBL) has been working out well to protect dozens of UnrealIRCd networks. It auto-submits to DroneBL (almost 2000 IPs the first 24 hours), so the rest of the IRC community benefited. Lots of IRC networks did not see much spam Dec 24/25 thanks to these IPs being in DroneBL already due to CBL DroneBL submissions. Spammers also targeted some networks directly, separate from the IRC-wide spam waves. Networks like Libera Chat, which are doing everything they can and (presumably) also submitting to DroneBL. Everyone in the IRC community doing their part. *Second wave on night of Dec 26* On the night (UTC) of December 25 to December 26 things changed. Spammers stopped re-using IP addresses and Central Block List didn't pick up the spam that night. The CBL detection was fixed on the morning of Dec 26, stopping 100% of the spam again. However, protecting the rest of the IRC community by sharing the IPs to DroneBL is no longer effective. *How to counter this spam?* If you are an UnrealIRCd network then consider subscribing to Central Block List <https://www.unrealircd.org/docs/Central_Blocklist>. Submissions require manual vetting by us to see if you are a legit network but once you are allowed in on CBL it is very effective. The forum post at https://forums.unrealircd.org/viewtopic.php?t=9458 may be updated/edited later. |
|
From: Bram M. <sy...@un...> - 2025-12-12 11:58:13
|
UnrealIRCd 6.2.2 is just a small maintenance release to fix a few minor issues. If you are running 6.2.1 then there is little reason to upgrade. *Still using UnrealIRCd 6.0.x/6.1.x?* If you are still running 6.0.x or 6.1.x then we highly recommend to upgrade to 6.2.x in December 2025. The 6.2.x series have proven to be stable and are a nice leap forward in terms of security with channel flood protection enabled by default <https://www.unrealircd.org/docs/Channel_anti-flood_settings>, our effort and guide to move users to TLS <https://www.unrealircd.org/docs/Use_TLS> and Post-quantum cryptography (PQC) enhancements <https://www.unrealircd.org/docs/PQC_measures>. *Wrapping up the year* I would like to take this opportunity to thank: * Our current monthly sponsors - IRCCloud, Réseau IRC Zeolia, Jellis, Rafael Grether, Dex, NerdyEnough - and everyone else who donated this year. * People who filed bugs, made feature suggestions, updated the documentation, all helping to make UnrealIRCd a better product. * Coders and contributors, Valware in particular. * Supporters and everyone else who helped people in #unreal-support and on the forums. * Finally, everyone who runs UnrealIRCd as part of their community along with all their users. Next release, 6.2.3, is scheduled for Q1 2026. We wish everyone a merry Christmas and a happy new year! As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with the command: ./unrealircd upgrade Enhancements: * Support for IRCv3 network icon <https://ircv3.net/specs/extensions/network-icon>. At the moment IRCCloud and ObsidianIRC display this. Simply provide an image URL (be sure to use single quotes): |set { network-icon 'https://.....'; }| * New JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC> functions: o |message| <https://www.unrealircd.org/docs/JSON-RPC:Message>: send messages/notices/numerics/standard-replies to users. o |security_group| <https://www.unrealircd.org/docs/JSON-RPC:Security_group>: List and get details of security groups <https://www.unrealircd.org/docs/Security-group_block>. o |connthrottle| <https://www.unrealircd.org/docs/JSON-RPC:Connthrottle>: Get status of Connthrottle <https://www.unrealircd.org/docs/Connthrottle>, enable/disable and reset counters. Changes: * When we run configure for PCRE2 we now pass the original |CFLAGS| instead of the ones we add for ourselves (|-Wall -Wextra etc..|). * Update shipped libs: c-ares (1.34.6) Fixes: * Crash if the module |usermodes/bot| or |usermodes/noctcp| is not loaded. * Make delayjoin work properly with third party modules that deal with invisible users (such as Gottem's third/auditorium module). * If you specified a set::tls::certificate and set::tls::key then these were seen as "in addition to" the default |conf/tls/server.cert.pem| and |conf/tls/server.key.pem|, while it should be "instead of". This is now fixed. o Just as a reminder, we normally recommend keeping the self-signed certificate for server linking and using a certificate issued by a trusted CA for client traffic (such as on port 6697), see Using Let's Encrypt with UnrealIRCd <https://www.unrealircd.org/docs/Using_Let's_Encrypt_with_UnrealIRCd>. Developers and protocol: * We now allow |/| in ISUPPORT tokens. * When using labeled-response <https://ircv3.net/specs/extensions/labeled-response>, some line endings were |\r\r\n| instead or |\r\n|. * JSON-RPC |channel.kick| now checks if the victim is actually in the channel and if not, responds with |JSON_RPC_ERROR_USERNOTINCHANNEL|. * Add new hook |HOOKTYPE_MOTD| so modules can add text at the end of the MOTD. * The |SJOIN| command now has |CMD_BIGLINES| support (incoming only). Please don't send such long lines yet, this is for future-proofing. |
|
From: Bram M. <sy...@un...> - 2025-11-02 15:51:25
|
UnrealIRCd 6.2.1 focusses on performance improvements, but it also comes with various new features and fixes, such as: webhooks, UTF8ONLY, IRCv3 draft/extended-isupport, support for multiple certificate/keys, etc. NOTE: If you were running 6.2.1-rc2 (so testing the last release candidate) then please upgrade to 6.2.1 stable, due to an issue with channel messaging on multi-servers and +H. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * A lot of optimizations were done: o Writes to SSL/TLS clients use 15-20% less CPU. o For hub servers various improvement add up to roughly 30%, depending on traffic. o Especially 100+ member channels (and even more so 1000+) are handled faster now due to various improvements regarding channel membership. o A concrete peak-load case would be a server losing a link (SQUIT) with 10,000 clones all in 10 channels. Previously this took 40 seconds at 100% CPU to process, now it takes only 2 seconds. * The log block now supports calling a webhook <https://www.unrealircd.org/docs/Log_block#Calling_a_webhook> on selected events. It's not suggested for high-rate events (xx per second) but for other events it can be quite useful to do a HTTPS call. * Add set::utf8-only <https://www.unrealircd.org/docs/Set_block#set::utf8-only>: setting this to |yes| means all IRC traffic is UTF8 only. See the setting and the |UTF8ONLY| <https://ircv3.net/specs/extensions/utf8-only> specification for more details. * Add |server-port| to the security-group block <https://www.unrealircd.org/docs/Security-group_block> and mask items <https://www.unrealircd.org/docs/Mask_item>. And the |server_port()| function in Crule <https://www.unrealircd.org/docs/Crule>. * When set::send-isupport-updates <https://www.unrealircd.org/docs/Set_block#set::send-isupport-updates> is enabled, we now send ISUPPORT updates for all values and not only for |CHANMODES|/|PREFIX|/|STATUSMSG|. (For example, changing set::min-nick-length would broadcast a |MINNICKLEN| change) * Add support for IRCv3 |draft/extended-isupport| <https://github.com/ircv3/ircv3-specifications/blob/master/extensions/extended-isupport.md> * We now support multiple TLS certificates/keys, such as ECDSE + ML-DSA (Post Quantum Crypto). Such a dual key approach may make sense in the future (see commit) <https://github.com/unrealircd/unrealircd/commit/877d151da41f3a20fa277f0a919c69576a4611ac> * You can now use |password| multiple times in the config file. This can come in handy in the future if we have link blocks with multiple passwords but also works with allow::password or vhost::password. Simply specify multiple password items and they are treated as a "if any of these succeed then the authentication is a PASS" (so it is an OR match, not an AND). * Add set::tls::signature-algorithms <https://www.unrealircd.org/docs/Set_block#set::tls::signature-algorithms>. We don't set it at the moment. It's just an additional knob in case something needs to be adjusted (e.g. if you need to disable something due to a vulnerability). * If TLSv1.3 is available on the system then calls to Central Blocklist <https://www.unrealircd.org/docs/Central_Spamfilter> and Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> will only use TLSv1.3. * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: o Add |away_reason| and |away_since| to the user object <https://www.unrealircd.org/docs/JSON-RPC:Client_Object#client.user_object>. o Add |server_port| and |local_port| to client objects (also in JSON Logging) * Since nearly everyone wants UnrealIRCd to start at system startup, we (already) tell about adding a Cron job <https://www.unrealircd.org/docs/Cron_job>. We now also ship with a Systemd unit <https://www.unrealircd.org/docs/Using_systemd_with_UnrealIRCd> for those who prefer using that. Changes: * In previous version 6.2.0 we turned channel flood protection on by default <https://www.unrealircd.org/docs/Channel_anti-flood_settings>. Now, when channel flood protection kicks in we tell chanops to run |MODE #channel +F| to get more information about the flood settings. The output of that command has been improved as well. * Best practices now have their own logging category 'advice', which is blue. * Previous (expired) UnrealIRCd PGP key was removed from |doc/KEYS| * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: For the |server_ban.*| and similar TKL calls use the "issuer" if the |set_by| field is not set. * Update offline |doc/unrealircd_wiki.zim| to current wiki Fixes: * Crash with proxy { } block <https://www.unrealircd.org/docs/Proxy_block> * Possible crash in |STATS maxperip| (IRCOp-only) * Make Remote includes <https://www.unrealircd.org/docs/Remote_includes> work on IPv6-only machines. * The |TLINE| command did not behave the same as e.g. |GLINE| for Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> which was confusing. * Memory leak in DEBUGMODE (only used by developers) Developers and protocol: * |client->local->caps| changes to a 64 bit unsigned int on all archs * We now run quick CI jobs at GitHub as well, e.g. for PRs and commits. This is in addition to the self-hosted BuildBot that is not public. * The (near last) sanitizer question in |./Config| will now not only enable AddressSanitizer, but also UndefinedBehaviorSanitizer. As always, we recommend developers to turn this on since it will often catch bugs. |
|
From: Bram M. <sy...@un...> - 2025-10-23 16:27:55
|
This is the second Release Candidate for future version 6.2.1. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ This version focussed on performance improvements but also various small new features were added. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * A lot of optimizations were done: o Writes to SSL/TLS clients use 15-20% less CPU. o For hub servers various improvement add up to roughly 30%, depending on traffic. o Especially 100+ member channels (and even more so 1000+) are handled faster now due to various improvements regarding channel membership. o A concrete peak-load case would be a server losing a link (SQUIT) with 10,000 clones all in 10 channels. Previously this took 40 seconds at 100% CPU to process, now it takes only 2 seconds. * Add set::utf8-only <https://www.unrealircd.org/docs/Set_block#set::utf8-only>: setting this to |yes| means all IRC traffic is UTF8 only. See the setting and the |UTF8ONLY| <https://ircv3.net/specs/extensions/utf8-only> specification for more details. * Add |server-port| to the security-group block <https://www.unrealircd.org/docs/Security-group_block> and mask items <https://www.unrealircd.org/docs/Mask_item>. And the |server_port()| function in Crule <https://www.unrealircd.org/docs/Crule>. * When set::send-isupport-updates <https://www.unrealircd.org/docs/Set_block#set::send-isupport-updates> is enabled, we now send ISUPPORT updates for all values and not only for |CHANMODES|/|PREFIX|/|STATUSMSG|. (For example, changing set::min-nick-length would broadcast a |MINNICKLEN| change) * Add support for IRCv3 |draft/extended-isupport| <https://github.com/ircv3/ircv3-specifications/blob/master/extensions/extended-isupport.md> * We now support multiple TLS certificates/keys, such as ECDSE + ML-DSA (Post Quantum Crypto). Such a dual key approach may make sense in the future (see commit) <https://github.com/unrealircd/unrealircd/commit/877d151da41f3a20fa277f0a919c69576a4611ac> * You can now use |password| multiple times in the config file. This can come in handy in the future if we have link blocks with multiple passwords but also works with allow::password or vhost::password. Simply specify multiple password items and they are treated as a "if any of these succeed then the authentication is a PASS" (so it is an OR match, not an AND). * Add set::tls::signature-algorithms <https://www.unrealircd.org/docs/Set_block#set::tls::signature-algorithms>. We don't set it at the moment. It's just an additional knob in case something needs to be adjusted (e.g. if you need to disable something due to a vulnerability). * If TLSv1.3 is available on the system then calls to Central Blocklist <https://www.unrealircd.org/docs/Central_Spamfilter> and Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> will only use TLSv1.3. * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: o Add |away_reason| and |away_since| to the user object <https://www.unrealircd.org/docs/JSON-RPC:Client_Object#client.user_object>. o Add |server_port| and |local_port| to client objects (also in JSON Logging) Changes: * Best practices now have their own logging category 'advice', which is blue. * Previous (expired) UnrealIRCd PGP key was removed from |doc/KEYS| * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: For the |server_ban.*| and similar TKL calls use the "issuer" if the |set_by| field is not set. * Update offline |doc/unrealircd_wiki.zim| to current wiki Fixes: * Crash with proxy { } block <https://www.unrealircd.org/docs/Proxy_block> * Possible crash in |STATS maxperip| (IRCOp-only) * Make Remote includes <https://www.unrealircd.org/docs/Remote_includes> work on IPv6-only machines. * The |TLINE| command did not behave the same as e.g. |GLINE| for Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> which was confusing. * Memory leak in DEBUGMODE (only used by developers) Developers and protocol: * |client->local->caps| changes to a 64 bit unsigned int on all archs * We now run quick CI jobs at GitHub as well, e.g. for PRs and commits. This is in addition to the self-hosted BuildBot that is not public. * The (near last) sanitizer question in |./Config| will now not only enable AddressSanitizer, but also UndefinedBehaviorSanitizer. As always, we recommend developers to turn this on since it will often catch bugs. |
|
From: Bram M. <sy...@un...> - 2025-10-12 13:28:23
|
This is the Release Candidate for future version 6.2.1. You can help us by testing this release and reporting bugs to https://bugs.unrealircd.org/ This version focussed on performance improvements but also various small new features were added. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with the command: ./unrealircd upgrade --rc Enhancements: * A lot of optimizations were done: o Writes to SSL/TLS clients use 15-20% less CPU. o For hub servers various improvement add up to roughly 30%, depending on traffic. o Especially 100+ member channels (and even more so 1000+) are handled faster now due to various improvements regarding channel membership. o A concrete peak-load case would be a server losing a link (SQUIT) with 10,000 clones all in 10 channels. Previously this took 40 seconds at 100% CPU to process, now it takes only 2 seconds. * Add set::utf8-only <https://www.unrealircd.org/docs/Set_block#set::utf8-only>: setting this to |yes| means all IRC traffic is UTF8 only. See the setting and the |UTF8ONLY| <https://ircv3.net/specs/extensions/utf8-only> specification for more details. * Add |server-port| to the security-group block <https://www.unrealircd.org/docs/Security-group_block> and mask items <https://www.unrealircd.org/docs/Mask_item>. And the |server_port()| function in Crule <https://www.unrealircd.org/docs/Crule>. * When set::send-isupport-updates <https://www.unrealircd.org/docs/Set_block#set::send-isupport-updates> is enabled, we now send ISUPPORT updates for all values and not only for |CHANMODES|/|PREFIX|/|STATUSMSG|. (For example, changing set::min-nick-length would broadcast a |MINNICKLEN| change) * Add support for IRCv3 |draft/extended-isupport| <https://github.com/ircv3/ircv3-specifications/blob/master/extensions/extended-isupport.md> * We now support multiple TLS certificates/keys, such as ECDSE + ML-DSA (Post Quantum Crypto). Such a dual key approach may make sense in the future (see commit) <https://github.com/unrealircd/unrealircd/commit/877d151da41f3a20fa277f0a919c69576a4611ac> * You can now use |password| multiple times in the config file. This can come in handy in the future if we have link blocks with multiple passwords but also works with allow::password or vhost::password. Simply specify multiple password items and they are treated as a "if any of these succeed then the authentication is a PASS" (so it is an OR match, not an AND). * Add set::tls::signature-algorithms <https://www.unrealircd.org/docs/Set_block#set::tls::signature-algorithms>. We don't set it at the moment. It's just an additional knob in case something needs to be adjusted (e.g. if you need to disable something due to a vulnerability). * If TLSv1.3 is available on the system then calls to Central Blocklist <https://www.unrealircd.org/docs/Central_Spamfilter> and Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> will only use TLSv1.3. * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: o Add |away_reason| and |away_since| to the user object <https://www.unrealircd.org/docs/JSON-RPC:Client_Object#client.user_object>. o Add |server_port| and |local_port| to client objects (also in JSON Logging) Changes: * Best practices now have their own logging category 'advice', which is blue. * Previous (expired) UnrealIRCd PGP key was removed from |doc/KEYS| * JSON-RPC <https://www.unrealircd.org/docs/JSON-RPC>: For the |server_ban.*| and similar TKL calls use the "issuer" if the |set_by| field is not set. Fixes: * Make Remote includes <https://www.unrealircd.org/docs/Remote_includes> work on IPv6-only machines. * The |TLINE| command did not behave the same as e.g. |GLINE| for Extended Server Bans <https://www.unrealircd.org/docs/Extended_server_bans> which was confusing. * Possible crash in |STATS maxperip| (IRCOp-only) * Memory leak in DEBUGMODE (only used by developers) Developers and protocol: * |client->local->caps| changes to a 64 bit unsigned int on all archs * We now run quick CI jobs at GitHub as well, e.g. for PRs and commits. This is in addition to the self-hosted BuildBot that is not public. |
|
From: Bram M. <sy...@un...> - 2025-09-09 16:40:34
|
UnrealIRCd 6.2.0 has channel flood protection turned on by default, UTF8 Text Analysis and Spamfilter enhancements, new best practices regarding plaintext port 6667 and TLS certificates, PQC enhancements, etc. All this to make chatting on IRC more secure and with less spam. It is highly recommended to read the release notes below. Or, at least read the first item under "Enhancements" there. The beta's for 6.2.0 didn't receive as much testing as I would have liked. If you want to hold off for a while because you are cautious or if you depend on 3rd party modules then feel free to wait for version 6.2.1. (At the time of this 6.2.0 release quite some 3rd party modules have not been updated to work with 6.2.x) As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with the command: ./unrealircd upgrade Note that our PGP key expired in June 2025, so all our files are signed by the new PGP key. The new key was created and announced in Nov 2024 already in this post <https://forums.unrealircd.org/viewtopic.php?t=9397>. UnrealIRCd 6.1.9 and 6.1.10 have the new key in the doc/KEYS <https://github.com/unrealircd/unrealircd/commit/3aa26ef1f1bd60d8508d503076bad8887967410e> file (because they were published on/after Nov 2024). With UnrealIRCd 6.1.9 and 6.1.10 the ./unrealircd upgrade command will work fine. On older versions of UnrealIRCd, however, you will get a scary warning. Enhancements: * Channel flood protection by default <https://www.unrealircd.org/docs/Channel_anti-flood_settings>: This is an important change that IRCOps and chanops should know about: o By default we now apply the anti-flood profile "normal", which should be fine for most channels. o If a chanop does not want this they can override this by setting |MODE +F| with another profile <https://www.unrealircd.org/docs/Channel_anti-flood_settings#Channel_mode_F_profiles>. o For example, for a channel with hundreds of users and lots of activity |+F relaxed| may be more appropriate. Or, chanops can turn anti-flood off entirely by setting |+F off| o The reason for this change is that many admins and chanops in practice don't seem to use |+f| or |+F|. With this change they are now protected "by default" when no MODE |+f| or |+F| is set. o Advanced users can can grab the detailed effective settings with |MODE #test F| o The default protection can be lowered in the config file with: set { anti-flood { channel { default-profile relaxed; } } } Note that doing so would lower protection for everyone. You can also use |off| instead of |relaxed| to disable it entirely (which is not recommended but makes it how things were before 6.2.x). We recommend using |normal| (which is the default already) and doing per-channel exceptions via |+F| where needed. * AntiMixedUTF8 <https://www.unrealircd.org/docs/Set_block#set::antimixedutf8>: This is now aware of a lot more unicode blocks. This will cause a higher score for some regular messages, so be aware if you have the score set very low (eg 2 or 3). On the plus-side, spam should now get an even higher score. Try a score between 5 and 10 and see if that works. * Spamfilter <https://www.unrealircd.org/docs/Spamfilter> and text analysis: o spamfilter::rule now supports |unicode_count('utf8 block name')|, like: |rule "unicode_count('Emoticons')>2";| o spamfilter::input-conversion now supports |deconfused| which will "deconfuse" text like "Ŧ𝕙ї𝘀 𝜄ŝ ạ 𝑡êśȶ" to "This is a test" so it can easily be matched on with simple matching or a regex. This will never be 100% perfect but can be helpful. o A new |SPAMINFO <text>| command which shows Text Analysis: scores for AntiMixedUTF8, how the text shows up "deconfused", which unicode blocks are used, etc. o The same Text Analysis is now in JSON logs for spamfilter hits and antimixedutf8 hits. * Best Practices <https://www.unrealircd.org/docs/Set_block#set::best-practices>: If any plaintext ports are found open, we will give an advice to move users to TLS. o The Use TLS <https://www.unrealircd.org/docs/Use_TLS> article explains why and shows how to do a gradual rollout, with warnings and automatic upgrades from plaintext to TLS for IRC clients that support it. o This message can be turned off by setting set::best-practices::listen-nontls-port <https://www.unrealircd.org/docs/Set_block#set::best-practices> to |no|. But please, read the Use TLS <https://www.unrealircd.org/docs/Use_TLS> article first. o You won't get this warning if set::plaintext-policy::user is |deny| or when the listen::ip is |127.0.0.1| or |::1|. * Best Practices <https://www.unrealircd.org/docs/Set_block#set::best-practices>: If no SSL/TLS cert is present that is issued by a trusted Certificate Authority, then we will give a suggestion to use Let's Encrypt. This can be turned off via set::best-practices::trusted-cert <https://www.unrealircd.org/docs/Set_block#set::best-practices>. For servers without any client listener blocks (or only on localhost) this message is not triggered (for e.g. hubs). * Post-quantum cryptography (PQC) enhancements: o set::tls <https://www.unrealircd.org/docs/TLS_Ciphers_and_protocols>: Rename |ecdh-curves| to |groups| (the old name will continue to work) o Add (and prefer) the |X25519MLKEM768| hybrid group, which is a mix of |X25519| that is commonly used today and quantum-safe |ML-KEM-768|. This to protect against "harvest now, decrypt later" <https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later>. o To benefit from this, OpenSSL 3.5.0 or later (released April 2025) is required on the server, and similarly a client that supports this. At the time of writing, almost no Linux distro has such an OpenSSL version yet (which is not a problem, this new feature will simply not be available). Notably Debian 13 has it, and our Windows build. o Also, change the TLS information on-connect and in WHOIS etc. from something like |TLSv1.3-TLS_CHACHA20_POLY1305_SHA256| to |TLSv1.3/X25519/TLS_CHACHA20_POLY1305_SHA256|. In other words: using slashes as separators and showing the group / key exchange in the middle. The group is only shown on newer OpenSSL versions. If someone would use the new PQC hybrid group mentioned above then their TLS info would start with |TLSv1.3/X25519MLKEM768/|. o TL;DR: better secrecy against future quantum attacks, even though not many clients or servers support it at the moment. * UnrealIRCd can now be used if your OpenSSL does not provide MD5 (there will be an error if you use |cloak_md5|, but everything will work fine if you use |cloak_sha256|). Changes: * Windows: we now use OpenSSL instead of LibreSSL. This also means PQC is available on Windows now (see Post-quantum cryptography above). * When a netsplit happens and set::server-linking::autoconnect-strategy <https://www.unrealircd.org/docs/Set_block#set::server-linking> is |sequential| (which is the default) or |sequential-fallback| (which is a good value for leafs) then we now consistently wait for class::connfreq <https://www.unrealircd.org/docs/Class_block> seconds before trying to connect to the (same or next) server. By default this is 15 seconds in the example configuration file server class. The reason for this is to provide a consistent behavior. Previously we waited semi-randomly for 0 to class::connfreq seconds. The previous behavior caused the picking of 'next server to try' to be inconsistent, which especially caused issues for |sequential-fallback|. If you want quicker recovery times in case of a netsplit, simply lower the value of class::connfreq <https://www.unrealircd.org/docs/Class_block> in your configuration file, e.g. to 5 instead of 15 seconds. * Currently it is still possible to link servers without certificate verification. This would be rare, since our server linking guide <https://www.unrealircd.org/docs/Tutorial:_Linking_servers> and |./unrealircd genlinkblock| use certificate verification. Since 2017 you'll get a message on-link when this happens with concrete advice to fix it. The wording has now been changed to be a clear warning about MITM <https://en.wikipedia.org/wiki/Man-in-the-middle_attack> attacks. In 2026Q2 we will turn this into a hard error. * Make error message if SSL/TLS cert or key is missing more helpful. * Update offline doc/unrealircd_wiki.zim to current wiki * Update shipped libs: PCRE2 (10.45), c-ares (1.34.5) * Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> now receives the last 20 lines instead of 10 and Text Analysis is included (such as which unicode blocks used in the messages). * Currently it is still possible to link servers without certificate verification. This would be rare, since our linking guides and |./unrealircd genlinkblock| use certificat verification. Since 2017 you'll get a "suggestion" on-link when this happens with concrete advice to fix this. The wording has now been changed to be a clear warning about MITM <https://en.wikipedia.org/wiki/Man-in-the-middle_attack> attacks. In 2026Q2 we will turn this into a hard error. Fixes: * |OS JUPE| not working (still allowing the server in) * Reputation scores <https://www.unrealircd.org/docs/Reputation_score> now really expire after 90 days. * For |./unrealircd genlinkblock| skip IP-detection if it is localhost. * Crash on |REHASH -dns| (IRCOp-only) Developers and protocol: * Command handlers (and overrides) now have an extra argument |ClientContext *clictx|. At the moment this has |clictx->cmd| which points to the command handler and |clictx->textanalysis| which may hold TextAnalysis info. In the future this struct can easily be extended. In your modules you should normally use |CMD_FUNC(cmd_mycmd)| and |CMD_OVERRIDE_FUNC(myoverridefunc)| and |CALL_NEXT_COMMAND_OVERRIDE()| and then your module does not updating between 6.1.x and 6.2.x. * TextAnalysis can be enabled for the last parameter in a command by setting |CMD_TEXTANALYSIS| in |CommandAdd()|. This is done by |PRIVMSG| and |SPAMINFO| for example. * New hook |HOOKTYPE_BANNED_CLIENT| * New hook |HOOKTYPE_CAN_USE_NICK| * On Windows the variables |LIBRESSL_INC_DIR| and |LIBRESSL_LIB_DIR| are now |SSL_INC_DIR| and |SSL_LIB_DIR| because we no longer use nor assume LibreSSL. |
|
From: Bram M. <sy...@un...> - 2025-08-01 10:19:44
|
UnrealIRCd 6.2.0-beta3 is now available for testing. I didn't announce beta1 and beta2 here to keep list traffic minimal, but now I think I can :). This version is not a stable release and does not contain all the features that are scheduled for 6.2.0 yet. This beta exists so people can test things, report bugs and give other feedback. Please use https://bugs.unrealircd.org/ for that. You can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade to the beta version with ./unrealircd upgrade --beta Note that our PGP key expired in June 2025, so all our files are signed by the new PGP key. The new key was created and announced in Nov 2024 already in this post <https://forums.unrealircd.org/viewtopic.php?t=9397>. UnrealIRCd 6.1.9 and 6.1.10 have the new key in the doc/KEYS <https://github.com/unrealircd/unrealircd/commit/3aa26ef1f1bd60d8508d503076bad8887967410e> file (because they were published on/after Nov 2024). With UnrealIRCd 6.1.9 and 6.1.10 the ./unrealircd upgrade --beta command will work fine. On older versions of UnrealIRCd, however, you will get a scary warning. Enhancements: * Channel flood protection by default <https://www.unrealircd.org/docs/Channel_anti-flood_settings>: This is an important change that IRCOps and chanops should know about: o By default we now apply the anti-flood profile "normal", which should be fine for most channels. o If a chanop does not want this they can override this by setting |MODE +F| with another profile <https://www.unrealircd.org/docs/Channel_anti-flood_settings#Channel_mode_F_profiles>. o For example, for a channel with hundreds of users and lots of activity |+F relaxed| may be more appropriate. Or, chanops can turn anti-flood off entirely by setting |+F off| o The reason for this change is that many admins and chanops in practice don't seem to use |+f| or |+F|. With this change they are now protected "by default" when no MODE |+f| or |+F| is set. o Advanced users can can grab the detailed effective settings with |MODE #test F| o The default protection can be lowered in the config file with: set { anti-flood { channel { default-profile relaxed; } } } Note that doing so would lower protection for everyone. You can also use |off| instead of |relaxed| to disable it entirely (which is not recommended but makes it how things were before 6.2.x). We recommend using |normal| (which is the default already) and doing per-channel exceptions via |+F| where needed. * AntiMixedUTF8 <https://www.unrealircd.org/docs/Set_block#set::antimixedutf8>: This is now aware of a lot more unicode blocks. This will cause a higher score for some regular messages, so be aware if you have the score set very low (eg 2 or 3). On the plus-side, spam should now get an even higher score. Try a score between 5 and 10 and see if that works. * Spamfilter <https://www.unrealircd.org/docs/Spamfilter> and text analysis: o spamfilter::rule now supports |unicode_count('utf8 block name')|, like: |rule "unicode_count('Emoticons')>2";| o spamfilter::input-conversion now supports |deconfused| which will "deconfuse" text like "Ŧ𝕙ї𝘀 𝜄ŝ ạ 𝑡êśȶ" to "This is a test" so it can easily be matched on with simple matching or a regex. This will never be 100% perfect but can be helpful. o A new |SPAMINFO <text>| command which shows Text Analysis: scores for AntiMixedUTF8, how the text shows up "deconfused", which unicode blocks are used, etc. o The same Text Analysis is now in JSON logs for spamfilter hits and antimixedutf8 hits. * Best Practices <https://www.unrealircd.org/docs/Set_block#set::best-practices>: If any plaintext ports are found open, we will give an advice to move users to TLS. o The Use TLS <https://www.unrealircd.org/docs/Use_TLS> article explains why and shows how to do a gradual rollout, with warnings and automatic upgrades from plaintext to TLS for IRC clients that support it. o This message can be turned off by setting set::best-practices::listen-nontls-port <https://www.unrealircd.org/docs/Set_block#set::best-practices> to |no|. But please, read the Use TLS <https://www.unrealircd.org/docs/Use_TLS> article first. o You won't get this warning if set::plaintext-policy::user is |deny| or when the listen::ip is |127.0.0.1| or |::1|. * Best Practices <https://www.unrealircd.org/docs/Set_block#set::best-practices>: If no SSL/TLS cert is present that is issued by a trusted Certificate Authority, then we will give a suggestion to use Let's Encrypt. This can be turned off via set::best-practices::trusted-cert <https://www.unrealircd.org/docs/Set_block#set::best-practices>. For servers without any client listener blocks (or only on localhost) this message is not triggered (for e.g. hubs). * Post-quantum cryptography (PQC) enhancements: o set::tls <https://www.unrealircd.org/docs/TLS_Ciphers_and_protocols>: Rename |ecdh-curves| to |groups| (the old name will continue to work) o Add (and prefer) the |X25519MLKEM768| hybrid group, which is a mix of |X25519| that is commonly used today and quantum-safe |ML-KEM-768|. This to protect against "harvest now, decrypt later" <https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later>. o To benefit from this, OpenSSL 3.5.0 or later (released April 2025) is required on the server, and similarly a client that supports this. At the time of writing, almost all Linux distros don't have such an OpenSSL version yet (which is not a problem, this new feature will simply not be available). Notably Debian 13 (when released in August 2025) will have it. LibreSSL does not support it either yet, so our Windows build does not have this feature. o Also, change the TLS information on-connect and in WHOIS etc. from something like |TLSv1.3-TLS_CHACHA20_POLY1305_SHA256| to |TLSv1.3/X25519/TLS_CHACHA20_POLY1305_SHA256|. In other words: using slashes as separators and showing the group / key exchange in the middle. The group is only shown on newer OpenSSL versions. If someone would use the new PQC hybrid group mentioned above then their TLS info would start with |TLSv1.3/X25519MLKEM768/|. o TL;DR: better secrecy against future quantum attacks, even though not many clients or servers support it at the moment. * UnrealIRCd can now be used if your OpenSSL does not provide MD5 (there will be an error if you use |cloak_md5|, but everything will work fine if you use |cloak_sha256|). Changes: * When a netsplit happens and set::server-linking::autoconnect-strategy <https://www.unrealircd.org/docs/Set_block#set::server-linking> is |sequential| (which is the default) or |sequential-fallback| (which is a good value for leafs) then we now consistently wait for class::connfreq <https://www.unrealircd.org/docs/Class_block> seconds before trying to connect to the (same or next) server. By default this is 15 seconds in the example configuration file server class. The reason for this is to provide a consistent behavior. Previously we waited semi-randomly for 0 to class::connfreq seconds. The previous behavior caused the picking of 'next server to try' to be inconsistent, which especially caused issues for |sequential-fallback|. If you want quicker recovery times in case of a netsplit, simply lower the value of class::connfreq <https://www.unrealircd.org/docs/Class_block> in your configuration file, e.g. to 5 instead of 15 seconds. * Currently it is still possible to link servers without certificate verification. This would be rare, since our server linking guide <https://www.unrealircd.org/docs/Tutorial:_Linking_servers> and |./unrealircd genlinkblock| use certificate verification. Since 2017 you'll get a message on-link when this happens with concrete advice to fix it. The wording has now been changed to be a clear warning about MITM <https://en.wikipedia.org/wiki/Man-in-the-middle_attack> attacks. In 2026Q2 we will turn this into a hard error. * Make error message if SSL/TLS cert or key is missing more helpful. * Update offline doc/unrealircd_wiki.zim to current wiki * Update shipped libs: PCRE2 (10.45), c-ares (1.34.5) * Central Spamreport <https://www.unrealircd.org/docs/Central_spamreport> now receives the last 20 lines instead of 10 and Text Analysis is included (such as which unicode blocks used in the messages). * Currently it is still possible to link servers without certificate verification. This would be rare, since our linking guides and |./unrealircd genlinkblock| use certificat verification. Since 2017 you'll get a "suggestion" on-link when this happens with concrete advice to fix this. The wording has now been changed to be a clear warning about MITM <https://en.wikipedia.org/wiki/Man-in-the-middle_attack> attacks. In 2026Q2 we will turn this into a hard error. Fixes: * |OS JUPE| not working (still allowing the server in) * Reputation scores <https://www.unrealircd.org/docs/Reputation_score> now really expire after 90 days. * For |./unrealircd genlinkblock| skip IP-detection if it is localhost. * Crash on |REHASH -dns| (IRCOp-only) Developers and protocol: * Command handlers (and overrides) now have an extra argument |ClientContext *clictx|. At the moment this has |clictx->cmd| which points to the command handler and |clictx->textanalysis| which may hold TextAnalysis info. In the future this struct can easily be extended. In your modules you should normally use |CMD_FUNC(cmd_mycmd)| and |CMD_OVERRIDE_FUNC(myoverridefunc)| and |CALL_NEXT_COMMAND_OVERRIDE()| and then your module does not updating between 6.1.x and 6.2.x. * TextAnalysis can be enabled for the last parameter in a command by setting |CMD_TEXTANALYSIS| in |CommandAdd()|. This is done by |PRIVMSG| and |SPAMINFO| for example. * New hook |HOOKTYPE_BANNED_CLIENT| * New hook |HOOKTYPE_CAN_USE_NICK| |
|
From: Bram M. <sy...@un...> - 2025-03-07 14:16:46
|
UnrealIRCd 6.1.10 is now available. This is mostly a maintenance release with a few small new features. See the release notes below. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with ./unrealircd upgrade. Do you like UnrealIRCd? Consider making a donation <https://www.unrealircd.org/index/donations> or order something from the shop <https://shop.unrealircd.org>. NOTE for people who installed 6.1.10-rc1: there are no changes between 6.1.10-rc1 and 6.1.10 except for the version number. Enhancements: * In the spamfilter { } <https://www.unrealircd.org/docs/Spamfilter_block> block two new options: o |input-conversion|: This can be set to |none| to make the spamfilter run against the original text. This in contrast to how default spamfilter behaves where the text is matched against text that has color and control codes removed. Can be useful if you need to match against such a special character. o |show-message-content-on-hit|: this works like set::show-message-content-on-hit <https://www.unrealircd.org/docs/Set_block#set::spamfilter::show-message-content-on-hit>. but on an individual spamfilter basis. * If |unrealircd.conf| doesn't exist then we now offer to copy the example configuration (showing a list of languages to pick from). * Ship with an offline copy of the wiki documentation (|doc/unrealircd_wiki.zim|). This is really only meant for cases where the wiki is unavailable, eg you don't have an internet connection, some major outage, etc. See ZIM <https://en.wikipedia.org/wiki/ZIM_(file_format)> and Kiwix <https://en.wikipedia.org/wiki/Kiwix> for more information. Changes: * Update the example configuration: o Mark specific sections with "CHANGE THIS" for people who are in a hurry and really only want to do the bare minimum to get the IRCd booted. o More things are commented out by default, like example link blocks and ulines. o In addition to the the default ircd.log text file log block, also add a JSON log block <https://www.unrealircd.org/docs/JSON_logging#Enabling_in_disk_logging>. JSON logging includes a lot of information about every event so is great for auditing purposes and machine readable. * Error on some more duplicate config items, eg allow::password. * In target-flood log messages we now show the message type (eg PRIVMSG). * Make the |./Config| question about remote includes <https://www.unrealircd.org/docs/Remote_includes> a bit more clear. The |https://| protocol is always supported and this question is only about supporting /other/ protocols and using the cURL library. Fixes: * Fix compile problems on (upcoming) GCC 15 as it assumes C23 by default. This for future Fedora 42 and possibly Ubuntu 25.04, both scheduled around April 2025. * Fix crash on |SPAMREPORT <ip>| (IRCOp-only command) if the central-blocklist module is loaded. * Fix make_channel() not checking minimal validity of channel names. Only an issue for (bad) trusted remote server traffic. You can download UnrealIRCd from https://www.unrealircd.org/ |
|
From: Bram M. <sy...@un...> - 2025-02-16 09:09:07
|
Hi everyone, The release candidate for 6.1.10 is now available. The actual 6.1.10 stable release will be in the week of March 7, 2025. You can help us by testing this release and reporting any bugs you find at https://bugs.unrealircd.org/ If you are on *NIX, you can upgrade to this release candidate with: ./unrealircd upgrade --rc This is mostly a maintenance release with a few small new features. See the release notes below. Enhancements: * In the spamfilter { } <https://www.unrealircd.org/docs/Spamfilter_block> block two new options: o |input-conversion|: This can be set to |none| to make the spamfilter run against the original text. This in contrast to how default spamfilter behaves where the text is matched against text that has color and control codes removed. Can be useful if you need to match against such a special character. o |show-message-content-on-hit|: this works like set::show-message-content-on-hit <https://www.unrealircd.org/docs/Set_block#set::spamfilter::show-message-content-on-hit>. but on an individual spamfilter basis. * If |unrealircd.conf| doesn't exist then we now offer to copy the example configuration (showing a list of languages to pick from). * Ship with an offline copy of the wiki documentation (|doc/unrealircd_wiki.zim|). This is really only meant for cases where the wiki is unavailable, eg you don't have an internet connection, some major outage, etc. See ZIM <https://en.wikipedia.org/wiki/ZIM_(file_format)> and Kiwix <https://en.wikipedia.org/wiki/Kiwix> for more information. Changes: * Update the example configuration: o Mark specific sections with "CHANGE THIS" for people who are in a hurry and really only want to do the bare minimum to get the IRCd booted. o More things are commented out by default, like example link blocks and ulines. o In addition to the the default ircd.log text file log block, also add a JSON log block <https://www.unrealircd.org/docs/JSON_logging#Enabling_in_disk_logging>. JSON logging includes a lot of information about every event so is great for auditing purposes and machine readable. * Error on some more duplicate config items, eg allow::password. * In target-flood log messages we now show the message type (eg PRIVMSG). * Make the |./Config| question about remote includes <https://www.unrealircd.org/docs/Remote_includes> a bit more clear. The |https://| protocol is always supported and this question is only about supporting /other/ protocols and using the cURL library. Fixes: * Fix compile problems on (upcoming) GCC 15 as it assumes C23 by default. This for future Fedora 42 and possibly Ubuntu 25.04, both scheduled around April 2025. * Fix crash on |SPAMREPORT <ip>| (IRCOp-only command) if the central-blocklist module is loaded. * Fix make_channel() not checking minimal validity of channel names. Only an issue for (bad) trusted remote server traffic. You can download UnrealIRCd from https://www.unrealircd.org/ |
|
From: Bram M. <sy...@un...> - 2024-12-31 09:44:10
|
It's the end of the year, so why not take an opportunity to look back on it. This year UnrealIRCd celebrated its 25th year birthday <https://forums.unrealircd.org/viewtopic.php?t=9363>, which is an amazing achievement that goes all the way back to the days of Stskeeps and codemastr. *Nine UnrealIRCd releases this year* 2024 brought us five regular UnrealIRCd releases and four dot releases to quickly fix some bugs. Feature-wise we got ASN <https://www.unrealircd.org/docs/ASN> support, several new properties in security groups <https://www.unrealircd.org/docs/Security-group_block> and a lot of new functions in crules <https://www.unrealircd.org/docs/Crule>, more flexible ban user { } <https://www.unrealircd.org/docs/Ban_user_block> and require authentication { } <https://www.unrealircd.org/docs/Require_authentication_block> blocks because they now take a mask item <https://www.unrealircd.org/docs/Mask_item> for matching, a new extban <https://www.unrealircd.org/docs/Extended_bans#Group_4:_special> ~inherit to make people banned in one channel also banned in another, auto-vhost support was new, set::restrict-commands <https://www.unrealircd.org/docs/Restrict_commands> with a new option channel-create for managing who may create new channels, and so on. *Security was increased* Almost exactly a year ago (29-dec-2023) we changed the default SSL/TLS settings <https://www.unrealircd.org/docs/TLS_Ciphers_and_protocols> to only allow TLSv1.2 and TLSv1.3 protocols and requiring ciphers that provide Forward Secrecy <https://en.wikipedia.org/wiki/Forward_secrecy>. Later in 2024 we dropped support for AES in old CBC mode in the default settings, only allowing AES in GCM mode. Thanks to all this, Qualys SSL Labs gives a solid A rating <https://www.ssllabs.com/ssltest/analyze.html?d=irc.unrealircd.org&s=40.86.218.96>(*). On *NIX we have the handy "./unrealircd upgrade" command and we already do PGP/GPG verification of the release in there. This year we added support to also do PGP/GPG verification for hot and cold patching (those are used for quickly fixing issues, usually without a restart, thanks to modules). *Sponsors and keeping the project sustainable* Also new in 2024 is the sponsorship program <https://forums.unrealircd.org/viewtopic.php?t=9353>. We are happy people stepped in to cover the hosting costs. In particular we would like to thank IRCCloud for becoming a Platinum Sponsor, Réseau IRC Zeolia and Deutscher-Chat as Bronze Sponsors, and Dex, Jellis and Rafael Grether as Iron sponsors. Single donations are also still appreciated and so are the sponsors that contribute but wish to remain anonymous. Thanks to all this, and a little income from the shop <https://shop.unrealircd.org>, we cover almost 75% of the monthly running costs, which is great! *The community* Finally, I would like to thank the community: everyone who helps other people on irc.unrealircd.org and the forums. Everyone who contributes as a coder, translator or to the documentation/wiki. And naturally, all the admins/IRCOps who continue to use UnrealIRCd and invest time into growing their own IRC community, often each with their own niche, tinkering and tweaking their setup. On IRCStats <https://www.ircstats.org/servers> we can see UnrealIRCd is still going strong in terms of servers deployed. That's all thanks to the people who run UnrealIRCd, and the people who chat there. (*) SSL Labs does not allow specifying a port like 6697, however irc.unrealircd.org also listens on port 443. We do that for easy websocket testing and hence it can be analyzed. |
|
From: Bram M. <sy...@un...> - 2024-11-21 19:05:25
|
Sorry, there was a bug in the TLS ciphers in 6.1.9. This caused TLSv1.2 not to work with RSA certs. Glad we catched it within a day, fixed in UnrealIRCd 6.1.9.1. For the 40-50 people who already downloaded 6.1.9, see https://forums.unrealircd.org/viewtopic.php?t=9399 <https://forums.unrealircd.org/viewtopic.php?t=9399> on how to fix without restart. For all others: use UnrealIRCd 6.1.9.1 for new installs. The original 6.1.9 announcement is below: UnrealIRCd 6.1.9(.1) is now available. This release fixes a number of bugs, such as IPv6 hosts not resolving in UnrealIRCd 6.1.8/6.1.8.1 and 100% CPU usage in some circumstances. It also changes the SSL/TLS defaults to make things a little safer/better. Unless major issues are found this should be the last release of 2024. Next stable release is expected in January/February 2025. As always, you can download UnrealIRCd from unrealircd.org <https://www.unrealircd.org/> and on *NIX you can upgrade with ./unrealircd upgrade. Do you like UnrealIRCd? Consider making a donation <https://www.unrealircd.org/index/donations> or order something from the shop <https://shop.unrealircd.org>. Enhancements: * SSL/TLS: o Change default TLS ciphers <https://www.unrealircd.org/docs/TLS_Ciphers_and_protocols> to only allow AES in GCM mode and no longer in CBC mode. o When using cURL for remote includes <https://www.unrealircd.org/docs/Remote_includes> we now explicitly set the minimum required version to TLSv1.2 and set our default ciphers and ciphersuites. Note that by default in UnrealIRCd 6 the built-in (non-cURL) implementation is used for remote includes, which already used these defaults. Also note that most distros, like Ubuntu and Debian, already required TLSv1.2 or later effectively in cURL. o Regarding default ecdh-curves: we now try to set the curves list to |x25519:secp521r1:secp384r1:prime256v1| first, and if that fails then we try |secp521r1:secp384r1:prime256v1|. The former could fail due to SSL library restrictions (old library or when in FIPS mode). Previously we were also supposed to do it like that, but due to a bug always had X25519 turned off. Fixes: * IPv6 hosts not resolving in UnrealIRCd 6.1.8 and 6.1.8.1. * 100% CPU usage in some (rare) circumstances. The IRCd is still fully responsive, but of course high CPU usage is never good. * Crash in |STATS S| (IRCOp-only) if having vhosts with autologin (and no vhost::login). * The Windows version did not allow tweaking of set::tls::ecdh-curves. Changes: * Update shipped libraries: c-ares to 1.34.3 * Update Windows libraries: c-ares to 1.34.3, curl to 8.11.0 and LibreSSL to 4.0.0. * Added |HELPOP EXTSERVERBANS| to explain Extended server bans <https://www.unrealircd.org/docs/Extended_server_bans> * Added new UnrealIRCd PGP release signing key <https://forums.unrealircd.org/viewtopic.php?p=40832> Developers and protocol: * No changes, other than the SSL/TLS changes mentioned earlier. |