Security Policies
When code is loaded into the runtime, the first things the runtime must figure out are “what actions should I allow this code to perform, and what resources should I allow it access to?” This is handled in a straightforward way: Each assembly in .NET exposes a series of characteristics (called evidence) that the runtime will examine in order to answer the aforementioned questions. Examples of this evidence include who signed the assembly, where the assembly came from, and so on.
Note
Remember that assemblies are units of deployable code.
The supplied evidence is used in conjunction with the established security policy to determine which permissions the assembly will be assigned. A security policy is a set of rules that are ...
Get Visual Basic® Programmer's Guide to the .NET Framework Class Library now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
