Home/ Questions/Q 53027
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T16:59:57+00:00

I want to be able to run unstrusted ruby code. I want to be

  • 0

I want to be able to run unstrusted ruby code. I want to be able to pass variables to said untrusted code that it may use. I also want said code to return a result to me. Here is a conceptual example of what I am thinking

input = 'sweet' output = nil Thread.start {    $SAFE = 4    #... untrusted code goes here, it uses the input variable(s)    #to calculate some result that it places in the output variable } #parse the output variable as a string.

Just to clarify, I am basically using the untrusted code as a function. I want to provide its some inputs, and then allow it to write to the output. That is all I really want, I don’t care how it is done, I just want the ability to use untrusted Ruby code as a sort of function. The solution does not have to look anything like the code I wrote above, I am just using it to illustrate what I want.

Now, I can currently think of 3 ways to do this:

  1. Use the $SAFE level construct above.
  2. whytheluckystiff has a Sandbox plugin for ruby
  3. I could run each function in its own virtual machine, using some sort of os virtualization software like vmware or Xen or something.

I am wondering if anyone has any recommendations for running untrusted ruby code in a functional way? What option would you recomend? How would you go about it? Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. $SAFE is not enough; you need to be at least at the level of Why’s freaky sandbox. However, I don’t know if that sandbox code is actively maintained or if he/they ever solved the holes such as infinite loops, etc.

    Unsafe generally means hostile. If you can relax from hostile to, say, ‘naive’, and depending upon the requirements of your app, you might get away with sandboxing in Ruby. It’s not really a first-class scenario in the language design.

    Even with that, though, you probably don’t need to go to the machine level of separation. I’d feel pretty safe using a sandbox in a separately spawned process, with your app functioning as a process manager to kill off any that manage to hang/flame. Now, that is a few orders of magnitude more work than your simple block above.

    But remember and keep repeating, ‘SAFE can’t deal with hostile’.

    • 0