|
From: Derek & V. <the...@gm...> - 2014-04-03 12:31:26
|
Felipe,
Using the cross test code I no longer get that error message. I get
others but those may be related to my cross compile build environment.
Cheers
Derek
On 04/02/2014 09:25 AM, Felipe Costa wrote:
> Hi Derek,
>
> The problem probably happens due to the lack of the inclusion of this
> header: sys/utsname.h
>
> This header is just used on Linux, so prior to the inclusion I am
> doing a verification to see if the target machine is a Linux or not,
> for that, I was using the following condition:
> #ifdef __gnu_linux__
> ...
> #endif
>
> Probably your cross compiler was not setting this macro. I have
> changed it to:
> #if (defined(__linux__) || defined(__gnu_linux__))
> ...
> #endif
>
> This sound more `fail proof`. The modification is available at the
> branch: cross_test
>
> https://github.com/SpiderLabs/ModSecurity/tree/cross_test
>
> Can you check if it is working fine?
>
> If not, can you send me the list of pre-defined macros of your
> compiler? Easy to get the list:
>
> touch /tmp/somefile.c
> cpp -dM /tmp/somefile.c
>
> Change cpp for your C++ cross compiler alternative.
>
> Br.,
> *Felipe "Zimmerle" Costa*
> Security Researcher, SpiderLabs
>
> *Trustwave* | SMART SECURITY ON DEMAND
> www.trustwave.com <http://www.trustwave.com/>
>
>
>
> On Apr 2, 2014, at 9:32 AM, Derek Werthmuller <the...@gm...
> <mailto:the...@gm...>>
> wrote:
>
>> I've given up on nginx and modsecurity. Not because I don't think it
>> works but because nginx is not a good forward proxy. I'm now working
>> to get the cross compile to work for the modsecurity and apache.
>>
>> I'm using the latest rc 2.8.0 and am getting a compile error, not
>> sure if its due to tool chain issues or an issue with the code.
>> I've downloaded the code from git.
>> https://github.com/SpiderLabs/ModSecurity/releases/download/v2.8.0-rc1/
>>
>> msc_status_engine.c: In function 'msc_status_engine_machine_name':
>> msc_status_engine.c:137:26: error: storage size of 'u' isn't known
>> static struct utsname u;
>> ^
>> make[5]: *** [mod_security2_la-msc_status_engine.lo] Error 1
>>
>> Thanks
>> Derek
>>
>>
>> On Sat, Feb 22, 2014 at 8:51 PM, Derek Werthmuller
>> <the...@gm... <mailto:the...@gm...>> wrote:
>>
>> Working on setting modsecurity with nginx in a forward proxy
>> configuration on a raspberry pi.
>> I've got modsecurity building ok it seems. Have nginx building
>> with out modsecurity ok. But nginx will not link properly with
>> modsecurity.
>>
>> nginx 1.5.10
>> apache 2.2.26
>> modsecurity 2.7.7
>>
>> Getting lots of messages like
>> modsecurity-apache_2.7.7/nginx/modsecurity/apr_bucket_nginx.c:67:
>> undefined reference to `apr_bucket_free'
>>
>> nginx doesn't have a with-apr section in its configure script, so
>> I figure this is referring to modsecurity's use of apr.
>>
>> Also seems to be having trouble finding the libxml2 libraries.
>> Bunch of these messages too.
>> ../modsecurity-apache_2.7.7/nginx/modsecurity/../../standalone/.libs/standalone.a(standalone_la-msc_crypt.o):
>> In function `hash_response_body_links':
>> msc_crypt.c:(.text+0x17ec): undefined reference to
>> `xmlXPathNewContext'
>> msc_crypt.c:(.text+0x184c): undefined reference to
>> `xmlXPathEvalExpression'
>>
>> Any guidance on getting this compiled correctly?
>> Cheers
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> mod-security-developers mailing list
>> mod...@li...
>> <mailto:mod...@li...>
>> https://lists.sourceforge.net/lists/listinfo/mod-security-developers
>> ModSecurity Services from Trustwave's SpiderLabs:
>> https://www.trustwave.com/spiderLabs.php
>
>
> ------------------------------------------------------------------------
>
> 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.
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> mod-security-developers mailing list
> mod...@li...
> https://lists.sourceforge.net/lists/listinfo/mod-security-developers
> ModSecurity Services from Trustwave's SpiderLabs:
> https://www.trustwave.com/spiderLabs.php
|
