v2.0.27 released!

Posted by ~Sadie on November 06 2018

InspIRCd v2.0.27 is now available, download it from the releases page.

This release contains minor bug fixes and documentation corrections. Most notably:

  • Clients connecting via m_cgiirc will no longer have the wrong IP address shown in messages.
  • Several bugs in the WHO implementation and documentation have been fixed.
  • The configure checks for eventfd(), <stdint.h>, and strlcpy() have been fixed.

All users are recommended to upgrade.


v2.0.26 released!

Posted by ~Sadie on April 21 2018

InspIRCd v2.0.26 is now available, download it from the releases page.

This release contains bug fixes and documentation corrections. Most notably:

  • m_banredirect no longer creates phantom redirects in some rare cases.
  • m_cgiirc clients connecting from [GZK]Lined hosts through an ELined gateway are now banned correctly.
  • m_swhois messages set via an oper block are now correctly removed on deoper.
  • m_xline_db and m_spanningtree now store the correct user as the XLine setter.

All users are recommended to upgrade.


v2.0.25 released!

Posted by ~Sadie on November 12 2017

InspIRCd v2.0.25 is now available, download it from the releases page.

This release contains minor bug fixes, including fixes to m_cgiirc to protect again WebIRC gateways from sending malformed hostnames and CIDR [GKZ]Lines not respecting the protections set in <insane>. All users are recommended to upgrade.


v2.0.24 released!

Posted by ~Adam on May 18 2017

InspIRCd v2.0.24 is now available, download it from the releases page.

This release contains minor bug fixes, including fixes to the build system and module manager to work on newer perl versions (>5.24.1) which are common on newer systems. All users are recommended to upgrade.


v2.0.23 released!

Posted by ~Adam on September 03 2016

InspIRCd v2.0.23 is now available, download it from the releases page.

This release fixes a serious security vulnerability in m_sasl in combination with any services that support SASL EXTERNAL. To be vulnerable you must have m_sasl loaded, and have services which support SASL EXTERNAL authentication.

If you are affected and can not immediately upgrade, it is recommended to unload m_sasl, or otherwise disable all SASL EXTERNAL authentication in services.