logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in RSS X


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
Post new topic   Forum Index -> Third-party Modules View previous topic :: View next topic
Reply to topic   Topic: ModSecurity 2.6.4 available
Author
Steffen
Moderator


Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU

PostPosted: Fri 09 Mar '12 21:54    Post subject: ModSecurity 2.6.4 available Reply with quote

ModSecurity 2.6.4 is now available, inlcludes Mlogc.

The stability of this release must be good and it includes some bug fixes. Mlogc old 100% cpu consume bug appears to be fixed now.
A new bug related to ctl:updateTargetByID was fixed, making apache memory grow.
The last release has a bug when reloading data from session and user collections, users running rules that use those collection must upgrade to this version.

Steffen


Changes:

09 Mar 2012 with 2.6.4
--------------------------
* Fixed Mlogc 100% CPU consume (Thanks Klaubert Herr and Ebrahim Khalilzadeh).
* Fixed ModSecurity cannot load session and user sdbm data.
* Fixed updateTargetById was creating rule unparsed content making apache memory grow.
* Code cleanup.
* Fixed @rsub adding garbage data into stream variables.
* Fixed regex for section A into mlogc-batch-load.pl (Thanks Ebrahim Khalilzadeh).
* Fixed logdata cuts message without closing it with final chars.
* Added sanitizeMatchedBytes support to verifyCPF, verifyCC and verifySSN.
Back to top
aturbide



Joined: 14 Mar 2012
Posts: 1
Location: Canada,Whitby

PostPosted: Wed 14 Mar '12 21:18    Post subject: Reply with quote

I believe a new bug was introduced with this version. If you use persistent collections (use the initcol cmd to setup ip and global collections), you might see tons of warnings with the term "collection_retrieve_ex: Retrieving collection " in your logs. This is due to an incorrect loglevel set for the collection routine. It won't affect the operations, just fill your logs fast.
Back to top
Steffen
Moderator


Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU

PostPosted: Wed 14 Mar '12 21:38    Post subject: Reply with quote

Thanks for posting.

A fix for release is on the way, planned next week. Breno wants also fix some other little things. Because it won't effect operation I shall not distribute a version with only this fix.

Steffen
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA

PostPosted: Wed 14 Mar '12 22:46    Post subject: Reply with quote

Hopefully Breno is making it LUA 5.2 compatible as well. I suppose I could email him myself with that one.
Back to top
maskego



Joined: 16 Apr 2010
Posts: 238

PostPosted: Thu 15 Mar '12 9:44    Post subject: Reply with quote

What is the mod_security_crs rules to cause this issue?
And,how to fix it?

I find that error messages at logs.It fills the log fast indeed.
Back to top


Reply to topic   Topic: ModSecurity 2.6.4 available View previous topic :: View next topic
Post new topic   Forum Index -> Third-party Modules