TheSwamp
Code Red => .NET => Topic started by: nobody on February 17, 2014, 11:32:47 PM
-
Can anyone recommend software to do this? Still need the junk to work in autocad and civil 3d.
-
http://www.theswamp.org/index.php?topic=41844.msg469593#msg469593
My recommendation: Crypto Obfuscator
-
We use Dotfuscator for the SincpacC3D, but it is $$. I've used a free one for my personal projects that seems to do a nice job and is very easy to use....Eazfuscator.NET, the link for this is jar's link.
-
...a free one for my personal projects that seems to do a nice job and is very easy to use....Eazfuscator.NET...
Eazfuscator is no longer free :-(
-
Thanks all you rock (course you knew that already) :)
-
Eazfuscator is no longer free :-(
Bummer! Looks like you can still find the last free version, which will work as long as you don't need .NET 4.5: LINK (http://favsoft.blogspot.com/2012/08/eazfuscator-net-gone-commercial.html)
-
We use Dotfuscator for the SincpacC3D, but it is $$....
I am sorry, but the assemblies obfuscated with Dotfuscator can be easily deofuscated. It is obvious that not everyone knows how to do this, but maybe Dotfuscator is not the best option.
with ildasm.exe (http://msdn.microsoft.com/es-es/library/f7dy01k1%28v=vs.110%29.aspx):
(http://i.imgur.com/wN75t8j.png)
-
Its not free but I have used RedGate's SmartAssembly (http://www.red-gate.com/products/dotnet-development/smartassembly/) with success.
-
This: https://bitbucket.org/0xd4d/de4dot/ is the most easily-accessible de-obfuscator around so you may want to run your obfuscated code through it to see what it spits out. There are others around too like http://netdeob0.codeplex.com/ etc. Google is your friend (or not).
Everything can be cracked, you just want ot make it hard for the casual crackers. See also http://stackoverflow.com/questions/2525/net-obfuscation-tools-strategy and related questions.
Personally, I'd want to be running a lot of unit tests against obfuscated code, just to be a little more sure it doesn't break.
-
..
Personally, I'd want to be running a lot of unit tests against obfuscated code, just to be a little more sure it doesn't break.
Indeed. Once I found out that overloaded functions with the same number of parameters can be a problem for some obfuscator software. So you need to test everything. Even when you can't imagine the obvious functions would fail.
-
Using this now...really like it
http://www.rustemsoft.com/obfuscator.asp