From: Jeroen Roovers <jer@gentoo.org>
To: Sebastian Pipping <sping@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>,
"pr@gentoo.org" <pr@gentoo.org>
Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Mon, 4 Jan 2016 06:11:01 +0100 [thread overview]
Message-ID: <20160104061101.5f9686bc@wim.fritz.box> (raw)
In-Reply-To: <5689BC34.5000006@gentoo.org>
On Mon, 4 Jan 2016 01:26:28 +0100
Sebastian Pipping <sping@gentoo.org> wrote:
> Hi!
>
>
> Better late then never. Posting 72 hours from now the earliest as
> advised by GLEP 42. Feedback welcome as usual.
>
>
> ===========================================================
> Title: Apache "-D PHP5" needs update to "-D PHP"
> Author: Sebastian Pipping <sping@gentoo.org>
> Content-Type: text/plain
> Posted: 2016-01-04
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: app-eselect/eselect-php[apache2]
>
> With >=app-eselect/eselect-php-0.8.1, to enable PHP support
> for Apache 2.x file /etc/conf.d/apache2 no longer
... 2.x, the file ...
> needs to read
=> should no longer read
>
> APACHE2_OPTS="......... -D PHP5"
>
> but
>
> APACHE2_OPTS="......... -D PHP"
>
> , i.e. without "5" at the end. This change is related to
instead, i.e. ...
> unification in context of the advent of PHP 7.x.
Vague.
> With that change, guard "<IfDefine PHP>" in file
> /etc/apache2/modules.d/70_mod_php.conf
> has a chance to actually pull in PHP support.
We'd like to be pretty certain that PHP application server is going to
"actually" do that.
> Without updating APACHE2_OPTS, websites could end up serving
> PHP code (include configuration files with passwords)
> unprocessed to website visitors!
That would mean there is an additional (local) security problem.
jer
next prev parent reply other threads:[~2016-01-04 5:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 0:26 [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP" Sebastian Pipping
2016-01-04 5:11 ` Jeroen Roovers [this message]
2016-01-04 16:53 ` Michael Orlitzky
2016-01-04 8:41 ` [gentoo-dev] " Kristian Fiskerstrand
2016-01-04 12:11 ` Rich Freeman
2016-01-04 13:30 ` Kristian Fiskerstrand
2016-01-04 14:20 ` Kristian Fiskerstrand
2016-01-04 14:51 ` Rich Freeman
2016-01-04 14:45 ` Peter Stuge
2016-01-04 15:08 ` Brian Evans
2016-01-04 10:45 ` [gentoo-dev] " Lars Wendler
2016-01-04 13:40 ` Michał Górny
2016-01-04 15:20 ` Michael Orlitzky
2016-01-04 15:42 ` Peter Stuge
2016-01-04 15:53 ` Michael Orlitzky
2016-01-04 16:11 ` Peter Stuge
2016-01-04 16:43 ` Michael Orlitzky
2016-01-04 17:21 ` Brian Evans
2016-01-04 17:49 ` Rich Freeman
2016-01-04 19:27 ` Michael Orlitzky
2016-01-05 19:35 ` Michael Orlitzky
2016-01-06 19:36 ` Sebastian Pipping
2016-01-06 19:53 ` Michael Orlitzky
2016-01-08 0:52 ` Marc Schiffbauer
2016-01-09 17:39 ` Michael Orlitzky
2016-01-06 19:39 ` Sebastian Pipping
2016-01-04 15:11 ` Hanno Böck
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=20160104061101.5f9686bc@wim.fritz.box \
--to=jer@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
--cc=sping@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