Saltar al contenido ForoHackers

Reverse engineering: start here

Ingeniería inversa
#783 · Ophuscado · · Denunciar

Reverse engineering is working out how something was built from the finished product, usually a compiled program with no source. It is used to understand file formats, check software for flaws, recover lost documentation, and study malware. Work on your own programs, training challenges and CTFs, and check the law and licences that apply to you.

Key concepts

  • From machine code back to meaning: a disassembler shows instructions; you rebuild functions, data types and intent.
  • Compilers leave patterns: loops, calls, switch tables and stack frames look the same across programs, and you learn to recognise them.
  • Static and dynamic views: read the code in a disassembler, then run it under a debugger to confirm.
  • Calling conventions and ABIs: where arguments, returns and saved registers live.
  • Annotate as you go: renaming and commenting turns an unreadable listing into a model you can share.

Vocabulary

  • Disassembler and decompiler: tools that show machine code as assembly, or as approximate source.
  • Symbols: names of functions and variables, usually missing in release builds.
  • Breakpoint: a stop in a running program so you can inspect its state.
  • Obfuscation: deliberate effort to make code hard to read.

What to study, in order

  1. C and the way it maps to assembly: compile small programs and read the output.
  2. x86-64 or ARM assembly well enough to follow a function.
  3. Use a debugger on your own program: set breakpoints, read registers and memory.
  4. Open source disassembly and decompiler tools, applied first to your own binaries without symbols.
  5. Crackme-style training challenges, written for this purpose, with a short write-up of each.

Related tags

#binary-analysis #assembly #c #malware-analysis #compilers

Inicia sesión o únete para responder.