Tag: object code

  1. Algebra of cracking: Vol.1

    If someone strips the debug info from an executable. It won't stop anyone who wants to hack it. And don't use embedded DEFINE macro also. Something like: #define FOO(x, y, result) \ do { \ do { \ --x; \ ++y; \ } while(x > y); \ result = x * y; \ } while(0) This definition shouldn't be used…

    on object code cracking

  2. Detect heap-based allocation in C

    In most cases `malloc`, `calloc` and `realloc` uses heap-based allocation when we are using libc. For the sake of this we need to check data for where it is allocated. How could you know that it is allocated by functions mentioned above? There is a little trick that you can…

    on c linkers loaders object code