How are you protecting your dot net apps from reverse engineering?

[Robert Johnson]

Hi all. I was wondering if you are just relying on the dotfuscator that is
included in VS2005 or do you use another method to protect your apps from
reverse engineering?

TIA

Robert

 

[Jason Hales]

I think Preemptive's .NET Obfuscator is one of the most popular
(probably due to inclusion of the community edition).

The Professional edition does an excellent job but I've only worked at
one place that could afford nearly $2000 for a license.

I've heard good things about RemoteSoft's Salamander obfuscator but
haven't used it myself - it's also much cheaper than Preemptive's
http://www.remotesoft.com/salamander/obfuscator.html

 

[Robert Johnson]

Thanks for the reply and link Jason.

Robert

 

[info]

Try Xenocode Postbuild. I like it a lot!!!

 

[Kevin Spencer]

Anything can be decompiled. Therefore, my strategy is to continually stay
ahead of the competition in terms of what I create. As long as I keep moving
forward, anything that might be copied or stolen from me is already obsolete
in my toolbox.

Just a thought.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

 

[Robert Johnson]

Thanks for the info.

Robert

 

[Robert Johnson]

Good point Kevin... but you have to try.

Robert

Anything can be decompiled. Therefore, my strategy is to continually stay
ahead of the competition in terms of what I create. As long as I keep
moving forward, anything that might be copied or stolen from me is already
obsolete in my toolbox.

Just a thought.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

 

[Kevin Spencer]

Good point Kevin... but you have to try.

You mean *you* have to try. I certainly don't have to, and I don't.

--
;-),

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

 

[Huihong]

What protection measures to take really depends on your comfort level.

If you think "well, I better do something", then obfuscators are fine,
defending casual users.

If you think "God, I really need to protect my code", then try native
compilation.

I wrote my salamander decompiler in java languages, before release, I
tried obfuscation, but didn't meet my goals, so I converted java source
code to C++ (for this I developed our java to C++ Octopus translator),
and recompiled it to native executables. Today, I still develop in Java
for the decompiler, but generate native code for release.

This is made possible for C#/VB.NET/MC++, with our native compiler:

http://www.remotesoft.com/linker

Huihong

 

[LogicNP]

The one including in VS is very limited - use others like Crypto Obfuscator - many settings for code obfuscation and effective.