Suggestion: Patch Friendly Settings

.NET obfuscator and automated error reporting

Suggestion: Patch Friendly Settings

Postby mclarke » Wed May 23, 2012 10:06 am


We use binary patches for our application - I noticed in the EAP forum a similar question was asked: ... hp?t=11010

I'm finding that our binaries are changing quite a bit, even with a small degree of change (~75%). I would find it useful, if I was able to specify that small changes to the code base resulted in smallish changes to the compiled binary.

Thanks for your time,
Posts: 6
Joined: Wed Feb 01, 2012 3:33 pm

Postby james.billings » Thu May 24, 2012 12:45 pm

Thanks for your post.

I don't think we've put any changes in to specifically assist in this scenario.

Many of the options in Smartassembly will stop you from subsequently post-processing the assembly. At a basic level, a binary diff of both assemblies *after* processing may work okay depending on the options you have selected, but the points raised in the previous post will still stand (in that a small change in the pre-obfuscated code could cause quite a large change to the resulting assembly once processed)
Posts: 1122
Joined: Wed Jun 16, 2010 10:10 am
Location: Red Gate

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 0 guests