One thing you should consider: Do it in a perlfunc:chroot environment. That way you can get most of the problems that might be there refering to the file system. Don't get me wrong - that can never a substitute for a good check against what will be sent. I would sugguest to strip every perlfunc:system and backticks out of it - it's almost impossible to make those secure. Keep it that way: The more you restrict the more secure the thing is. Keep in mind what you really want to achieve and don't permit them more than that. Stripping down permissions is IMHO the wrong approach to a secure system - giving (some) permissions is the way you should go.
--
use signature; signature(" So long\nAlfie");

In reply to Re: A perl sandbox? by alfie
in thread A perl sandbox? by nashdj

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.