WARNING: Readers will be educated. Survivors will be educated again.
-
Decompiling Tenchu: Stealth Assassins part 9: rescue the debugging data
-
Decompiling Tenchu: Stealth Assassins part 8: make-believe executable for PSX.SYM
-
Decompiling Tenchu: Stealth Assassins part 7: the AFSMAKE.EXE side-quest
-
Decompiling Tenchu: Stealth Assassins part 6: archive adventures
-
Decompiling Tenchu: Stealth Assassins part 5: memory mismanagement
-
Decompiling Tenchu: Stealth Assassins part 4: juggling executables
-
Decompiling Tenchu: Stealth Assassins part 3: setting up a Ghidra server on a cheap Synology NAS
-
Decompiling Tenchu: Stealth Assassins part 2: grabbing the files
-
Decompiling Tenchu: Stealth Assassins part 1: what's decompiling?
-
Decompiling Tenchu: Stealth Assassins: introduction
-
Porting the Atari Jaguar SDK part 5: I have a feeling we're not on Linux anymore
-
Porting the Atari Jaguar SDK part 4: where we're going, we don't need the C standard library
-
Porting the Atari Jaguar SDK part 3: makin' elves
-
Porting the Atari Jaguar SDK part 2: abusing Ghidra's version tracking tool for fun and profit
-
Porting the Atari Jaguar SDK part 1: loading executables into Ghidra the hard way
-
Porting the Atari Jaguar SDK: introduction
-
The taxonomy of delinking, or how I misnamed the unlinking technique
-
Reverse-engineering part 10: with a little help from my extension
-
Reverse-engineering part 9: look Ma, no relocations!
-
Reverse-engineering part 8: baby's first steps with delinking
-
Reverse-engineering part 7: setting up the stage for delinking (training wheels edition)
-
Reverse-engineering part 6: crash course on binary patching with Ghidra
-
Reverse-engineering part 5: old-school binary patching
-
Reverse-engineering part 4: running our case study
-
Reverse-engineering part 3: introspecting with the toolchain
-
Reverse-engineering part 2: building our case study
-
Reverse-engineering part 1: the toolchain workflow
-
Reverse-engineering: introduction