Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115406
MIME-Version: 1.0
References: <CAF+90c-4-R4SYY_AAL679ZYBn2QAZTYAGXH6E6Bz1hYGN=MFcA@mail.gmail.com>
 <5af05f50-cf90-c0f2-adb7-b70b57ca1186@gmx.de> <d6cea3fb-25b7-fee8-26b8-8705fb33fc5e@gmail.com>
In-Reply-To: <d6cea3fb-25b7-fee8-26b8-8705fb33fc5e@gmail.com>
Date: Mon, 12 Jul 2021 15:54:25 +0200
Message-ID: <CAF+90c_23nSxd5zJjtdTP8yNKquwNK9sERi8E7VpQ6oxHRa1EQ@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000083c7be05c6ed76cf"
Subject: Re: [PHP-DEV] Re: open_basedir?
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000083c7be05c6ed76cf
Content-Type: text/plain; charset="UTF-8"

On Thu, Jul 8, 2021 at 11:34 PM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > Apparently, there has been no resolution for this issue so far.  While I
> > don't really care about the open_basdedir directive per se, I fully
> > agree that we should not advertize it as security feature, and to
> > clearly state this in the PHP manual, as well as in our security policy.
>
> Correct. As I mentioned, de-facto it's already the case for years now.
> Let's fix the docs at least? Though I'd really start thinking about
> maybe removing it in the next major version...
> --
> Stas Malyshev
> smalyshev@gmail.com
>

Yeah, feel free to go ahead with updates for docs & security policy.

Regards,
Nikita

--00000000000083c7be05c6ed76cf--