Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » CAS » StrongName   (RSS)

Trusting Applications with their Strong Name

Last time I talked about reasons that you might want to strongly name your application's entry point . The most obvious reason is so that you can setup your security policy to increase the level of trust given to that assembly by the default policy. You
Posted by shawnfa | 1 Comments
Filed under: , ,

When to Strongly Name an Application Entry Point

Junfeng wonders why you might want to strongly name an exe . Sometimes strong naming your exe can be a very useful, but like any feature it's not necessarily always the tool you need for the job. For instance, when running a simple managed .exe off of
Posted by shawnfa | 4 Comments
Filed under: ,

The Difference Between the Strong Name Hash and Hash Evidence

The System.Security.Policy.Hash class allows you to make security decisions based upon the hash of an assembly using the HashMembershipCondition . That sounds awfully similar to how strong names are calculated ... According to ECMA partition II section

Easily Creating a StrongNameMembershipCondition for an Assembly

Taking a break from sandboxing in an AppDomain for a minute, lets take a look at another aspect of policy. One situation that comes up very frequently when trying to execute code in a limited-trust sandbox is that there are some assemblies that you do
Posted by shawnfa | 3 Comments
Filed under: , ,

Spot the Defect: Modifying the Security Policy in Code

Modifying the CLR's security policy can be done in your code by interacting with the SecurityManager object. Specifically, you can access the PolicyHierarchy method which will expose an enumerator over the policy levels, and the SavePolicy method, which
Posted by shawnfa | 2 Comments
Filed under: , , ,
 
Page view tracker