Date: Tue, 22 Jan 2019 19:54:39 +0100 From: Gregory Byshenk <freebsd@byshenk.net> To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, SoftwareInforJam <softwareinforjam@gmail.com> Subject: Re: Issue with mod_security3 Message-ID: <20190122185438.GC85865@v1.leiden.byshenk.net> In-Reply-To: <5c4744cd.1c69fb81.7b84f.5450@mx.google.com> References: <5c4744cd.1c69fb81.7b84f.5450@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 22, 2019 at 11:29:01AM -0500, SoftwareInforJam wrote: > I am have a queer problem with the port mod_security3. I > actually want to set it up to work with NGINX. The port > /usr/ports/www/mod_security3 exists but when I do a > # pkg install mod_security3 > I get > ???pkg: No packages available to install matching 'mod_security3' > have been found in the repositories??? > > When I do a pkg search ???mod_security*??? only > ap24-mod_security-2.9.2_3 Intrusion detection and prevention > engine. So only version 2.9 shows up. Not sure why this is > happening. Can anyone shed some light on this please? I'm no expert on mod_security, but my guess, based on reading https://www.linuxjournal.com/content/modsecurity-and-nginx, is that previous (to v3) versions of mod_security worked _only_ with apache. And it seems likely that the port has not yet been updated to the newest v3. Also based on the article, it seems that getting even mod_security v3 to work with nginx is slightly complicated, as building it depends on the specific version of nginx that is installed. -- gregory byshenk - gbyshenk@byshenk.net - Leiden, NL
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190122185438.GC85865>