Now we are able to use Enigma API functions. Simply drag and drop this file in project in Solution Explorer: In Visual Studio we need to add Enigma_IDE.cs module to the project (take it from the folder “EnigmaSDK\C# (.NET)\” of installed Enigma Protector). Click Options button and specify the type of data as Wide String:įinally, list of protected strings should look as following:Īfter protected strings are loaded in protection, we need to extract them from protection in application. Let’s add strings for protection in Enigma Protector, go to Protection Features – Protected Strings, add couple of strings from source code there. They can also be used for strings protection. Using same example above, we have two strings in source code suitable for protection, they are the following:Īpart of that, in our example, there are strings in form designer module, inside InitializeComponent function. Imagine that cracker dumped the application, somehow got rid of protection, resulting file won’t work (or work correctly) because protected strings will be kept in removed protection, that’s a purpose of using protected strings feature. We can use protected strings for deeper integration of application into protection. dll, pictures, data files, they all can be hidden from cracker using this feature (files, embedded into Virtual Box, can be removed from disk since they will be emulated by protection in memory) Virtual Box – Files – if you have some external files, like.Protection Features – Inline Patching – protects application and protection code against changes in memory.Checkup – Control Sum – checks for modification of protected file and protection core in process memory.Debugger is a tool that crackers are using to reverse the application Checkup – Anti-debugger – force protection to quit application if debugger is found.This step is simple to apply, it describes basic features of Enigma Protector which are worth to use: If there is no ways to apply other options described below, that’s already good point for start. This kind of protection much complex for cracker to analyze. When Enigma finishes, run protected file, check if it works well. Now let’s try Enigma Protector, open it, create new project, select the file to protect, enter product name and version, then click Protect button Code before obfuscation, almost same as original code Code after obfuscation. Let’s try dotPeek to see the changes in the code that we got after obfuscation. Click Protect! and wait until it finishes.Īs a result, we get folder “Confused” with the obfuscated exe file. On the Settings panel, select the file in the left panel and add protection rules. In ConfuserEx, we select the folder with executable to obfuscate and the executable file itself. net obfuscation tools, so let’s try to apply ConfuserEx. In most of the cases it is enough to use even free, open source. net code, so the first thing we have to do after compilation – obfuscate the file. ObfuscationĮnigma Protector does not obfuscate. Protected file will work well, but it is usually not enough to protect the application from being reverse engineered by advanced cracker. exe file and simply protect with Enigma Protector. Application has few fields, it asks user to enter degree angle value and then calculates angle sinus, cosine, tangent by button click.Īt this step we can compile the project to. Let’s start with the simple test Windows Forms C# application written in Visual Studio. So protection of such files with Enigma Protector (which is mainly designed for protecting of native applications) requires some more attention from developer. NET files are rather different than the native files that can be compiled with C++, Delphi, Pascal and others native compilators.NET files do not contain instructions (machine code) that are being running on computer’s CPU, they contain a data (set of instructions) to run on.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |