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

Restrict environment #2

Open
der-flo opened this issue May 25, 2011 · 2 comments
Open

Restrict environment #2

der-flo opened this issue May 25, 2011 · 2 comments

Comments

@der-flo
Copy link

der-flo commented May 25, 2011

It is quite easy to break out of the sandbox, because the context doesn't restrict things like constants etc. .
With e.g. https://github.com/tario/shikashi you can restrict them, but it isn't ruby-1.9-compatible yet.
Can you make suggestions how you would solve this problem in combination with "sandboxed"?

Thanks,
der Flo

@QaDeS
Copy link
Owner

QaDeS commented May 26, 2011

Currently, Sandboxed is merely a wrapper for Ruby's $SAFE mechanism. The current HEAD is prepared to use other mechanisms, and I even started to implement source inspection. Alas, my current project doesn't allow to finish it right now.

If you have urgent requests that can be fixed in little time, I'll be glad to help, though. Just bring on the details / test cases ;o)

@der-flo
Copy link
Author

der-flo commented May 26, 2011

Well ok, I fixed this issue by moving all the sandboxed code out to another ruby process. I'll watch this project and this issue for progress.
Thanks for your answer.

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

2 participants