How can I use CAS in .NET 4 to lock down my MEF extensions? -
I have an application in .NET 4 that uses accessibility for MEF. My main application consists of three assemblies: host
, applications
and contracts
.
Host
"Boot-stacking" is executable which creates and stays the container.
In the application
, there is a logic of my application, and there are more expansion points for third parties.
Contracts
contains interfaces (and some supporting classes) that are used in detail points.
Therefore, no contracts
, but for application
, which develops a third party application.
I think my security model should look like this:
- Should be
host
andthe application
Protective -
Contracts
should be SecuritySafeCritical - All third-party extensions Security
I think that will be satisfied with 1. default I know that I can apply 2. With an assembly feature. The question is how do I apply Rule 3? Does the operating system automatically flags with all download extensions unsafe? Is it possible to get the downloaded extension assembly completely trustworthy?
If your application is running in full faith, by default your extensions are running in full faith And they will be able to do whatever they want. It will not make any difference to what the security features are on them. To limit the extension, you need to create a sandbox app domain. You will set your host
and applications
as a completely dependent in your iPad and all other code will only be allowed by you.
Here is an MSDN article on this topic:
Comments
Post a Comment