For those who are interested (and I already chatted with Chris on IRC),
I've implemented a pastebin that is able to (among some other things) to
run arbitrary Haskell code: http://paste.hskll.org/
I've also developed a 'restricted-workers' library for managing processes
that should run in secured e
On 12 October 2013 01:19, Johan Tibell wrote:
> Whatever guarantees GHC offers (e.g. using Safe Haskell), I would always run
> things like these in a sandbox. It's much better for security to dissallow
> everything and then whitelist some things (e.g. let the sandbox communicate
> with the rest of
Whatever guarantees GHC offers (e.g. using Safe Haskell), I would always
run things like these in a sandbox. It's much better for security to
dissallow everything and then whitelist some things (e.g. let the sandbox
communicate with the rest of the world in some limited way) than the other
way arou
On 12.10.2013 00:30, Christopher Done wrote:
Is there a definitive list of things in GHC that are unsafe to
_compile_ if I were to take an arbitrary module and compile it?
E.g. off the top of my head, things that might be dangerous:
* TemplateHaskell/QuasiQuotes -- obviously
* Are rules safe?
*
On Fri, Oct 11, 2013 at 1:30 PM, Christopher Done wrote:
> Is there a definitive list of things in GHC that are unsafe to
> _compile_ if I were to take an arbitrary module and compile it?
>
> E.g. off the top of my head, things that might be dangerous:
>
> * TemplateHaskell/QuasiQuotes -- obviousl
Is there a definitive list of things in GHC that are unsafe to
_compile_ if I were to take an arbitrary module and compile it?
E.g. off the top of my head, things that might be dangerous:
* TemplateHaskell/QuasiQuotes -- obviously
* Are rules safe?
* #includes — I presume there's some security ri