E
Ed Sutton
I am a .NET newbie and I just ran ILDASM on my executable and I am
freaked-out about how easy it is. Is the only real solution to fork over
$2000 and purchase Salamander .NET Protector?
How can a company that values it's intellectual property so highly not have
a secure solution for this? Will Microsoft ever produce a new version of
Microsoft Office using it's own .NET language tools if disassembly is this
easy?
I see vendors selling software that produce re-compilable source code from
ANY *.exe or *.dll. I found others selling .NET code obfuscators and
encryption packages.
Review: RemoteSoft Explorer, Decompiler, Obfuscator and Protector
http://www.eggheadcafe.com/articles/20021213.asp
http://www.remotesoft.com/salamander/protector.html
The following article talks about protecting from disassembly using ILASM to
set an owner. I get a gut feeling that this is easy to crack.
http://www.dotnetextreme.com/articles/protectIL.asp
Has anyone out there released a commercial application using .NET? Do you
mind if I decompile your code?
-Ed
freaked-out about how easy it is. Is the only real solution to fork over
$2000 and purchase Salamander .NET Protector?
How can a company that values it's intellectual property so highly not have
a secure solution for this? Will Microsoft ever produce a new version of
Microsoft Office using it's own .NET language tools if disassembly is this
easy?
I see vendors selling software that produce re-compilable source code from
ANY *.exe or *.dll. I found others selling .NET code obfuscators and
encryption packages.
Review: RemoteSoft Explorer, Decompiler, Obfuscator and Protector
http://www.eggheadcafe.com/articles/20021213.asp
http://www.remotesoft.com/salamander/protector.html
The following article talks about protecting from disassembly using ILASM to
set an owner. I get a gut feeling that this is easy to crack.
http://www.dotnetextreme.com/articles/protectIL.asp
Has anyone out there released a commercial application using .NET? Do you
mind if I decompile your code?
-Ed