pysandbox is a new Python sandbox project under development. By default, untrusted code executed in the sandbox cannot modify the environment (write a file, use print or import a module). But you can configure the sandbox to choose exactly which features are allowed or not, eg. import sys module and read the file /etc/issue.
Download the repository using git: git clone git://github.com/haypo/pysandbox.git or git clone http://github.com/haypo/pysandbox.git
Or download the .zip or .tar.gz tarball using the "Download source" button on the website.
I think that the project reached the "testable" stage. I launch a new challenge: try to escape from the sandbox. I'm unable to write strict rules. The goal is to access objects outside the sandbox. Eg. write into a file, import a module which is not in the whitelist, modify an object outside the sandbox, etc.
To test the sandbox, you have 3 choices:
Don't use "with sandbox: ..." because there is known but with local frame variables. I think that I will later drop this syntax because of this bug. Except of debug_sandbox, I consider that all features are safe and so you can enable all features :-)
There is no prize, it's just for fun! But I will add the name of hackers founding the best exploits.
pysandbox is not ready for production, it's under heavy development. Anyway I hope that you will quickly find bugs!
Use tests.py to found some examples of how you can escape a sandbox. pysandbox is protected against all methods described in tests.py ;-)
See the README file to get more information about how pysandbox is implemented and get a list of other Python sandboxes.
pysandbox is currently specific to CPython, and it uses some ugly hacks to patch CPython in memory. In the worst case it will crash the pysandbox Python process, that's all. I tested it under Linux with Python 2.5 and 2.6. The portage to Python3 is not done yet (is someone motivated to write a patch? :-)).
-- Victor Stinner http://www.haypocalc.com/