Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Isolation? #3

Closed
leblancmeneses opened this issue Nov 30, 2012 · 4 comments
Closed

Security Isolation? #3

leblancmeneses opened this issue Nov 30, 2012 · 4 comments

Comments

@leblancmeneses
Copy link

I like the idea of using razor syntax in our email templates.

From what i can tell using this engine could have security implications if template editing is externalized.

We want end users to be able to update these templates. Does your framework support isolation/chroot - so that they cannot affect anything outside the template engine's sandbox?

@jlamfers
Copy link
Owner

This framework has no sandbox features (yet :-)

@leblancmeneses
Copy link
Author

Okay i tried your solution here is one issue I had.

after installing the nuget package - I am having problems on our build server that uses nuget's package restore system. (we don't checkin dll's. I think it has to do with the naming convention and actual dll's you reference do not match)
http://blog.nuget.org/20120518/package-restore-and-consent.html

fyi: about the sandbox feature ...
https://github.com/RickStrahl/Westwind.RazorHosting
seems to prevent access by hosting in another appdomain.

@jlamfers
Copy link
Owner

jlamfers commented Dec 7, 2012

It probably was due to the fact that there were two versions 2.4 (2.4 and 2.4.0) on nuget. I published a new nuget package version 2.4.1 holding the same binaries (v2.4) and content.

@jlamfers
Copy link
Owner

When using isolation with appdomains you can constraint execute and access permissions. You cannot simply constraint things like creating threads, allocating memory, and other resource consuming things. If you start to allow untrusted users to execute untrusted code I think you should monitor and constraint that too, or else you should run each request in a seperate (balanced) process to protect any user from any other's misbehaviour. I decided that such behaviour is outside the scope of this framework, at this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants