in reply to Perlmonks MOO

Some thoughts on the security aspect. I know theres a *nix function called "chroot", which lets you redefine the root of a process. I assume theres also someway to limit the cpu / memory usage of a process via similar means? What if the parent script forked a child that would just execute the user submitted code, but execute it only inside this chroot and under process restrictions? This way you don't have to worry about messing about with Safe or any such ops, and you can even give the user a small amount of control over his own file system, with the ability to create tmp files and such.

Replies are listed 'Best First'.
Re: Re: Perlmonks MOO
by Trag (Monk) on May 29, 2004 at 01:27 UTC
    Hmm, internal filesystems within the MOO. That could make things interesting...


    our @item = reverse (114, 101, 107, 99, 97, 104, 32, 108, 114, 101, 80, 32, 114, 101, 104, 116, 111, 110, 97, 32, 116, 115, 117, + 74); local $my = reverse ")meti@\ ,rhc (pam tnirp";eval $my;