Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74970
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53A12C3D.1060808@sugarcrm.com>
References: <CAEZPtU7rc+JpguO=Ke8UmiLLaidvyJEQ81C9Lsvn8yHgkp=+qw@mail.gmail.com>
	<53A10C5B.1000003@lerdorf.com>
	<CAEZPtU7=rKAuucx61NUqteoD4z-w6RK0dLQKKK=RRjVnxkViug@mail.gmail.com>
	<53A12C3D.1060808@sugarcrm.com>
Date: Wed, 18 Jun 2014 08:29:18 +0200
Message-ID: <CAEZPtU6wrE0P1UmUP4f8_OX7=vFyObTChKbFg7h-qiq0Eh6YtQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.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 8:05 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> 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.
>
> If you use it right, it does not. Every security feature would give you
> false sense of safety if you use it wrong - but that alone is not the
> reason to not have it at all, if it has legitimate uses. IMO
> open_basedir does.
>
>> That being said I have no issue with keeping it besides the lost
>> opportunity to get rid of an old bad decision.
>
> Bad decision was to brand open_basedir as security function that allows
> defense against attacker with PHP code execution rights. It is obvious
> we can not deliver on this promise. However, it does not mean that used
> differently - e.g. as a safeguard in your own code to not access things
> that you don't want this code to access by mistake - it can not be used.
> I think it can.

This exact example is easily done using system features.

Anyway, we have different views and that's why I started to this
thread, to know other views :)

I will still create a RFC to get an official result on that as all the
users I talked to, as well as security people, consider this feature
as a problem.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org