[Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited) (original) (raw)

Maciej Fijalkowski fijall at gmail.com
Sat Apr 9 08:47:55 EDT 2016

I'm with Victor here. In fact I tried (and failed) to convince Victor that the approach is entirely unworkable when he was starting, don't be the next one :-)

On Sat, Apr 9, 2016 at 3:43 PM, Victor Stinner <victor.stinner at gmail.com> wrote:

Please don't loose time trying yet another sandbox inside CPython. It's just a waste of time. It's broken by design.

Please read my email about my attempt (pysandbox): https://lwn.net/Articles/574323/ And the LWN article: https://lwn.net/Articles/574215/ There are a lot of safe ways to run CPython inside a sandbox (and not rhe opposite). I started as you, add more and more things to a blacklist, but it doesn't work. See pysandbox test suite for a lot of ways to escape a sandbox. CPython has a list of know code to crash CPython (I don't recall the dieectory in sources), even with the latest version of CPython. Victor

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/fijall%40gmail.com

More information about the Python-Dev mailing list