Printable View
For those that remember our discussions and my code for loading plugins, I am now working on trying to add some safety to these plugins. Basically I am looknig for some information/code to specify what the dll can do and make sure the dll cannot override that. In other words, I want to keep plugins from running executables and keep it from doing other dangerous actions.
Any thoughts, theories, or code ais welcome..
That one is a bit difficult since you aren't the one writing the code for the plugins. I think you can run different threads in different User Permissions, maybe you could run the plugins in an alternate thread with lesser permissions.
Well, what I am hoping is that with the power that was given with Reflection for using dll's very dynamically, that MS might have actually considered stuff like this.
I mean I could impersonate a low permission user, but I wonder if the dll would be able to override that. I would assume no since it should be running under a persmission that wouldnt allow that. I will just have to do some experimenting with this.