Re: [mod-security-users] ModSecurity v3 and Atomicorp Rules

[Phil D. <ux...@sp...>]

Actually it appears to be complaining about the configuration key SecHttpBlKey ?

----- On 13 Jan, 2017, at 12:48, Christian Folini chr...@ne... wrote:

> On Fri, Jan 13, 2017 at 12:29:53PM +0000, Phil Daws wrote:
>> When I try and enable Honeypot I get: nginx: [emerg] "server_name"
>> directive Rules error. File:
>> /etc/nginx/modsecurity.d/owasp-modsecurity-crs/crs-setup.conf. Line:
>> 532. Column: 1. invalid character S in /etc/nginx/nginx.conf:103
>> nginx: configuration file /etc/nginx/nginx.conf test failed
>> 
>> Line 532 is where the API key is defined:
>> 
>> SecHttpBlKey rtszy*******
> 
> Too bad. Maybe you can apply for a new API key without an "S" in it.
> 
> @Felipe, can you help?
> 
> Christian
> 
> 
>> 
>> SecAction "id:900500,\ phase:1,\ nolog,\ pass,\ t:none,\
>> setvar:tx.block_search_ip=1,\ setvar:tx.block_suspicious_ip=1,\
>> setvar:tx.block_harvester_ip=1,\ setvar:tx.block_spammer_ip=1"
>> 
>> Am sure others are not having these problems :(
>> 
>> 
>> ----- On 13 Jan, 2017, at 11:53, Christian Folini
>> chr...@ne... wrote:
>> 
>> > Hello,
>> > 
>> > On Fri, Jan 13, 2017 at 11:37:48AM +0000, Phil Daws wrote:
>> >> Once I fixed that line it then throws up another error :(
>> > 
>> > Too bad.
>> > 
>> >> Seems like at the moment will be unable to use the Atomicorp rules
>> >> :(
>> > 
>> > Does that mean you are now considering CRS3?
>> > 
>> > Ahoj,
>> > 
>> > Christian
>> > 
>> > 
>> > -- Neither a man nor a crowd nor a nation can be trusted to act
>> > humanely or to think sanely under the influence of a great fear.  --
>> > Bertrand Russell
> 
> --
> https://www.feistyduck.com/training/modsecurity-training-course
> mailto:chr...@ne...
> twitter: @ChrFolini