From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/openfire/
Date: Sun, 23 Jun 2019 17:15:49 +0000 (UTC) [thread overview]
Message-ID: <1561310116.c32aef5d13c57017978860eb65c1c4f5ce88721c.mjo@gentoo> (raw)
commit: c32aef5d13c57017978860eb65c1c4f5ce88721c
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 23 17:13:53 2019 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Jun 23 17:15:16 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c32aef5d
net-im/openfire: new revision to clean up ownership handling.
The new revision (-r2) is intended to clean up some of the ownership
and group handling that led to the security issue in bug 630914. Note
that while that *particular* bug was fixed, the ebuild was still
calling "chmod" in a user-controlled directory, which is also
exploitable. The following changes hopefully eliminate all of
those problems:
* Add /opt/openfire/conf to CONFIG_PROTECT.
* Use insopts/diropts to create everything under /opt/openfire with
the correct ownership and permissions to begin with.
* Install conf/openfire.xml and conf/security.xml in src_install(),
instead of creating (and chmod'ing) them later in pkg_postinst().
* Drop pkg_postinst() entirely now that we install {openfire,security}.xml
in src_install().
Bug: https://bugs.gentoo.org/630914
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
net-im/openfire/openfire-4.2.3-r2.ebuild | 80 ++++++++++++++++++++++++++++++++
1 file changed, 80 insertions(+)
diff --git a/net-im/openfire/openfire-4.2.3-r2.ebuild b/net-im/openfire/openfire-4.2.3-r2.ebuild
new file mode 100644
index 00000000000..d504e403aba
--- /dev/null
+++ b/net-im/openfire/openfire-4.2.3-r2.ebuild
@@ -0,0 +1,80 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+inherit eutils java-pkg-2 java-ant-2 systemd
+
+MY_P=${PN}_src_${PV//./_}
+DESCRIPTION="Openfire (formerly wildfire) real time collaboration (RTC) server"
+HOMEPAGE="http://www.igniterealtime.org/projects/openfire/"
+SRC_URI="http://www.igniterealtime.org/builds/openfire/${MY_P}.tar.gz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="doc"
+
+RDEPEND=">=virtual/jre-1.7"
+DEPEND="net-im/jabber-base
+ ~dev-java/ant-contrib-1.0_beta2
+ >=virtual/jdk-1.7"
+
+S=${WORKDIR}/${PN}_src
+
+pkg_setup() {
+ java-pkg-2_pkg_setup
+}
+
+src_compile() {
+ # Jikes doesn't support -source 1.5
+ java-pkg_filter-compiler jikes
+
+ ANT_TASKS="ant-contrib"
+ eant -f build/build.xml openfire plugins $(use_doc)
+
+ # delete nativeAuth prebuilt libs:
+ # uses outdated unmaintained libshaj, does not support amd64
+ rm -rfv target/openfire/resources/nativeAuth || die
+}
+
+src_install() {
+ #Protect ssl key on upgrade
+ dodir /etc/env.d/
+ echo 'CONFIG_PROTECT="/opt/openfire/resources/security/"' > "${D}"/etc/env.d/98openfire
+ echo 'CONFIG_PROTECT="/opt/openfire/conf/"' > "${D}"/etc/env.d/98openfire
+
+ newinitd "${FILESDIR}"/openfire-initd openfire
+ newconfd "${FILESDIR}"/openfire-confd openfire
+ systemd_dounit "${FILESDIR}"/${PN}.service
+
+ diropts --owner=jabber --group=jabber
+ insopts --owner=jabber --group=jabber
+ dodir /opt/openfire
+
+ dodir /opt/openfire/logs
+ keepdir /opt/openfire/logs
+
+ dodir /opt/openfire/lib
+ insinto /opt/openfire/lib
+ doins target/openfire/lib/*
+
+ dodir /opt/openfire/plugins
+ insinto /opt/openfire/plugins
+ doins -r target/openfire/plugins/*
+
+ dodir /opt/openfire/resources
+ insinto /opt/openfire/resources
+ doins -r target/openfire/resources/*
+
+ if use doc; then
+ dohtml -r documentation/docs/*
+ fi
+ dodoc documentation/dist/*
+
+ dodir /opt/openfire/conf
+ insinto /opt/openfire/conf
+ insopts --mode=0600 --owner=jabber --group=jabber
+ newins target/openfire/conf/openfire.xml openfire.xml
+ newins target/openfire/conf/security.xml security.xml
+}
next reply other threads:[~2019-06-23 17:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 17:15 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-23 17:25 [gentoo-commits] repo/gentoo:master commit in: net-im/openfire/ Michael Orlitzky
2019-02-16 9:45 Pacho Ramos
2019-02-15 18:40 Mikle Kolyada
2019-02-15 18:40 Mikle Kolyada
2019-02-15 0:18 Thomas Deutschmann
2019-01-13 21:36 Sergei Trofimovich
2018-09-22 17:29 Sergei Trofimovich
2018-03-23 20:48 Sergei Trofimovich
2018-02-19 8:02 Sergei Trofimovich
2017-06-30 21:05 Sergei Trofimovich
2017-06-30 21:01 Sergei Trofimovich
2017-05-04 22:28 Sergei Trofimovich
2017-02-25 9:33 Sergei Trofimovich
2017-02-19 10:59 Sergei Trofimovich
2017-01-01 7:21 Sergei Trofimovich
2016-12-30 10:27 Sergei Trofimovich
2016-12-29 10:45 Agostino Sarubbo
2016-12-24 9:24 Aaron Bauman
2016-12-21 21:44 Sergei Trofimovich
2016-12-01 22:44 Sergei Trofimovich
2016-08-26 15:45 Sergei Trofimovich
2016-07-29 7:22 Sergei Trofimovich
2016-07-28 15:23 Agostino Sarubbo
2016-07-09 17:46 Agostino Sarubbo
2016-06-19 13:53 Sergei Trofimovich
2016-03-22 8:50 Sergei Trofimovich
2016-02-06 10:36 Sergei Trofimovich
2015-11-18 21:07 Sergei Trofimovich
2015-11-01 13:27 Mikle Kolyada
2015-10-27 12:18 Agostino Sarubbo
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=1561310116.c32aef5d13c57017978860eb65c1c4f5ce88721c.mjo@gentoo \
--to=mjo@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