Re: [Mod-security-developers] compile modsecurity --with-curl=no

[Felipe C. <FC...@tr...>]

Hi Christian,

Mlogc depends on curl to submit the logs to the target host. Did you managed to compile the mlogc while using --with-curl=no ?

Br.,
Felipe "Zimmerle" Costa
Security Researcher, SpiderLabs

Trustwave | SMART SECURITY ON DEMAND
www.trustwave.com<http://www.trustwave.com/>


From: "chr...@go...<mailto:chr...@go...>" <chr...@go...<mailto:chr...@go...>>
Reply-To: "mod...@li...<mailto:mod...@li...>" <mod...@li...<mailto:mod...@li...>>
Date: Monday, November 2, 2015 at 8:34 AM
To: "mod...@li...<mailto:mod...@li...>" <mod...@li...<mailto:mod...@li...>>
Subject: [Mod-security-developers] compile modsecurity --with-curl=no

Dear devolopers,

I searched the mailing lists and google for my question, but didn't find anything. Hopefully this is the right place to ask my question.

We use a modified apache httpd (2.2.29) with modsecurity 2.9.0 on RHEL 6.6 (64bit). On graceful restarts of the httpd the number semaphore arrays start to increase till they reach the limit of 128 when mlogc is enabled. The support of the modified httpd suggested to compile modsecurity "--with-curl=no". The number of semaphore arrays is not encreasing anymore.

Now my question is which impact will this option have on modsecurity/mlogc?

Thanks in advance,
Christian
____________________________________________________________________________________________________
Gesellschaft: Gothaer Systems GmbH
Sitz: Gothaer Allee 1, 50969 Köln (Hausanschrift)
Aufsichtsrat: Dr. Mathias Bühring-Uhle (Vorsitzender)
Geschäftsführung: Dr. Hans Volkmar Weckesser (Vorsitzender), Hans Berg
Rechtsform: Gesellschaft mit beschränkter Haftung
Registergericht: Amtsgericht Köln, HRB 25642
USt.-IdNr. DE811850000

________________________________

This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.