wcc

You're too optimistic about what it can do, here's a sample output: https://github.com/endrazine/wcc/wiki/wcch This is not what I'd call an "API dump"; all prototypes return void pointers and allow any arguments. Hence, it's just as much of a blackbox as the original executable is because you have no idea what the functions do, what arguments they take and what values they return.

I wonder how many folks are aware that ELF shared libraries and ELF executables are the exact same thing? There's no substantial compiling or decompiling necessary to go from shared object to executable and back. One need only add or remove the appropriate symbols from the object and (perhaps even optionally) change the object type. Have you ever tried to directly execute your libc.so.6 on a linux system? You can. There's nothing at all novel about this process, other than making it easy for folks who've never read the manual for their linker. Edit: Someone downvoted this observation; I imagine they think I'm unfairly trivializing this so I'll add: Read the source code. This tool we're discussing is a simple ~100 line program. It's not complicated: https://github.com/endrazine/wcc/blob/master/src/wld/wld.c

He is just missing the new witchcraft compiler wcc, which can unlink exes into shared libs, load those libs into your exe and inspect any function or variable. And then link it back into an exe. https://github.com/endrazine/wcc

The Witchcraft Compiler Collection is on github !! --[ url : https://github.com/endrazine/wcc --[ repo : https://github.com/endrazine/wcc.git --[ slides: http://tinyurl.com/jkxsg2u --[ All DEF CON demos : http://tinyurl.com/zaokau3 Open Source : MIT License Featuring : * Transforming ET_EXEC ELF executables into shared libraries * Unlinking ELF binaries into relocatable object files * Running OpenBSD binaries natively on linux * Using ET_DYN executables as shared libraries * Prototyping exploits from symbolic execution partial traces * In memory JIT translation from ARM to Intel x86_64 + debugging