x86 Software Reverse-Engineering, Cracking, and Counter-Measures by Stephanie Domas & Christopher Domas

Author:Stephanie Domas & Christopher Domas [Domas, Stephanie & Domas, Christopher]
Language: eng
Format: epub
ISBN: 9781394199891
Publisher: Wiley
Published: 2024-02-06T00:00:00+00:00

The choice of whether to use static or dynamic linking depends on the developer or the compiler. But putting your software cracking hats on, both options have their security implications.

Reverse engineers typically prefer that an application be statically linked. Static linking makes it easier to determine the exact load address of shared library functions, which is useful when crafting exploits. It means you can leverage code in the shared libraries to perform your exploitation, and that code will be at a predictable location inside of your binary at runtime. Leveraging a library that is linked dynamically is possible, but it is much more difficult because of the need to search for the desired library in the shared library memory and locate its address every single time, as it will move and be unpredictable.

Crackers, on the other hand, tend to prefer dynamically linked libraries. Dynamic linking results in much less code to sift through, and crackers are interested solely in an application's custom code, not the shared library code.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.