From owner-freebsd-stable@freebsd.org Tue Jan 22 18:54:48 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4C9414AB761 for ; Tue, 22 Jan 2019 18:54:48 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from v1.leiden.byshenk.net (v1.leiden.byshenk.net [37.97.209.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77C2E6A1D3 for ; Tue, 22 Jan 2019 18:54:47 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: by v1.leiden.byshenk.net (Postfix, from userid 1002) id 0DBC175934; Tue, 22 Jan 2019 19:54:39 +0100 (CET) Date: Tue, 22 Jan 2019 19:54:39 +0100 From: Gregory Byshenk To: "freebsd-stable@freebsd.org" , SoftwareInforJam Subject: Re: Issue with mod_security3 Message-ID: <20190122185438.GC85865@v1.leiden.byshenk.net> References: <5c4744cd.1c69fb81.7b84f.5450@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5c4744cd.1c69fb81.7b84f.5450@mx.google.com> User-Agent: Mutt/1.11.1 (2018-12-01) X-Rspamd-Queue-Id: 77C2E6A1D3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.65 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.28)[-0.277,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.39)[0.392,0]; NEURAL_HAM_LONG(-0.38)[-0.383,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[byshenk.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[v2.leiden.byshenk.net,v1.leiden.byshenk.net]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[freebsd@byshenk.net,byshenknet@byshenk.net]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20857, ipnet:37.97.128.0/17, country:NL]; FROM_NEQ_ENVFROM(0.00)[freebsd@byshenk.net,byshenknet@byshenk.net]; IP_SCORE(-0.28)[asn: 20857(-1.40), country: NL(0.02)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2019 18:54:48 -0000 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