Hi,
On Fri, Aug 15, 2014 at 7:59 PM, Stas Malyshev
wrote:
> Hi!
>
> > The source of the problem is that the open_basedir will always leek
> > information about dirs that the user is not suppose to see (out of the
> > open_basedir restriction). The reason is that false value can indicate
> > that
Hi!
> The source of the problem is that the open_basedir will always leek
> information about dirs that the user is not suppose to see (out of the
> open_basedir restriction). The reason is that false value can indicate
> that (more info in the PR or https://bugs.php.net/bug.php?id=65489 ).
> Howe
Hi,
On Fri, Aug 15, 2014 at 2:19 AM, Stas Malyshev
wrote:
> Hi!
>
> > Sorry, I missed that one. I suspect it was the time where I
> > misconfigured git and branches did not get merged. Feel free to merge
> > it back/backport as I won't be able to do it before Monday.
>
> OK, I have backported it
Hi!
> Sorry, I missed that one. I suspect it was the time where I
> misconfigured git and branches did not get merged. Feel free to merge
> it back/backport as I won't be able to do it before Monday.
OK, I have backported it (and following Anatol's patches for it).
--
Stanislav Malyshev, Softwa
hi Stas, Jakub,
On Wed, Aug 13, 2014 at 12:23 AM, Stas Malyshev wrote:
> Hi!
>
> Recently bug 47358 came to my attention, and there's something strange
> with it. It is fixed only for 5.6, not listed in NEWS for even that
> version, but the log contains these:
>
> commit f566b4d32183032663ecb3589
