Just want to make it a little harder.changing function names etc can add dramatically to reverse engineering I would think
Anthony Melbourne StuffUps.learn from others, share with others! http://www.meetup.com/Melbourne-Ideas-Incubator-Stuffups-Failed-Startups/ ---------------------------------------------------------------------------- ------ NOTICE : The information contained in this electronic mail message is privileged and confidential, and is intended only for use of the addressee. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. (*13POrtC*) ---------------------------------------------------------------------------- ------- From: [email protected] [mailto:[email protected]] On Behalf Of Joseph Cooney Sent: Wednesday, 27 November 2013 12:46 PM To: ozDotNet Subject: Re: dotnetobfuscator All managed code obfuscation can be broken, usually fairly easily. Mixed mode C++ /CLI for your IP sensitive code is one option, but to a determined reverse engineer even un-managed code is no big deal. The cost of protection should be in line with the value of the IP you're trying to protect. Joseph On Nov 27, 2013 11:37 AM, <[email protected]> wrote: Looking at obfuscating my code..anyone recommend a an easy\cheap solution? Is a dotnet 4 app harder to reverse engineer than a dot 3 for example? Anthony Melbourne StuffUps.learn from others, share with others! http://www.meetup.com/Melbourne-Ideas-Incubator-Stuffups-Failed-Startups/ ---------------------------------------------------------------------------- ------ NOTICE : The information contained in this electronic mail message is privileged and confidential, and is intended only for use of the addressee. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. (*13POrtC*) ---------------------------------------------------------------------------- -------
