This method will not protect your assemblies from a experienced hacker. Everyday we see new keygens, cracks, serials being released that contain ways around copy protection from small companies. This is a simple process that will make a lot of hackers quit because so many others use nothing. If you were a thief would you pick the
house that has security signs and an alarm or one that has nothing? To so begin: Obfuscation is the concealment of meaning
in communication, making it confusing and harder to interpret. Lets begin by looking at the cartoon below: You are probably familiar with the term and probably ignored this like most programmers ignore user security. Today, I’m going to show you reflection and a way to obfuscate it. Please understand that I am aware of ways around this, but I believe some security is better than no security.
In this sample program below, the code appears exactly as it does
in Visual Studio. When the program runs, you get either a true or false
in a console window. Sample Program. using System; using System.Diagnostics; using System.Linq; namespace ObfuscateMe { class Program { static void Main(string[] args) { Console.WriteLine(IsProcessOpen("notepad")); //Returns a True or False depending if you have notepad running. Console.ReadLine(); } public static bool IsProcessOpen(string name) { return Process.GetProcesses().Any(clsProcess => clsProcess.ProcessName.Contains(name)); } } } Pretend, that this is a commercial application. The hacker will only have the executable and maybe a few config files, etc. After reviewing the executable, he can determine if it was produced
in .NET by examing the file
in ILDASM or Redgate’s Reflector. We are going to examine the file using RedGate’s Reflector. Upon launch, we simply drag/drop the exe over to the application. We have the following for the Main method: and for the IsProcessOpen method: Without any other knowledge as to how this works, the hacker could export the exe and get vs project build or copy this code
in and our application would run. Using Reflector output. using System; using System.Diagnostics; using System.Linq; namespace ObfuscateMe { class Program { static void Main(string[] args) { Console.WriteLine(IsProcessOpen("notepad")); Console.ReadLine(); } public static bool IsProcessOpen(string name) { return Process.GetProcesses().Any<Process>(delegate(Process clsProcess) { return clsProcess.ProcessName.Contains(name); }); } } } The code is not identical, but returns the same value. At this point, with a little bit of effort you could prevent the hacker from reverse engineering your code so quickly by using Eazfuscator.NET. Eazfuscator.NET is just one of many programs built for this. Visual Studio ships with a community version of Dotfoscutor. So download and load Eazfuscator.NET and drag/drop your exectuable/project into the window. It will work for a few minutes depending if you have a quad-core or not. After it finishes, open the executable
in RedGate Reflector and you will get the following: Main After Obfuscation IsProcessOpen Method after obfuscation: As you can see with the jumbled characters, it is not as easy as the first example. I am aware of methods around this, but it takes more effort and unless the hacker is up for the challenge, they will just pick another program. This is also helpful if you are a consultant and make clients pay a yearly license fee. This would prevent the average software developer from jumping into your security routine after you have left. I hope this article helped someone. If you have any feedback, please leave it
in the comments below.
