is this like the ultimate form of "headline is all you need"?
I came here wanting to see after-action-report of someone actually using Ai or wtvr for reverse-engineering. Instead I got "I heard it was so. The end"
For example, just yesterday I reverse engineered the internal API of a SAAS tool we use and it allowed me to gain programmatic access to data that was only available in their slow clunky UI.
Doing the same by hand can be really time consuming and difficult depending on how many obfuscation measures are layered on top.
Maybe he had a particular audience in mind when he wrote it. An audience for whom the mere realization would rock the foundations of their stolid and boring lives.
On the other hand, I’ve watched the movie Paycheck (2003), so my imagination has a high bar before it’s rocked by mere suggestion. Therefore, I wonder why the OP user @edward thought it was worthy of our attention.
I expected to read their excited engagement with others here, but alas no. It’s a mystery.
Various firmware bugs that I’m sure could be fixed but aren’t, because they don’t bug the manufacturer enough? But they certainly bug me on a daily basis.
Also this weekend I found out that Claude is better at writing Home Assistant automations than I am and I have been doing it for years.
The multiplier comes from being able to design arbitrary fast feedback loops - Claude wrote Python scripts to do decompilation matching for itself, and then use Frida traces from the original as a verification harness.
There's no way to make a profit off reverse engineering home devices so I expect while this is likely to be one of the most groundbreaking impacts of LLMs, it won't see a ton of adoption until token costs come down.
Send $20 pi zero that will reflash expensive camera, that is out of support. Or do mail business, with reflashing devices.
There are billions out of support devices, and rework is great industry in China. In US you sadly hit legal BS if doing it commercially...
Human-written API documentation, on the other hand, tends to be inconsistent in quality
So I use AI for exactly what Simon’s post discusses, and am thrilled to be able to rid myself of crap software written by device vendors, and make the devices work without my stuff.
But well, any documentation is good when a human would've written zero docs
AI's verbosity is definitely a problem, but I think it's something you can just check once more. Of course, opinions vary.
You can reverse engineer websites at a breathtaking speed if you do it correctly. PeachJam.dev took me approximately 2 months to make, for instance. If I had access to Sol from the start it would likely just take 1 month.
Software license/key verification. Sometimes it’s as easy as replacing a “JNE” with a “JE”, or replacing “JMP”, or even just “NOP” some “CMP” operation. It’s a fun challenge, at least for people who enjoy solving puzzles.
e.g. why do I need V380 app to configure and watch the feed of my IP Camera.