FAQ

On Tue, Aug 16, 2011 at 7:47 PM, Philip Olson wrote:
On Aug 16, 2011, at 9:11 AM, Christopher Jones wrote:


On 8/16/11 8:40 AM, Ferenc Kovacs wrote:
On Tue, Aug 16, 2011 at 5:34 PM, Christopher Jones
wrote:

On 8/16/11 4:30 AM, Hannes Magnusson wrote:

What are you doing?
Did I miss some discussion on this?
And another question: is Suhosin even maintained anymore?
https://twitter.com/#!/i0n1c/statuses/59373164915994624
Four months and waiting since that promise.  And 15 months since the last release.
We only document core and PECL extensions, and Suhosin is neither.
It's a little tricky though because it's a default extension with
several Linux distributions, so I'm not sure if an exception should
be made. Our ultimate goal is to help users find information.

But according to precedent and our current procedures, this commit
should not have been made. I recommend disabling it from manual.xml.in
for now, until the situation becomes known. Internals and the Suhosin
authors should decide if Suhosin will become an official PHP extension
(PECL or otherwise), as it's not something the PHP documentation team
should decide.

Regards,
Philip
this is somehow related: http://marc.info/?l=pecl-dev&m=128041932812250&w=2

Stefan also mentioned that he won't continue the development of
bytekit in it's current form, and if I remember correctly Pierre
suggested that if the package is abandoned by the original developer,
a new developer could take it over and bring it to pecl.
for suhosin, having a decent documentation is much needed, and as you
also mentioned, it's really "popular", albeit the Gentoo dropped the
suhosin patch recently, as the it doesn't apply cleanly anymore.
for the long term, I would like to see that we leave the past behind,
and the useful features should be incorporated in the core, this way
removing the need for suhosin in it's current form.

--
Ferenc Kovács
@Tyr43l - http://tyrael.hu

Search Discussions

  • Pierre Joye at Aug 16, 2011 at 6:12 pm

    On Tue, Aug 16, 2011 at 8:06 PM, Ferenc Kovacs wrote:

    Stefan also mentioned that he won't continue the development of
    bytekit in it's current form, and if I remember correctly Pierre
    suggested that if the package is abandoned by the original developer,
    a new developer could take it over and bring it to pecl.
    for suhosin, having a decent documentation is much needed, and as you
    also mentioned, it's really "popular", albeit the Gentoo dropped the
    suhosin patch recently, as the it doesn't apply cleanly anymore.
    for the long term, I would like to see that we leave the past behind,
    and the useful features should be incorporated in the core, this way
    removing the need for suhosin in it's current form.
    As of now there is almost zero reason to actually use it. Most were
    arguing about blowfish or session safety (entropy src) which is now
    fully supported in core and even in a better form than in the
    extension. I'm still waiting for a list of the feature/addition we
    should introduce in core.

    I'm totally against to document suhosin in www.php.net or any related
    sites. This extension is not supported, nor it is part of our
    projects. Distros having a wrong definition of safety and enabling
    random extension is a real problem, making it somehow official won't
    improve the situation.

    Cheers,

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-internals @
categoriesphp
postedAug 16, '11 at 6:06p
activeAug 16, '11 at 6:12p
posts2
users2
websitephp.net

2 users in discussion

Pierre Joye: 1 post Ferenc Kovacs: 1 post

People

Translate

site design / logo © 2022 Grokbase