Re: [PATCH] Fix for bug #31440 (GLOBALS can be by G/P/C when register_globals=On)
| From: | Stanislav Malyshev | Date: | Wed, 16 Feb 2005 09:11:41 +0000 |
| Subject: | Re: [PATCH] Fix for bug #31440 (GLOBALS can be by G/P/C when register_globals=On) | ||
| References: | 1 2 3 4 | Groups: | php.internals php.internals |
| Request: | Send a blank email to internals+get-15024@lists.php.net to get a copy of this message | ||
AG>>>Seems like a bad excuse. Being able to destroy a superglobal array like
AG>>>that is clearly a bug that should be fixed.
IMO there should be no possibility to destroy GLOBALS with ?GLOBALS=foo,
but there should be possibility to write GLOBALS with ?GLOBALS[foo]=bar -
why not, if we allow accessing globals anyway? I didn't check how hard
it should be to separate these - if it's hard then restricting access to
GLOBALS would be good.
--
Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115