|Summary:||www/apache24: Add mod_security v3 support|
|Product:||Ports & Packages||Reporter:||epopen|
|Component:||Individual Port(s)||Assignee:||freebsd-apache mailing list <apache>|
|Status:||Closed Feedback Timeout|
|Severity:||Affects Some People||CC:||brnrd, joneum, marius.halden, me|
Description epopen 2018-05-02 05:51:47 UTC
Hi All. The bug reference with bug #220353 I running Apache from prots www/apache24. Found next version of ModSecurity in www/mod_security3 before. And known it require connector to work with Apache as below. https://github.com/SpiderLabs/ModSecurity-apache I tried make it but failure. So I have no idea let it work. Can help ports official support add either merge into apache like www/nginx or individual ports? Thank a lot.
Comment 1 Bernard Spil 2018-05-02 08:55:40 UTC
Hi Marius, The www/mod_security3 port is not correctly named. It implies that it is a module (to apache) but in reality it is a stand-alone solution that needs a connector (in nginx or apache) to operate. I'd like to rename www/mod_security3 to security/modsecurity3 which is more in line with upstream naming, and add a www/mod_security3 port which is actually the Apache connector libexec/apache24/mod_security.so which establishes the connection. (from https://github.com/SpiderLabs/ModSecurity-apache) Can you please provide a patch for the renaming? Cheers, Bernard (with hat apache@)
Comment 2 Marius Halden 2018-05-02 10:43:46 UTC
Created attachment 192989 [details] modsecurity-rename.patch Hi, You can try the attached patch, it also changes the dependency for nginx and nginx-devel.
Comment 3 Jochen Neumeister 2019-02-15 19:25:49 UTC
is this still relevant?