php-developer-list | 2002112
Date: 11/18/02
- Next message: Derick Rethans: "Re: [PHP-DEV] [PATCH] php4/configure.in.patch & php4/ext/standard/dns_get_record.patch"
- Previous message: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- In reply to: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Next in thread: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Reply: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 non-shared
> > servers.
>
> True, but it was clearly documented that it shouldn't work. Do we really
> have to make a feature out of every bug? I'd say no...
But why do you assume that the documentation was right and the code was
wrong and not the other way around?
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
- Next message: Derick Rethans: "Re: [PHP-DEV] [PATCH] php4/configure.in.patch & php4/ext/standard/dns_get_record.patch"
- Previous message: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- In reply to: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Next in thread: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Reply: Derick Rethans: "Re: [PHP-DEV] Re: #20461 [Opn->Bgs]: Unable to access $PHP_AUTH_USER or $PHP_AUTH_PW"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

