There are a lot of assemblies that we create in our projects daily. Have we ever wondered that all those assemblies that we write after putting in such a lot of hard work and effort could be easily used by someone else. Also at times you don't want others to use a particular class or a method because it may retrieve some important or confidential information. .NET by itself works on the concept of sharing assemblies between applications which enables rapid application development (RAD). We can secure our code by identifying the caller.
Managed code offers several ways to restrict method access:
- Limit the scope of accessibility to the class, assembly, or derived classes, if they can be trusted. This is the simplest way to limit method access. Note that, in general, derived classes can be less trustworthy than the class they derive from, though in some cases they share the parent class's identity. In particular, do not infer trust from the keyword protected, which is not necessarily used in the security context.
- Limit the method access to callers of a specified identity -- essentially, any particular evidence (strong name, publisher, zone, and so on) you choose.
- Limit the method access to callers having whatever permissions you select.
Let's see how we can accomplish this:
- Create a strong named assembly e.g. Calc.dll with one class called
MyClass having the
Add() method which adds two numbers.
- .NET Framework has a tool called SecUtil.exe.
- Go to the Visual Studio command prompt
- Type SecUtil.exe /?. This will display help and all the available options.
- Then type secutil.exe -s -hex -c Calc.dll (or the name of your DLL).
- This will display the public key as hexadecimal value as shown below:
C:\DotNet\DLLProj\bin\Debug>secutil -hex -c -s Calc.dll
Microsoft (R) .NET Framework SecUtil 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Public Key =
Now You can use this public key with any class or method in your assembly that you don't want anyone else to access, you can use the
StrongNameIdentityPermissionAttribute for this. Any calling code that isn't signed with your *.snk file won't have access to it.
Here I have used it at the class level. You can also achieve the same at the method or assembly level.
So, let's secure our class:
public class MyClass
public int Add(int i , int j)
- Now create any Win app which will be a client app for this assembly.
- Do not strong name this assembly.
- Reference the above assembly in the client App.
- Call the
Add method or any other method of
- The code will compile.
- Try and execute the function call. You will get an error message similar to the one below:
Additional information: Request for the permission of
type System.Security.Permissions.StrongNameIdentityPermission, mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.
- 16th January, 2006: Initial post