On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
But why do you assume that the documentation was right and the code was
wrong and not the other way around?
Because it was working like documented before. (When the documentation
was written). Anyway, not sure what to do with this one...
I
On Mon, 18 Nov 2002, Edin Kadribasic wrote:
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
I don't have the energy to do a cvs check, but I remember adding this
restriction years ago (php2 days) and then removing it (by commenting out
the check) ages ago as well. I'm not sure PHP4 ever had
On Mon, 18 Nov 2002, Edin Kadribasic wrote:
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
But why do you assume that the documentation was right and the code was
wrong and not the other way around?
Because it was working like documented before. (When the documentation
was written).
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
I'm still not overly convinced that this isn't a restriction that should
only kick in when safe_mode or open_basedir is active. This change is
going to break working code and it is not a security fix on non-shared
servers.
True, but it was clearly
On Mon, 18 Nov 2002, Derick Rethans wrote:
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
I'm still not overly convinced that this isn't a restriction that should
only kick in when safe_mode or open_basedir is active. This change is
going to break working code and it is not a security fix on
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
On Mon, 18 Nov 2002, Derick Rethans wrote:
On Sun, 17 Nov 2002, Rasmus Lerdorf wrote:
I'm still not overly convinced that this isn't a restriction that should
only kick in when safe_mode or open_basedir is active. This change is
going to
But why do you assume that the documentation was right and the code was
wrong and not the other way around?
Because it was working like documented before. (When the documentation
was written). Anyway, not sure what to do with this one...
I don't have the energy to do a cvs check, but I
