June 23, 2019
Sigh. This blog is about reverse engineering. Initially it will be about software reverse engineering (SRE), eventually it will lead into hardware reverse engineering (HRE).
Why would people read this blog? Not too sure. Probably some sort of interest in working out how something works. Which could be for many reasons:
- fun (this is why I do it)
- working to get exploits up
- subverting malware
- producing a compatible product
- see how binaries and machines are put together
- learning how to protect software from people like yours truly
Be careful if you plan to do it for profit, for most types of such activities there are laws against it.
I’ll start by providing some pointers regarding getting NSA’s Ghidra up and running in a useful way. This is boring, I know. But fair cop, you need to know your tools if you want to be a professional reverse engineer.
Then, I’ll introduce some dynamic debugging techniques using GDB’s python API.
Then I’ll demonstrate extending Ghidra to do some programmatic SRE.
Then I’ll fuse dynamic debugging using GDB and Ghidra.
All boring things I know. Give me time. The next thing is embarking on a journey of teaching by way of doing. I’ll be working to reverse engineer hidden keys from withing illegitimate software. Note doing such things against legitimate software is just as fun, but you can’t publish that shit. Ok, ok, you can, but shiiiiiiiiiit have fun with that.
Please don’t hack this site. I’m not very good at protecting things, that is not approval to take my stuff and fuck it up.
I’ll buy a case of beer for anyone for each hole in the site they help me close.
Written by Dan Farrell who lives and works in Seattle tinkering away on firmware. To subscribe send an email to firstname.lastname@example.org.