Roslyn c# scripting sandbox

Question

Is there a way to sandbox execution of a script such that it a) Can't do anything "dangerous" and b) it can access any files it wants to so long as the file is within the same directory as the script file itself. Kind-of as-if it were to treat all file-paths as relative.

I guess I'm asking about Roslyn's scripting security measures and their level of customization.

Roslyn has absolutely no security when executing scripts? That's even worse than faking scripting with codedom. — RoyalPotato
– RoyalPotato, Commented Mar 20, 2016 at 2:33
Securely allowing arbitrary code is an extremely hard problem. Roslyn does not try to address that; you should not run untrusted scripts. — SLaks
– SLaks, Commented Mar 20, 2016 at 2:35
In fact, if you also want to protect the secrecy of other data on the same computer, it's basically impossible. — SLaks
– SLaks, Commented Mar 20, 2016 at 2:36
Yeah, I was hoping there would be an easy way to "secure" things. Because .Net could make quite the powerful scripting engine for a game. Looks like I'll have to find a different route, thanks for the advices! — RoyalPotato
– RoyalPotato, Commented Mar 20, 2016 at 2:46

Community · Accepted Answer · 2017-05-23 12:08:34Z

1

This is possible, but as SLaks says, it is a hard problem. You should probably read In .NET 4.0, how do I 'sandbox' an in-memory assembly and execute a method?. You would need the following steps

Use a CSharpCodeProvider or VBCodeProvider to compile the source to an assembly on the harddrive.
Create a new AppDomain granting it only those permissions you would like it to have.
Use MarshalByRefObject's to communicate back and forth between your original AppDomain and the child AppDomain you've just created. See this and this.

edited May 23, 2017 at 12:08

CommunityBot

11 silver badge

answered Jun 16, 2016 at 21:38

Bert Cushman

8012 gold badges9 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

RoyalPotato Over a year ago

A: I was hoping to avoid System.CodeDom. B: I was also hoping to avoid creating another appdomain. C: I require greater control over script permissions than this would allow. For example, I'm OK with scripts playing with file-IO, but only if I can force all file-io activities to work out of directories relative to my app's .exe (yes, even if they try to specify an absolute directory). I knew these goals were longshots though, to be honest.

cskwg Over a year ago

AFAIK, this is not possibly anymore with DotNetCore.

Collectives™ on Stack Overflow

Roslyn c# scripting sandbox

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related