Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124815
Message-ID: <7b881961-e8bf-4a81-96f7-798968d10098@gmail.com>
Date: Tue, 6 Aug 2024 21:13:56 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [Discussion] Sandbox API
To: internals@lists.php.net
References: <e08f6af322dcc5b4e4dd5e772f28be07ffa07ba4.camel@ageofdream.com>
 <c510eb675bd0038efbbe5489bebd42ff7438e967.camel@ageofdream.com>
 <7d9a9752-a202-4099-a60a-2686d4265d96@gmail.com>
 <ffc9c850-06f1-4937-be55-b9e2cc614dfb@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <ffc9c850-06f1-4937-be55-b9e2cc614dfb@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: dossche.niels@gmail.com (Niels Dossche)

On 06/08/2024 21:05, Rob Landers wrote:

> Hey Niels,
> 
> I find this assertion kind of scary from a shared hosting perspective or even from a 3v4l kind of perspective. How do these services protect themselves if php is inherently insecure?
> 
> — Rob

Hi Rob

I'm not a sysadmin guy or anything like that, so I don't know how shared hosting stacks looks like in practice.
But containers, chroot jails, seccomp-bpf, ... can offer protection. And you should be doing those things anyway (as a matter of defense-in-depth) if you're offering servers running untrusted code.

Kind regards
Niels