Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74966
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53A10C5B.1000003@lerdorf.com>
References: <CAEZPtU7rc+JpguO=Ke8UmiLLaidvyJEQ81C9Lsvn8yHgkp=+qw@mail.gmail.com>
	<53A10C5B.1000003@lerdorf.com>
Date: Wed, 18 Jun 2014 05:57:09 +0200
Message-ID: <CAEZPtU7=rKAuucx61NUqteoD4z-w6RK0dLQKKK=RRjVnxkViug@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHP6, drop open_basedir?
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Jun 18, 2014 at 5:49 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> I think you have a very narrow view of how this feature is used.
> Security and code quality is about layers. This is a useful layer that
> helps verify that an application, or even a subset of an application, is
> only able to access a given set of directories. If something tries to
> access a file outside of the defined scope, we get an error and we know
> there is a bug in the code. I, and many companies out there, rely quite
> heavily on this feature to catch mistakes. And yes, there are ways of
> getting around it at the PHP-level if you deliberately craft your PHP
> code to do so, but that doesn't make the feature any less useful to all
> the people using it to catch non-deliberate mistakes.

It gives a false sense of safety, and that alone for me is a good
enough reason to remove it. it is not as bad as safe_mode but simply
not good.

That being said I have no issue with keeping it besides the lost
opportunity to get rid of an old bad decision.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org