Summary

for RuBoard

This chapter discussed the three different kinds of permissions: code access permissions, identity permissions, and other permissions. Standard code access permissions directly protect resources. Identity permissions represent evidence that is granted to assemblies. Other permissions are those that don't fall into either of the other two categories. The only such permission in the .NET Framework class library is built on role-based security.

Permissions are used in several different circumstances. First, they are used by security policy to grant specific rights to code. Second, they are used in permission demands to protect against luring attacks. Third, they are used in other security actions, like Assert . Due to the variety of uses for permissions, they are represented in two different forms: declarative and imperative.

The .NET Framework comes with a wide range of default permissions. Table 6.1 lists 25 different permission classes in the .NET Framework used to protect a variety of resources.

In order to allow operations to occur on more than a single permission at a time, the .NET Framework has permission set objects. These are collections of permissions that work effectively as a single permission object.

Permissions really are at the core of Code Access Security. They represent all the nuances of different resources that you might want to protect, and they are the primary focus of stack walks. Because of this, permissions and permission sets are the most widely used security objects in the .NET Framework class libraries.

for RuBoard


. NET Framework Security
.NET Framework Security
ISBN: 067232184X
EAN: 2147483647
Year: 2000
Pages: 235

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net