If you run ChucK on a Unix-like system, like Linux or OSX, as a restricted user, it shouldn't be able to do anything nasty to the actual installation of the operating system. OTOH, the low-level connection to the sound interface means that the watchdog needs to be active, or folks can crash your computer with an endless loop without waits. I'm not completely sure about the status of the watchdog on Linux.

/Stefan

On Tue, Jan 4, 2011 at 7:58 PM, Alan Yoder <tempjayren@gmail.com> wrote:
right, i havent been toying with chuck all that long so i'm a newbie, really more of a meganewbie i think, though isn't one of those os features the ability to read files such as .ck files? if you neuter chuck like that, how will it get its code to play?



On 1/4/2011 1:26 PM, Zed A. Shaw wrote:
Hi,

I'm toying with a small idea to let people upload bits of chuck code to
a website and then have it play out to the world.  I haven't started
coding anything yet, but I was wondering how hard it is to put ChucK
into a safe environment so that it can't touch the OS?  In Lua I'd do
that by ripping out the various OS features.  Is there a similar thing
with Chuck?

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users



--
Release me, insect, or I will destroy the Cosmos!