Critical Infrastructure Is Maintained by People You Have Never Heard Of
I write about the maintenance work behind infrastructure security and the people doing it.
I keep technical articles, research notes and public reasoning here so I can revisit the implementation details, policy arguments, disclosure work and engineering decisions later.
Read time starts with a base speed by writing type then is adjusted for headings, text breaks, code blocks, tables and images.
Notes use 230 WPM, articles use 210 WPM and research or PoC work uses 190 WPM as their base speed. The final estimate is rounded up to the next minute.
RSS lets you follow this writing in a feed reader without checking the site manually. The feed is available at steadytao.com/rss.xml.
If my writing, maintenance work or technical notes are useful to you, GitHub Sponsors is the clearest way to support more of it.
Open GitHub Sponsors7 results, no filters active
I write about the maintenance work behind infrastructure security and the people doing it.
I explain why age assurance creates identity and privacy infrastructure even when it is introduced as a child-safety check.
I explain how modern DNS carries connection policy, privacy bootstrap material and edge configuration and what that means for operators and tooling.
I trace the path from name resolution to the first HTTP request and explain why DNS now helps bootstrap transport, protocol and privacy decisions.
My high-level write-up on CVE-2026-33825, its public disclosure and why I considered the Defender local privilege escalation urgent.
I explain why inventory, discovery and readiness come before algorithm replacement.
I use a Caddy case study to explain why RFC compliance alone does not settle implementation strategy.
Try removing one or more filters or adjust the search query.