Please keep compatibility with modsecurity 2.6 about coreruleset HOT 6 CLOSED

User rcbarnett-zz commented on date 2012-12-19 19:32:07:

Most distribution packagers have upgraded to v2.7.x. What distro repo are you using?

from coreruleset.

User sathieu commented on date 2012-12-19 20:14:12:

I use Debian. Debian stable (squeeze) has 2.5.12, and incoming stable (wheezy) has 2.6.6 (See http://packages.debian.org/search?keywords=mod-security&searchon=names&suite=all&section=all).

I will probably write a script that remove all those new actions ("maturity" and "accuracy") and hope it is enough.

Anyway, having a too strong relation between the mod_security engine and the CRS makes upgrade sharder. We previously had to migrate to mod_sec 2.6 because of a new CRS release depending on it, and then old CRS was not working anymore with this new engine (syntax errors). As such we had to migrate all our vhosts to the newest CRS which brought a lot of new false positive. This was a lot of pain.

from coreruleset.

User choffee commented on date 2013-02-21 18:09:57:

The same is true for Ubuntu LTS

http://packages.ubuntu.com/precise-updates/libapache2-modsecurity

Looks like they will be around for a bit. Is there some way things like fixed regex's could be backported to a stable repo?

from coreruleset.

User eilandert commented on date 2013-06-16 23:03:13:

https://launchpad.net/~team-mayhem/+archive/ppa has up2date modsecurity packages, for ubuntu anyway

from coreruleset.

User rcbarnett-zz commented on date 2013-07-01 17:46:41:

Added script from sathieu to remove v2.7 actions for use with older ModSecurity installs -

https://github.com/SpiderLabs/owasp-modsecurity-crs/blob/master/util/rule-management/remove-2.7-actions.pl

from coreruleset.

User sathieu commented on date 2013-07-02 15:02:16:

Thank you.

from coreruleset.