InspIRCd v3.5.0 is now available, download it from the releases page.
This release fixes many minor bugs and adds several minor features. Most notably:
X-Real-IP and X-Forwarded-For headers to the websocket module.TAGMSG messages to be sent without any tags attached.No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3.
InspIRCd v3.4.0 is now available, download it from the releases page.
This release fixes many minor bugs and adds several minor features. Most notably:
<cloak:ignorecase> to ignore the case of a FQDN when cloaking.EV_SET workaround now that upstream have fixed the issue.No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3.
InspIRCd v3.3.0 is now available, download it from the releases page.
This release fixes a crash bug in the mysql module as well as adding several minor features. Most notably:
<chanfilter:maxlen> from 100 to 250.<bind:replace> enabled not being replaced in some circumstances.server-time timestamps on the server the source is connecting from.geo_maxmind module trying to interpret an AF_UNIX endpoint as an IP address.No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3.
InspIRCd v2.0.28 is now available, download it from the releases page.
This release fixes a crash bug in the mysql module as well as fixing several minor issues:
As mentioned previously InspIRCd v2 is now deprecated and will no longer receive security updates after 2020-05-31 2020-12-31. You should strongly consider updating to the v3 branch as soon as possible. Documentation on how to do so is available on the docs site.
InspIRCd v3.2.0 is now available, download it from the releases page.
This release fixes many minor bugs and adds several minor features. Most notably:
channels/auspex privilege not being able to request the topic of secret/private channels with the /TOPIC command.<pid:file> not being relative to the data directory as was intended.No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3.