Decoding stack trace of an obfuscated assembly

[Guest]

Hello, In order to protect our code we obfuscate it before every release using the Smart Assembly.The problem is that the obfuscation is different for each version. In this case - Will you be able to detect similar exceptions from different versions? What we would like to do is to decode the stack trace of each Exception before logging it. In my opinion the most appropriate place for work like this would be on your server. So is there any way to decode the stack trace of an exception before you actually log it into EQATEC Analytics? Thank you in advance for the assistance and for the great support you have provided so far. Regards, Rumen

[Guest]

Hi Rumen We've contemplated adding de-obfuscation into the exception handling pipeline for some time but have not yet found enough traction for it in our customer base. Adding such support is not a big thing conceptually but the overall issue is picking out which obfuscators (and thus de-obfuscation techniques) to support since there are a large number of 3rd party obfuscators, SmartAssembly being just one of these (we also use SmartAssembly on some of our other products, coincidently). Deobfuscation information is typically maintained in some xml structure and we'd have to develop some mechanism for storing/keeping these schemas on a per-release basis. So for now I'll just add your feedback to our existing item in the backlog and I hope to be able to make SmartAssembly the first obfuscator support when the time comes. Thanks for the feedback and keep sending questions and comments Regards Soren EQATEC Team

[Guest]

Added to FogBugz