Skip to main content
Be Bitwise

Why Reverse Engineer?

Reverse Engineering Basics · Reverse Engineering track

3 min read

In this module

Looking Under the Hood

This course has been pulling computers apart from the ground up: binary, assembly, memory, the OS. Reverse engineering runs the same machine in reverse. You start with a compiled binary and figure out, byte by byte, what it does and how. You've got the assembly chops from Assembly Language and the memory model from Memory Fundamentals through Addresses & Pointers. Time to point them at real-world code.

Why Reverse Engineer?

Reverse engineering keeps showing up in serious computing work for a handful of reasons.

Malware analysis is the canonical example. When a new sample lands on a researcher's desk, nobody wants to run it on production. So you crack open the binary, trace its logic, and document the behaviour: how it phones home, what it exfiltrates, how it digs in for persistence.

Vulnerability research lives in the same toolkit. When source isn't available, which is most of the closed-source, firmware, and embedded world, the only audit you can do is on the binary itself. The exploit work in Exploit Development & Real-World Impact rests on this skill.

Interoperability is the friendlier cousin. Sometimes the only way to talk to a system is to figure out a protocol or file format the vendor never documented. Samba famously reverse-engineered Microsoft's SMB so Linux machines could join Windows file shares.

Legacy system maintenance sneaks up on organisations more often than you'd think. Source goes missing, the original devs leave, the build system rots. If the system is mission-critical, sometimes you reverse engineer your own binaries because there's no other option.

Legal Considerations

Reverse engineering legality varies by jurisdiction. In the United States, the DMCA restricts reverse engineering of copy protection mechanisms but provides exceptions for interoperability and security research. Many other countries also provide fair-use exceptions. Always understand the legal framework in your jurisdiction before reverse engineering software you do not own.

The Reverse Engineer's Mindset

Reverse engineering is detective work. You begin with almost nothing, just a stream of bytes, and slowly build a picture. You guess what a function does, check by reading the code that calls it, then revise the guess. Patience, pattern recognition, and a high tolerance for ambiguity are the load-bearing skills. The assembly fundamentals you've already built are the floor under all of it.

A first look at an unknown binary usually starts with three questions: what is it, what does it call, and where does input go? The cheapest tool for the first two is strings, which prints every run of printable bytes in the file. The runner below is a toy crackme that runs its own little strings over its own executable. Before you run it, guess whether the password survives compilation in a form you could read.

Try itFind the password and the library calls in the output, then build the key at run time from two halves and see what's left to find.
C (GCC 9.2.0)

Among the noise (short runs that happen to be printable bytes inside machine code) you'll find the key in plain text, the two messages, and imported function names like strcmp and puts. That last group answers "what does it call" before you've read a single instruction. Where input goes is the question that needs a disassembler, which is the next lesson.