![]() NET Common Language Runtime (CLR) constitutes a COM object and as such may be hosted by any Windows unmanaged application. In chapter 20 entitled CLR Hosting, AppDomains, and Reflection the author explains that. NET Framework Programming by Jeffry Richter – an excellent one!) already provides a good hint to a better protection of managed code. NET book I read back in year 2002 (Applied Microsoft. But this list is definitely not exhaustive - many more articles and posts (especially published on Stack Overflow site) were used. Some of them are referenced at the end of the article. This work is based on previous articles and code of other authors. The article presents an approach illustrated with code sample, that allows developers to thwart direct attempts to reveal their managed code by reflection of their executable files. But obfuscation is a problematic solution since in this case code is normally readable with reflectors, application logic is preserved intact and, even more important, may disrupt reflection usage by the application itself. Other people try some palliative means for code protection, like e.g., obfuscators. However, nowadays code placed on public cloud may require protection also. ![]() Some people argue that most of the managed executables may be placed on server side, out of customer reach. In fact, most of the developers have accepted the situation when everybody can effortlessly reveal original code by its binaries, as inevitable toll for benefits of managed code usage. NET executables, politely asking user in what language he/she'd like to get original code. And indeed, Lutz Roeder’s Reflector and many reflectors that followed, crack. NET, it had become a common place that managed binaries were easy target for reverse engineering via reflection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |