Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61977
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVpXTza67aOOeFqJ72F3=nxe3vTRHWkkzZNc+FChhCbwhg@mail.gmail.com>
References: <CANVTSm5g0FWqe=HaJTutniLYOj19rp5twOzF0jti0y3iEsnWEg@mail.gmail.com>
	<CAKOpQSwSwseEoxDYzpfwkgk-azxKyAVq=hRJa=P=v8qg7VAJ_A@mail.gmail.com>
	<CAFt2z-nHB91SSNaJpn_K1-OzWtC7=W4WUUKCBQYHbb+kbeKsBg@mail.gmail.com>
	<CAESVnVpXTza67aOOeFqJ72F3=nxe3vTRHWkkzZNc+FChhCbwhg@mail.gmail.com>
Date: Fri, 3 Aug 2012 00:17:21 +0100
Message-ID: <CAPwsocEbXSVSc-aDUQjjaADF3-pNLQF=Danxo67GE5oZpCY-5A@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Add runkit to PHP Runtime
From: leight@gmail.com (Leigh)

> Sandboxing: Complicated by the fact that it only works in a threaded
> build, can't transfer all types (e.g. resource, complex objects), and
> can't run concurrently.  Until/unless these problems can be
> meaningfully solved, I wouldn't consider it a functional
> implementation.

To me the "thread thing" feels like the dirty hack workaround
_because_ it's in PECL, and this is the only option available.

chroot() isn't available everywhere. chrooting with php-fpm requires
an additional amount of configuration (and forethought), and running
both a chrooted and non-chrooted pool even more so.

I did originally pose it as a potential v6 feature, and that's where
I'll leave it. In the "wouldn't it be nice" pile.

There's always going to be cases where products want to use
user-generated code, and isolating in a way that prevents it breaking
things is desirable. Having the right tools to do that instead of
requiring clunky workarounds "would be nice" when the engine can
support it.