All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Herve Codina <herve.codina@bootlin.com>
Cc: Tom Marcuzzi <tom.marcuzzi@orolia.com>,
	Matthew Weber <matthew.weber@collins.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/modsecurity2: new package
Date: Fri, 17 Dec 2021 21:47:40 +0100	[thread overview]
Message-ID: <20211217214740.2eb6c14f@windsurf> (raw)
In-Reply-To: <20211018132532.814742-1-herve.codina@bootlin.com>

Hello,

On Mon, 18 Oct 2021 15:25:31 +0200
Herve Codina <herve.codina@bootlin.com> wrote:

> The modsecurity2 package provides an Apache module implementing
> a web application firewall (WAF) module.
> 
> Based on initial work from Tom Marcuzzi <tom.marcuzzi@orolia.com>
> and Nicolas Carrier <nicolas.carrier@orolia.com>
> 
> modsecurity2 will be superseeded sooner or later by modsecurity v3
> ie. libmodsecurity [1] and its Apache connector [2]. libmodsecurity
> is already supported in Buildroot with its Nginx connector.
> According to the Apache connector web page and the discussion [3],
> the Apache connector is not ready for production use.
> 
>   [1] https://github.com/SpiderLabs/ModSecurity
>   [2] https://github.com/SpiderLabs/ModSecurity-apache
>   [3] https://github.com/SpiderLabs/ModSecurity-apache/issues/80
> 
> The best we can do now is to still use modsecurity2 (v2.9.x) for
> Apache:
>   https://github.com/SpiderLabs/ModSecurity/tree/v2/master
> 
> Signed-off-by: Herve Codina <herve.codina@bootlin.com>

Thanks, I've applied after:

 * Adding a bunch of additional --without-<something> to disable
   optional dependencies that are not handled

 * Adding a dependency on pcre, which even if it is already guaranteed
   to be there from Apache, is used directly by modsecurity2, so it
   makes sense to express this dependency.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-17 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 13:25 [Buildroot] [PATCH 1/1] package/modsecurity2: new package Herve Codina
2021-12-17 20:47 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-21 17:30 Tom Marcuzzi
2019-11-21 20:14 ` Matthew Weber
2019-11-22 10:57   ` Tom Marcuzzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211217214740.2eb6c14f@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=herve.codina@bootlin.com \
    --cc=matthew.weber@collins.com \
    --cc=tom.marcuzzi@orolia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.