Hi Carlos There is a known problem on ModSercurity 2.x which leads to a problem somewhat similar to what you have reported. If you are running 2.x I would recommend you to move forward to 3.0.3: - https://github.com/SpiderLabs/ModSecurity - https://github.com/SpiderLabs/ModSecurity-nginx If that is not the case, please, tell us more about your setup. Br., Z. On Mon, Apr 15, 2019 at 7:22 Pby zimmerle - Nginx Mailing List - English
Hi, Please upgrade your libModSecurity to v3.0.3: https://github.com/SpiderLabs/ModSecurity/releases/tag/v3.0.3 Br., Z. On Fri, Nov 9, 2018 at 11:14 AM alang <nginx-forum@forum.nginx.org> wrote: > Yeah I fixed this issue. It was definitely the modsecurity connector. > They > had done an update to master branch that required to use their newer > libraries. > > Posted atby zimmerle - Nginx Mailing List - English
Hi Lukas, On Sun, Jan 10, 2016 at 11:05 AM Lukas <l@ymx.ch> wrote: > I found that recommendation. Since I also read that it would not be > fully compatible with OWASP/CRS I have not given it a try. > > What is the situation regrading OWASP/CRS? > Currently there are three different versions of ModSecurity for nginx: - Version 2.9.0: That is the last released version, I thby zimmerle - Nginx Mailing List - English
Hi Lukas, You may want to use the ModSecurity's nginx_refactoring branch instead of the master branch. Here is the link to the branch: https://github.com/SpiderLabs/ModSecurity/tree/nginx_refactoring Br., Felipe Zimmerle Lead dev for ModSecurity On Sun, Jan 10, 2016 at 10:39 AM Lukas <l@ymx.ch> wrote: > Dear all > > Fascinated by nginx, I attempted to integrate it with modsecuby zimmerle - Nginx Mailing List - English
Hi, It should not be a problem. The parameter "crypto" is optional and should not affect ModSecurity behavior. Check the SecRemoteRules description on ModSecurity reference manual, at: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#secremoterules Br, Z.by zimmerle - Nginx Mailing List - English