Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain managedit.ie designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A633CF2D7C7BED41B41F1E64F25507B8069D29BD16@MAILR001.mail.lan>
References: <CALjhHG_wYvJn-Z+x9fJUi+dgmZ+Ha9BD54N5VwhneJM4sg1xBQ@mail.gmail.com>
 <5FB5CFDA-6FE8-4C20-A9B9-7844ED96659B@nopiracy.de> <CAEZPtU7jtQTDNpUovxxnDdRunjH9BOdX=WbS8JcGz+5Wkz8ocw@mail.gmail.com>
 <4F2A9378.70803@thelounge.net> <4F2AC9CA.2070308@sugarcrm.com>
 <4F2B2ED8.4050900@jimdo.com> <72878E6C-4C17-4D94-9F73-1446769247E1@nopiracy.de>
 <CAEZPtU5CP3GqUnKsxx51-ieHAdGh=ySvZCWhhAwa0kwuNG6Bhg@mail.gmail.com>
 <A33C7716-F355-455E-863D-5458205C3208@nopiracy.de> <4F2CEA7E.9010906@sugarcrm.com>
 <A633CF2D7C7BED41B41F1E64F25507B8069D29BD16@MAILR001.mail.lan>
Date: Sat, 4 Feb 2012 17:34:44 +0000
Message-ID: <CAGSj+Qs5GTp8RGc2HKeJm7N7CexCg21wDEJ8ONEKEKVafoiYuA@mail.gmail.com>
To: John Crenshaw <johncrenshaw@priacta.com>
Cc: PHP internals <internals@lists.php.net>, ondrej@sury.org, 657698@bugs.debian.org
Content-Type: multipart/alternative; boundary=e89a8f839f6181661904b826d9ac
Subject: Re: [PHP-DEV] Suhosin patch disabled by default in Debian php5 builds
From: kiall@managedit.ie (Kiall Mac Innes)

--e89a8f839f6181661904b826d9ac
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi John,

=EF=BB=BFOnd=C5=99ej (One of the Debian PHP maintainers) listed 5 or 6 reas=
ons in the
initial email in this thread.

Honestly, I can't think of a good reason for Debian or anyone else to
include 3rd party patches, whatever the patches purpose, in the default PHP
packages.

I would argue that, if people want 3rd party patches they should either:

A) Apply the patch themselves. or:
B) Petition the author and php-core to have the patch applied upstream, to
everyone's benefit.

This is the only way to ensure IMO that everyone is using "the same PHP",
or they have explicitly opted to use some 3rd party code.

Thanks,
Kiall


On Sat, Feb 4, 2012 at 5:21 PM, John Crenshaw <johncrenshaw@priacta.com>wro=
te:

> OK, All the mud slinging is getting really silly (on *both* sides).
> There's no need to denigrate others because you don't agree with them.
> There's no point in arguing about who isn't a team player or who works fo=
r
> which evil multinational corporation. Nobody is attacking anybody else by
> suggesting that Suhosin is or is not critical, and none of that really
> matters anyway.
>
> I may have missed something, but has anyone asked *why* the patch was
> disabled? I think I could make a good guess, but I haven't seen even the
> slightest hint of the actual reasons in this email chain (though I could
> easily have missed it entirely).
>
> IMO we should try to focus on:
> 1. What are the pros vs. cons of enabling the Suhosin patch by default?
> 2. Why did the Debian team opt to disable it?
> 3. Are there better solutions that should be considered and recommended?
>
> John Crenshaw
> Priacta, Inc.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--e89a8f839f6181661904b826d9ac--