Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6654
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3FE494B9.7090501@cschneid.com>
Date: Sat, 20 Dec 2003 19:28:09 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031009
MIME-Version: 1.0
To: Lukas Smith <smith@backendmedia.com>
Cc: =?ISO-8859-2?Q?=22=27ing=2EMartin_Pr=E1=B9ek=27=22?= <prasek@silesia.cz>,
	internals@lists.php.net
References: <006501c3c6f2$9002e540$d300a8c0@webpropag.cz> <php.internals-6649@news.php.net>
In-Reply-To: <php.internals-6649@news.php.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Extending PHP  with sandbox capability ? 
From: cschneid@cschneid.com (Christian Schneider)

Lukas Smith wrote:
>>Sandbox ?

This would have to be done _very_ carefully to not leave a backdoor 
open. PHP offers oh so many ways of accessing the system.

I guess one'd have to start with safe_mode with quite some functions 
disabled and go from there. But...

> BTW: if PHP wants to be the ultimate template engine it needs such a

Maybe it's easier (and safer too) to not eval PHP code from external 
sources. You'd also have to make sure the output of their code is valid 
(X)HTML or they could render your whole site invalid (think closing 
table they didn't open, inserting javascript code and the like). And 
that's already hard enough as it is. Allowing them to submit SQL queries 
for example opens up a whole new can of worms.

I guess a sandbox model is something to be thought about for PHP6 ;-)

- Chris