Availability of ModSecurity 2.7.7 Stable Release (Dec 19, 2013)
ModSecurity release 2.7.7 contains small fixes to allow an easy integration
to packaging generation and build automation. Tarball were renamed to fit the
same structure of older releases and configure scripts were placed back as
part of the Tarball. For further information on the changes check the
release notes. For issues, please check the Issues on GitHub.
Availability of ModSecurity 2.7.6 Stable Release (Dec 16, 2013)
We are pleased to announce ModSecurity release 2.7.6. Besides the bug fixes
this release also includes modification on the build system that counts on QA
mechanisms such as coding style checker and static analysis. All ports and all
platforms had some changes that may reduce the possibility of errors while
trying to compile the project. Regression tests and unit tests are now more
independent of platform or utilities versions. There is a new installer for MS
Windows. Libinjection was updated. For further information on the changes,
please check the
release notes. For more information about the fixed bugs or to report a new
one, have a look at our
Issues on GitHub.
Availability of ModSecurity 2.7.5 Stable Release (Jul 30, 2013) The ModSecurity Development Team is pleased to announce the availability of ModSecurity 2.7.5 Stable Release.The stability of this release is good, includes many bug fixes and some new features.
Specially libjection was updated and many issues, false positives, false negatives were fixed. NGINX compilation issue and a crash after reload were fixed. We added some small improvement like severity now accepts string.
Please see the release notes included into CHANGES file. For known problems and more information
about bug fixes, please see the online ModSecurity Jira. Please report any bug
Community support is available on the
mod-security-users/lists.sourceforge.net mailing list. You must
subscribe first (by clicking here)
in order to post. The list archives are available as