Dammit Christian, putting me in the hot seat. I bow to the will of the
community in all efforts :) send the pull through (I¹m excited to see it).
I¹ve been trying to take notes to quickly codify this in the new
documentation but haven¹t had time to update this yet. Hopefully this will
help people this time around with the word paranoid :)

On 2/22/16, 3:00 PM, "Christian Folini" <christian.fol...@netnea.com>
wrote:

>Chaim,
>
>On Mon, Feb 22, 2016 at 01:06:20PM +0000, Chaim Sanders wrote:
>> already put off by the complexity of ModSecurity. Although you bring up
>> many good points in your email, I still think that based off of my
>> experiences it makes more sense to call it aggressiveness, especially
>>now
>> that we have multiple levels. Great email btw Christian.
>
>Thanks for the flowers. Took me a while to assemble it. ;)
>
>I agree with you, that paranoia may sound difficult, but I am sure
>we can get the point across, that the default is _less_
>paranoid/aggressive than it used to me thanks to exile of the
>paranoid rules into the higher and non-standard paranoia settings.
>
>Now how do we proceed? It seems I was able to convince most
>other participants in this conversation outside you. You
>are in charge, so I have no problem with you making the decision.
>But a decision we need.
>
>My pull request #1 is ready. I can submit it as is, or I do
>s/paranoia/aggressiveness/. Your call.
>
>Ahoj,
>
>Christian
>
>
>--
>Our sense of responsibility is not always as well developed
>as our sense of righteousness.
>--- Mark Burgess, Principles of Network and System Administration


________________________________

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.
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
Owasp-modsecurity-core-rule-set@lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set

Reply via email to