Be very, very, careful. You don't want someone submitting a rootkit as a sample solution! Were I you I would do some very serious studying of ways of executing untrusted code. Note that there are well-known ways of breaking chroot jails, that is not enough. On many *nix systems you have something called POSIX capabilities (a marketing misnaming since they have essentially nothing to do with real capabilities) that might be able to give you enough protection to sleep at night.

Other ideas are to use OpenBSD for the test, run the code inside of VMWare (from a stock image that you throw away afterwards) or examine user-mode Linux.

Personally I like the VMWare and user-mode Linux ideas the best, but YMMV. It is your system after all...

In reply to RE (3): Flocking in advance by tilly
in thread Flocking in advance by larsen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.