Systems1 min read
Read the bytes
If you cannot follow a buffer, a pointer, and a calling convention, you are commenting on security — not doing it.
Avdi Ajeti · Ajetonix
Most security writing starts at the tool. Burp here, nmap there, a screenshot of a dashboard. Useful, until the bug lives one layer down and the dashboard has nothing to say.
The weekly C work is not nostalgia. It is how I keep the lower layer readable: types, layout, who owns a pointer, what happens when a length is a lie.
Read the bytes. Then write the note. The other order produces fiction.
Also in the feed