in reply to Re: Re: Running untrusted perl code
in thread Running untrusted perl code

Don't forget to provide a means for users to kill the jobs that they submit. That would be a useful feature for all concerned.

Not knowing what range of tasks the untrusted perl code is expected to address, I wonder whether there might be a dilemma between keeping the server safe versus providing an adequate range of resources to support meaningful tasks (e.g. access to non-core modules? user-specifiable input data? debugging mode?) Anyway, good luck with it.

  • Comment on Re: Re: Re: Running untrusted perl code

Replies are listed 'Best First'.
Re: Re: Re: Re: Running untrusted perl code
by BUU (Prior) on May 31, 2004 at 04:55 UTC
    Providing a means to kill runaway processes is definately a good idea, I'll have to see exactly what is needful.

    Perhaps I should have explained further what I'm contemplating with the use of this code. The main point is to provide a perl scripting language for a MU* type of system, so the "tasks" performed by the various bits of code should be really fairly simple, and not need to use any "outside" resources.
[reply]

In Section Seekers of Perl Wisdom