Conflict of Interest : Reflector and SmartAssembly

• 

  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 February 05, 2011 20:25

  - 0 +

Add comment

Please sign in to leave a comment.