UnrealIRCd 6.1.6

This is mostly a bug fix release but also comes with Crule enhancements.

UnrealIRCd turned 25 a few weeks ago! 🎉 See UnrealIRCd celebrates its 25th birthday.

Enhancements:

• Crule functions can now do everything that security group blocks can do.
  In practice, this means the following functions were added in this release:
  • is_tls() returns true if the client is using SSL/TLS
  • in_security_group('known-users') returns true if the user is in the specified security group.
  • match_mask('*@*.example.org') or match_mask('*.example.org') returns true if client matches mask.
  • match_ip('192.168.*') or with CIDR like match_ip('192.168.0.0/16') returns true if IP address of client matches.
  • is_identified() which returns true if the client is identified to a services account.
  • is_webirc() which returns true if the client is connected using WEBIRC.
  • is_websocket() which returns true if the client is connected using WebSockets.
  • match_realname('*xyz*') which returns true if the real name (gecos) contains xyz.
  • match_account('xyz') which returns true if the services account name is xyz.
  • match_country('NL') which returns true if GeoIP determined the country to be NL.
  • match_certfp('abc') which returns true if the Certificate fingerprint is abc.

Changes

• For many years REHASH -all is the same as REHASH so we now reject the former.
• The Crule function inchannel('#xyz') is now called in_channel('#xyz') to match the naming style of the other functions. The old name will keep working for the entire UnrealIRCd 6 series too.

Fixes

• Crash if you first REHASH and have a parse error (failed rehash 1) and then REHASH again but have a "late" rehash error, such as a remote include failing to load (failed rehash 2).
• Conditional config: using @if with a variable like @if $VAR == "something" always evaluated to false.
• A ~forward ban did not check ban exemptions (+e), always forwarding the user.
• When booting for the first time (without any cached files) the IRCd downloads GeoIP.dat. If that fails, e.g. due to lack of internet connectivity, we now show a warning and continue booting instead of it being a hard error. Note that we already dealt with this properly after the file has been cached (so after first download), see "What if your web server is down" in Remote includes.

Removed

• The tls-and-known-users security group was confusing, in the sense that this group consisted of tls-users and of known-users (in an OR fashion, not AND). Since this group is rarely used it has now been removed altogether. If you used it in your configuration then you can still manually (re)create the security group with: security-group tls-and-known-users { identified yes; reputation-score 25; tls yes; }

Developers and protocol

• Modules can now provide SASL locally, see Dev:Authentication module.