From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/
Date: Wed, 7 Oct 2020 18:58:23 +0000 (UTC) [thread overview]
Message-ID: <1602097097.df0f81ee11f036df6b46f5b6d968295335ef532d.sam@gentoo> (raw)
commit: df0f81ee11f036df6b46f5b6d968295335ef532d
Author: Tomáš Mózes <hydrapolic <AT> gmail <DOT> com>
AuthorDate: Thu Oct 1 18:39:07 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Oct 7 18:58:17 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=df0f81ee
www-apache/modsecurity-crs: bump to 3.3.0
Closes: https://bugs.gentoo.org/706148
Bug: https://bugs.gentoo.org/719250
Signed-off-by: Tomáš Mózes <hydrapolic <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/17741
Signed-off-by: Sam James <sam <AT> gentoo.org>
www-apache/modsecurity-crs/Manifest | 1 +
www-apache/modsecurity-crs/metadata.xml | 2 +-
.../modsecurity-crs/modsecurity-crs-3.3.0.ebuild | 33 ++++++++++++++++++++++
3 files changed, 35 insertions(+), 1 deletion(-)
diff --git a/www-apache/modsecurity-crs/Manifest b/www-apache/modsecurity-crs/Manifest
index 869ccd079b4..06878bd7d39 100644
--- a/www-apache/modsecurity-crs/Manifest
+++ b/www-apache/modsecurity-crs/Manifest
@@ -1,2 +1,3 @@
DIST modsecurity-crs-3.0.2.tar.gz 156751 BLAKE2B 111a330b6081d476899be321e15d74379b3c3db23f429a4a4ef1900c87e4b29229638acf3bb367745446ef97ccba4679db91b0d84bae93f2c127bbb6e8031851 SHA512 ae8fe9a0f00a57708c8680cb76882214e4f5ff647e13087aaf1bfc7382cefb38d2f3a88eb1f210031b553f56d3e44c12dbdc68f8b0d09fb4a9e2f15a70d885aa
DIST modsecurity-crs-3.1.0.tar.gz 250617 BLAKE2B 6081d09e90f3c18435e046264ff8c0b700fd0c8c2b6377f44517fce3ad74dcf1d6a8cf7eaf055b85040b21196b603bcb762f5a7ed237d14b6a05f1febd623cda SHA512 d613d2af8248424ac5d4d006a9f221b07c714fb47f84e6ec237b1389379b50dce984f51121cc22b69d148910169b5257b11558656640bc8349d0b09d9e70bb11
+DIST modsecurity-crs-3.3.0.tar.gz 290379 BLAKE2B 557a41e937564698809ecca40d4e76e5c1d3617b62189b7ca230ac7533cba14fdf619bef81c1e40a996dd260d2eb52c27563437dd795c2412bf38715f026f300 SHA512 12043aae12b5e01455e229136411e1fdef3a14318aff191d190b567463b63efb72630a695449b56f1d654ed1cfc0b4eb452a64502c35337d37cce920d5fa4ea4
diff --git a/www-apache/modsecurity-crs/metadata.xml b/www-apache/modsecurity-crs/metadata.xml
index 3947bbf17be..64361f081f7 100644
--- a/www-apache/modsecurity-crs/metadata.xml
+++ b/www-apache/modsecurity-crs/metadata.xml
@@ -3,6 +3,6 @@
<pkgmetadata>
<!--maintainer-needed-->
<upstream>
- <remote-id type="github">SpiderLabs/owasp-modsecurity-crs</remote-id>
+ <remote-id type="github">coreruleset/coreruleset</remote-id>
</upstream>
</pkgmetadata>
diff --git a/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild b/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild
new file mode 100644
index 00000000000..985caa85072
--- /dev/null
+++ b/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild
@@ -0,0 +1,33 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI="7"
+
+DESCRIPTION="OWASP ModSecurity Core Rule Set"
+HOMEPAGE="https://coreruleset.org/"
+SRC_URI="https://github.com/coreruleset/coreruleset/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND=">=www-apache/mod_security-2.9.1"
+
+S="${WORKDIR}/coreruleset-${PV}"
+
+src_install() {
+ insinto "/usr/share/${PN}"
+ doins -r rules
+
+ dodoc CHANGES CONTRIBUTORS.md KNOWN_BUGS README.md crs-setup.conf.example
+
+ # 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"
+}
+
+pkg_postinst() {
+ einfo "The CRS configuration file has been installed to:"
+ einfo " ${ROOT}/etc/apache2/modules.d/80_mod_security-crs.conf"
+}
next reply other threads:[~2020-10-07 18:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 18:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 18:10 [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/ Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-10-26 6:02 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-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
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=1602097097.df0f81ee11f036df6b46f5b6d968295335ef532d.sam@gentoo \
--to=sam@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