Thanks you all for your answers. AOT'in the app and then removing the IL code sounds like a nice nice tradeoff, I am going to have a deeper look in that direction. As suggested, I might also consider embedding some parts of our current codebase in C++ for performance reasons (real impact is still to be evaluated and porting them to mono also offers some advantages).
Your help was much appreciated. Thanks again > Date: Mon, 25 Oct 2010 15:42:45 +0100 > Subject: Re: [Mono-list] How to protect a mono application from reverse > engineering? > From: [email protected] > To: [email protected] > CC: [email protected]; [email protected] > > Just to expand on jonathans answer, you can strip all the method > bodies from your assembly once you AOT. The tool you're looking for is > 'mono-cil-strip'. It's as simple as AOT'ing your assembly and then > running: mono-cil-strip in_file out_file. Anyone who decompiles the > binary will end up seeing a bunch of class names and method names, but > nothing inside the methods. That should be enough to dissuade all but > the most dedicated people. >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
