Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make untrusted python code execution safe (pypy-sandbox) #1

Open
Stinkfist0 opened this issue May 14, 2013 · 0 comments
Open

make untrusted python code execution safe (pypy-sandbox) #1

Stinkfist0 opened this issue May 14, 2013 · 0 comments

Comments

@Stinkfist0
Copy link
Contributor

Migrate to here from realXtend/tundra#87

Python is not very useful now for EC_Script because it is a gaping security hole. It can be made safe by integrating pypy-sandbox, a standalone python interpreter that is run in a sub-process by pypy_interact.py. pypy_interact.py can be run by the current embedded CPython, so we don't need to remove the current embedded python.

Pypy-sandbox by itself is not very helpful because it won't be able to talk to the Tundra API. So we also need ctypes bindings to Tundra that Pypy-sandbox can load. Ctypes is not the only option, if we want to expose only a small subset of the Tundra API, this could be done with pickle messages over a port talking with pypy_interact.py.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant