On Wed, 30 Jun 2004, Gareth Ardron wrote:
Does the examples I gave you before not count ?
Yes. It does not count.
in this case, the __destruct() function within someOtherClass does
absolutly bugger all.
You can't reference one object from another's destructor. PHP makes no
promises about
This is a possible fix for #28167
Anyone care to have a look ?
--
Ard
Index: zend_builtin_functions.c
===
RCS file: /repository/ZendEngine2/zend_builtin_functions.c,v
retrieving revision 1.237
diff -u -r1.237 zend_builtin_functions.c
Hi,
This post is about some general considerations about inexpediencies
regarding safe_mode and documentation. This is not about the fundamental
flaws regarding safe_mode, but rather some unfortunate side-effects,
that *could be fixed*. Please pour up a nice cup of coffee or tea :) My
questions
Peter,
although he hangs out here from time to time, you may want to forward
this to Stefan Esser of HardenedPHP
http://www.hardened-php.net/
l0t3k
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
currently there exists REGISTER_XXX_CONSTANT macros for procedural
extensions. we need their counterparts (REGISTER_CLASS_XXX_CONSTANT) to
populate the constants_table of internal classes.
l0t3k
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Even better, if you do discover something that might be exploitable,
you should keep your mouth shut and instead send mail to
[EMAIL PROTECTED] where, among a handful of others, Stefan will also
read your message.
--Wez.
On Wed, 30 Jun 2004 13:45:50 -0400, l0t3k [EMAIL PROTECTED] wrote:
Hi Moriyoshi,
The object handle is not a unique identifier. Different object types (e.g.
PHP objects, SimpleXML objects) can have the same object handle. The real
unique identifier is object handle + object handlers array or more useful
in your case, possibly class name and object handle.
Andi