Conflict of Interest : Reflector and SmartAssembly

Conflict of Interest : Reflector and SmartAssembly

Postby rdhatch » Wed Feb 02, 2011 5:30 pm

In separate acquisitions - RedGate now owns both Reflector and Smart Assembly obfuscator.

One Question: How is developing both Reflector and Smart Assembly not a conflict of interest?

Thank you -

Ryan D. Hatch
rdhatch
 
Posts: 1
Joined: Wed Feb 02, 2011 5:21 pm

Re: Conflict of Interest : Reflector and SmartAssembly

Postby JDelekto » Sun Feb 06, 2011 2:25 am

rdhatch wrote:In separate acquisitions - RedGate now owns both Reflector and Smart Assembly obfuscator.

One Question: How is developing both Reflector and Smart Assembly not a conflict of interest?

Thank you -

Ryan D. Hatch


Greets,

Having both a tool which 'decompiles' as well as a tool which obfuscates is not really a conflict of interest.

If they added the ability to 'de-obfuscate' code into Reflector which had knowledge of their obfuscation would be more of a feature than it would be a threat; I say so because it would not require people using other obfuscators to have to drag and drop obfuscated stack traces into tools to see exactly where a problem exists. (If they even get that input.)

Obfuscation is just that, it makes an assembly difficult to understand. Owning a tool which can decompile is usually thwarted by some obfuscation attempts --to the point it may cause them to crash.

If you ask me, it sounds like a good marriage of products --a way to obfuscate code and a way to debug through the obfuscation. Of course, one would have to have: a) the PDB files; and b) a version of Reflector that could de-obfuscate.

Cheers.
JDelekto
 
Posts: 21
Joined: Sat Feb 05, 2011 2:36 pm


Return to .NET Reflector 7.0 Feedback

Who is online

Users browsing this forum: No registered users and 0 guests

cron