ID: 24732
Comment by: dpenning at s0nix dot de
Reported By: nightcat at poczta dot onet dot pl
Status: Open
Bug Type: Feature/Change Request
Operating System: *
PHP Version: 5.0.0b1 (beta1)
New Comment:
you can scan the file using the tokenizer and decide yourself if it is
secure
Previous Comments:
------------------------------------------------------------------------
[2003-07-20 17:25:03] nightcat at poczta dot onet dot pl
Description:
------------
Basicly, everyone who creates CMS at some point want to add modules, or
any other type of space for additional code.
But also we want this code to be signed as "untrusted", because we
_are_ afraid about this code (we don't know).
It would be really great to be able to lock some things for include
code. I don't have any clear vision of this, but i'll try to paste
example of my intention.
Reproduce code:
---------------
lock_variables($db->password, $accountPassword);
block_functions(mail, fopen, file);
include_once('module.inc');
unblock_functions(mail, fopen, file);
unlock_variables($db->password, $accountPassword);
Expected result:
----------------
It's only idea.
I'd expect that from inside of this include (and any recursive) there
want be any possiblity to use those functions and modify those
variables.
Secondly it would be really _great_, if if functions called from inside
of include could use everything normally. For eg. there won't be any
way to modify DB password (which is property of object $db) but calling
$db->connect would work normally (if it's not blocked by
block_functions() ).
Actual result:
--------------
There is really no way in PHP4 to prevent some untrusted parts from do
what they want with whole CMS. In PHP5 i can do it but in very tricky
and dirty way.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=24732&edit=1
