This project is read-only.


Jan 26, 2010 at 3:00 AM

how about code obscuration?

Jan 26, 2010 at 10:13 AM
Edited Jan 26, 2010 at 10:17 AM

Please remember that primary purpose of Exepack is to simplify deployment. It is not intended to be a protection tool. Protection is just a side effect :)

For code obfuscation I personally recommend using Eazfuscator.NET. It offers wery well protection with lots of advanced obfuscation techniques (including control flow obfuscation, class hierarchy linearization, etc). Best of all, it's completely free (although not open-source). 

Jan 26, 2010 at 11:44 AM
thanks for you detail reply. maybe not now, but in the future, your
ExePack.Net might support obscuration;)

Jan 26, 2010 at 12:29 PM

Basic obfuscation (i.e. symbol renaming) doesn't seem to be very difficult to implement. Maybe I should investigate it for some of the upcoming releases. Thanks for the suggestion!

Jan 26, 2010 at 2:53 PM
right, symbol renaming is really useful. flow control, however, seems
more diffcult to implement

Jan 28, 2010 at 9:53 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.