Re: [Mod-security-developers] ModSecurity V2 as a dynamic nginx module

[Muenz, M. <m....@sp...>]

Am 10.12.2016 um 14:40 schrieb Muenz, Michael:
> Am 10.12.2016 um 14:03 schrieb Muenz, Michael:
>> Am 09.12.2016 um 12:59 schrieb Felipe Costa:
>>> Hi Michael,
>>>
>>> You may want to upgrade your libModSecurity to the most recent version, this
>>> specific issue was fixed a while ago.
>>>
>> Hi Felipe,
>>
>> were there some major changes? I did a fresh setup like in this article:
>> http://www.routerperformance.net/howtos/setup-modsecurity-3-and-nginx-in-debian-8/
>>
>> This worked with source from mid november but now I get a
>> nginx: [emerg] module
>> "/etc/nginx/modules/ngx_http_modsecurity_module.so" is not binary
>> compatible in /etc/nginx/nginx.conf:8
>>
>> Source from nginx is the some, don't know why it doesn't work now. :(
>>
>>
>
> Doooh ... forget my mail. I forgot that with N+ you have to use the same
> configure params.
> Now it works really fine!!!
>
> The only problem I still have is, that with ModSecurity Commercial
> Rules, it takes about 5 minutes to restart/reload nginx.
>
>

Sorry for spamming but I fixed this one too.
With nginx (ATM) you don't have to use SecRuleRemote in MS config, 
instead just use the variable modsecurity_rules_remote described in 
https://github.com/SpiderLabs/ModSecurity-nginx