Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Your specification doesn't seem very clear to me. It seems that you do want the untrusted code to be able to operate on long-lived data structures and files. But how do you define malicious code, then? Let alone hindering it from doing its evil. Locking down what the user-supplied code is able to do might be possible but the restriction will apply to all code, then. Malicious or not. Commented Jun 19, 2017 at 0:47
  • the code should be allowed to do whatever it wants with the files it is provided, but only with those files. It should not be able to break out and alter any other files. Commented Jun 19, 2017 at 19:00