Software Protection
-
I was just wondering what you guys are using to protect the applications written in any language under the .Net Framework. Do you prefer the exe packers and crypters, or some other schemes? Which scheme is the best to implement, and presents a good ratio between a price/time to implement/protection it offers? Thanks.
-
I was just wondering what you guys are using to protect the applications written in any language under the .Net Framework. Do you prefer the exe packers and crypters, or some other schemes? Which scheme is the best to implement, and presents a good ratio between a price/time to implement/protection it offers? Thanks.
Hi Damir, Its realy difficult to protect a .NET Application, because the application is only IL-Code (with a win32 loader) and you can recreate the code of it really good. Try Lutz Roeder's Reflector[^], for instance with the System.dll (Framework Namespace System). One solution is to use a obfuscator. The obfuscator renames all variables and methodes in useless terms, like a12423. But a have no tip for a special product. A communication version (free for students and freeware authors) of the dotfuscator is part of visual studio 2003. See: http://preemptive.com/products/dotfuscator/Editions.html[^] A free alternative is the Aspose Obfuscator/[^]. An other idee is to pack all used dll's in one stream and embedded this stream as embedded resource in the application. Unpack this stream at runtime and load the dlls from this unpacked memory. Its simple possible to crypt the embedded stream. A example implementation is descript in the magazin Dr. Dobb's Journal March 2005. Reducing the Size of .NET Applications[^] Hope, it's help a bit Niedzi
-
Hi Damir, Its realy difficult to protect a .NET Application, because the application is only IL-Code (with a win32 loader) and you can recreate the code of it really good. Try Lutz Roeder's Reflector[^], for instance with the System.dll (Framework Namespace System). One solution is to use a obfuscator. The obfuscator renames all variables and methodes in useless terms, like a12423. But a have no tip for a special product. A communication version (free for students and freeware authors) of the dotfuscator is part of visual studio 2003. See: http://preemptive.com/products/dotfuscator/Editions.html[^] A free alternative is the Aspose Obfuscator/[^]. An other idee is to pack all used dll's in one stream and embedded this stream as embedded resource in the application. Unpack this stream at runtime and load the dlls from this unpacked memory. Its simple possible to crypt the embedded stream. A example implementation is descript in the magazin Dr. Dobb's Journal March 2005. Reducing the Size of .NET Applications[^] Hope, it's help a bit Niedzi