Same here, tho Debian Squeeze. We even backported a more recent version from
wheezy a while back, but it's too much for us to keep up with constantly doing
that on our own.
Thanks,
Brian
Sent from my mobile device.
----- Reply message -----
From: "Gjorgji Zarezankov" <gjorg...@paymentus.com>
Date: Fri, Aug 10, 2012 08:49
Subject: [mod-security-users] Using the latest ModSecurity Versions
To: "Ryan Barnett" <rbarn...@trustwave.com>,
<mod-security-us...@lists.sourceforge.net>,
<owasp-modsecurity-core-rule-set@lists.owasp.org>
In our case its exactly that: We use SUSE SELS 11 SP and latest version
available from there repositories is 2.5.6.
*From:* Ryan Barnett [mailto:rbarn...@trustwave.com]
*Sent:* Friday, August 10, 2012 9:38 AM
*To:* mod-security-us...@lists.sourceforge.net;
owasp-modsecurity-core-rule-set@lists.owasp.org
*Subject:* [mod-security-users] Using the latest ModSecurity Versions
Question for the lists – if you are not running the latest version of
ModSecurity (v.2.6.7), what are the reasons why you have not upgraded?
I ask this question because we are constantly adding new features to
ModSecurity that can then be leveraged with the OWASP ModSecurity CRS. For
example, we have added some new actions:
- ver – which will hold the rule package data. Example -
"id:'959901',ver:'OWASP_CRS/2.2.5',…"
- maturity – which will give the user a better idea of how well tested
the rule is. Example - "id:'959901',ver:'OWASP_CRS/2.2.5',maturity:'9'…"
- accuracy – wh
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
Owasp-modsecurity-core-rule-set@lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
