public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/
Date: Sat, 20 Jul 2024 06:42:50 +0000 (UTC)	[thread overview]
Message-ID: <1721457761.6c4d4c78d2965670dc4b3f4c3b174c96b929a968.juippis@gentoo> (raw)

commit:     6c4d4c78d2965670dc4b3f4c3b174c96b929a968
Author:     Tomáš Mózes <hydrapolic <AT> gmail <DOT> com>
AuthorDate: Wed Jun 26 17:18:54 2024 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sat Jul 20 06:42:41 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6c4d4c78

www-apache/modsecurity-crs: add 4.4.0

Signed-off-by: Tomáš Mózes <hydrapolic <AT> gmail.com>
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 www-apache/modsecurity-crs/Manifest                |  1 +
 .../modsecurity-crs/modsecurity-crs-4.4.0.ebuild   | 45 ++++++++++++++++++++++
 2 files changed, 46 insertions(+)

diff --git a/www-apache/modsecurity-crs/Manifest b/www-apache/modsecurity-crs/Manifest
index 9235054778d5..bf38e67426cc 100644
--- a/www-apache/modsecurity-crs/Manifest
+++ b/www-apache/modsecurity-crs/Manifest
@@ -1,3 +1,4 @@
 DIST modsecurity-crs-3.3.5.tar.gz 299458 BLAKE2B b8617de77cf5168c7b95fab46eae45e2101b4ec7a537d8d471b9b1b27a856b1d370a9de43ee262c07dc9371b3ff79cd86b7328b171fde003da9110897206e91e SHA512 001f9afe25f479dd988aaec1a4a2c0197b2d27e00d2cd10b70892e4889b399259cd0655f42a96965ae655855abdb7f9d8295c225ae17bf1e47361b70232633e5
 DIST modsecurity-crs-4.0.0.tar.gz 504720 BLAKE2B e6da0268ae9209179d1f6cefba34e097b614dd4659a4b4df2ef3e6a0b32be7be9d825beaf6d8ca1fbef0dd27217b4707090844e59eaa817111be4a6f8333e205 SHA512 c25bfd6de772815977783e78d7afd388d60bbba151762a38c7050fd5ecde6a48baa0a850028a24d42855ae4a788404ad1ee0f7a4ad2d94d53a46e261a00f7224
 DIST modsecurity-crs-4.2.0.tar.gz 511240 BLAKE2B f33d1a2bfac809e08ce5480af68b2380b19ea33f4d1409dd79d2117e451631df5b73ba2ccbc6eae2757df3b092c9439bfe79b49658d76fda1a1237f204317080 SHA512 041556b2071385c10a4b4a29ad4f926ee86f819f8b9c95f849e76b3d2724d5fc29c21a69f9eba6fd62e7f5709a109a95feca67a19d8c8d1f0410ee2987ac7a6b
+DIST modsecurity-crs-4.4.0.tar.gz 510998 BLAKE2B 770a392836fbe29b69d0aa0b487bd7798cc618d1a5923d169a04bcac52b3add6dee8d5777e97e9b3afb3776bc442fb004e02c0c27becb07df62f2fa289d70be9 SHA512 a196a922c5456a2f025f43f8c0b5e3905eed8b3586c54d7b7771c386e5226d8dc6fce2b0bc05d69b389b07d5935bf8abbfb0a524e8ef856a433e9e4aed4b448d

diff --git a/www-apache/modsecurity-crs/modsecurity-crs-4.4.0.ebuild b/www-apache/modsecurity-crs/modsecurity-crs-4.4.0.ebuild
new file mode 100644
index 000000000000..1a0a134d3046
--- /dev/null
+++ b/www-apache/modsecurity-crs/modsecurity-crs-4.4.0.ebuild
@@ -0,0 +1,45 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit optfeature
+
+MY_PV=${PV/_/-}
+
+DESCRIPTION="OWASP ModSecurity Core Rule Set"
+HOMEPAGE="https://coreruleset.org/"
+SRC_URI="https://github.com/coreruleset/coreruleset/archive/v${MY_PV}.tar.gz -> ${P}.tar.gz"
+S="${WORKDIR}/coreruleset-${MY_PV}"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="+apache2"
+
+RDEPEND="apache2? ( >=www-apache/mod_security-2.9.6 )"
+
+DOCS=( CHANGES.md CONTRIBUTORS.md crs-setup.conf.example KNOWN_BUGS.md README.md )
+
+src_install() {
+	insinto "/usr/share/${PN}"
+	doins -r plugins rules
+
+	einstalldocs
+
+	if use apache2; then
+		# I don't think it's worth pulling in apache-module.eclass just for
+		# this path...
+		insinto /etc/apache2/modules.d
+		doins "${FILESDIR}/80_mod_security-crs.conf"
+	fi
+}
+
+pkg_postinst() {
+	if use apache2; then
+		einfo "The CRS configuration file has been installed to:"
+		einfo "  ${ROOT}/etc/apache2/modules.d/80_mod_security-crs.conf"
+	fi
+
+	optfeature "apache-less installations, e.g. nginx" dev-libs/modsecurity
+}


             reply	other threads:[~2024-07-20  6:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20  6:42 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-26  6:02 [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/ Joonas Niilola
2024-10-26  6:02 Joonas Niilola
2024-10-26  3:49 Sam James
2024-10-26  3:49 Sam James
2024-10-25 11:36 Joonas Niilola
2024-10-25 11:36 Joonas Niilola
2024-07-20  6:42 Joonas Niilola
2024-04-27 13:21 Petr Vaněk
2024-04-27 13:21 Petr Vaněk
2024-04-26 17:16 Sam James
2024-04-26 17:16 Sam James
2024-03-16  9:26 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2023-10-31  0:06 Sam James
2023-10-30 23:13 Sam James
2023-10-28  7:07 Hans de Graaff
2022-12-02  6:15 John Helmert III
2022-12-02  3:38 Sam James
2022-12-02  3:34 Sam James
2022-11-21  9:22 Joonas Niilola
2022-11-21  9:22 Joonas Niilola
2021-12-24  8:02 Sam James
2021-12-22  0:45 Sam James
2021-12-22  0:44 Sam James
2021-12-21  2:05 Sam James
2020-12-29  2:00 Sam James
2020-10-09 15:23 Agostino Sarubbo
2020-10-09  8:41 Agostino Sarubbo
2020-10-07 18:58 Sam James
2019-03-04  1:35 Thomas Deutschmann
2018-10-26  0:52 Thomas Deutschmann
2018-10-20 18:01 Mikle Kolyada
2018-05-20 23:26 Aaron Bauman
2018-03-29 19:23 Michał Górny
2016-11-03 21:46 Diego Elio Pettenò
2016-08-07  9:30 Pacho Ramos

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=1721457761.6c4d4c78d2965670dc4b3f4c3b174c96b929a968.juippis@gentoo \
    --to=juippis@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox