Re: Restrict access to critical functions

2011-12-18 Thread Bystroushaak
Yep. Useful google dork: sandbox. On 14.12.2011 19:55, mta`chrono wrote: Maybe you should use a VM to run your restricted applications. Or have a look a chroot, dchroot or schroot, to setup such stuff. The Programming Language will not help you in this case!

Re: Restrict access to critical functions

2011-12-18 Thread Manfred_Nowak
Bystroushaak wrote: Useful google dork: sandbox. nice: safeD - sandbox - VirtualBox Make a virtual machine an integral part of the compiler :-) -manfred

Re: Restrict access to critical functions

2011-12-15 Thread deadalnix
Le 14/12/2011 13:48, Timon Gehr a écrit : On 12/14/2011 01:28 PM, Kagamin wrote: Goal would be to have a possibility to compile and let run code from random people (some of them perhaps evil minded), watch over the processes and kill them, if they take too long or use up too much memory. I

Re: Restrict access to critical functions

2011-12-15 Thread Jonathan M Davis
On Thursday, December 15, 2011 13:57:21 deadalnix wrote: Even haskell has non pure functions (IO monad for exemple). Actually, Haskell is a 100% purely functional language. Monads are completely pure. They're _how_ Haskell manages to be pure with I/O, when every functional language before them

Re: Restrict access to critical functions

2011-12-15 Thread Timon Gehr
On 12/15/2011 06:04 PM, Jonathan M Davis wrote: On Thursday, December 15, 2011 13:57:21 deadalnix wrote: Even haskell has non pure functions (IO monad for exemple). Actually, Haskell is a 100% purely functional language. Not entirely. For example:

Re: Restrict access to critical functions

2011-12-14 Thread Kagamin
Goal would be to have a possibility to compile and let run code from random people (some of them perhaps evil minded), watch over the processes and kill them, if they take too long or use up too much memory. I believe this is what SafeD is for.

Re: Restrict access to critical functions

2011-12-14 Thread Kagamin
You can also try to run arbitrary D code at codepad.org, see http://codepad.org/f4b7wPhn for example.

Re: Restrict access to critical functions

2011-12-14 Thread Timon Gehr
On 12/14/2011 01:28 PM, Kagamin wrote: Goal would be to have a possibility to compile and let run code from random people (some of them perhaps evil minded), watch over the processes and kill them, if they take too long or use up too much memory. I believe this is what SafeD is for. SafeD

Re: Restrict access to critical functions

2011-12-14 Thread bearophile
Kagamin: I believe this is what SafeD is for. Nope. SafeD is just for memory safety. Bye, bearophile

Re: Restrict access to critical functions

2011-12-14 Thread Andrew Wiley
2011/12/12 Christian Köstlin christian.koest...@gmail.com: Hi, I want to restrict the access of a piece of d2-code to just some functions I declare allowed. E.g. I would like to forbid all access to io and prevent the program to format my hd. Or even better I would like to tell D2 which

Re: Restrict access to critical functions

2011-12-14 Thread Adam D. Ruppe
On Monday, 12 December 2011 at 18:48:17 UTC, Christian Köstlin wrote: Goal would be to have a possibility to compile and let run code from random people (some of them perhaps evil minded), watch over the processes and kill them, if they take too long or use up too much memory. This is

Re: Restrict access to critical functions

2011-12-14 Thread mta`chrono
Maybe you should use a VM to run your restricted applications. Or have a look a chroot, dchroot or schroot, to setup such stuff. The Programming Language will not help you in this case!