This piece had potential but IMO was a bit disappointing. The entire thing could be summarized as:
1. "I used AI to download and analyze a firmware image, and found a way to unlock DEBUG mode."
2. "I didn't actually explore the DEBUG mode at all, but here are the commands the AI found for me (link)"
I'd love for the author to at least put in a little real effort, explore some of these debug commands, and tell us why they are interesting.
As this is - I find it to be very minimum-effort, AI-assisted blog-slop. Sorry!
(Now for the link[1] to the actual (unexplored) debug-commands... It has really weird casing of the descriptions in the "behaviour"-column. Does anyone know why that is?)
[1] https://inventor7777.github.io/brother-mfc-commands-list.htm...
Seriously, this article is so fucking dull. So are most security or programming write-ups these days. "ChatGPT said this, Claude did this..." Same thing with that Switch 2 exploit. I so dearly miss the days of hearing stories of people discovering things and actually solving problems, instead of just asking some LLM and copy-pasting the output with no understanding.
I'm sorry you found it dull. Like I said above, I admittedly did not spend a ton of time writing it, I honestly just wanted to show off what I found for more informational purposes rather than anything else. I'm not one of those incredibly talented writers who can write long coherent pieces about anything.
The weird casing seems to be a minimum accepted prefix for the keywords.
> As this is - I find it to be very minimum-effort, AI-assisted blog-slop. Sorry!
Don't be sorry, this is good feedback. Like you observed, I admittedly did not spend a ton of time writing it, I just wanted to show off what I found for more informational purposes rather than anything else. I'm not one of those incredibly talented writers who can write long coherent pieces about anything.