Infrastructure Patterns and Recon: How Systems Betray Themselves
A technical method for turning DNS, certificate logs, code, and client-side clues into testable infrastructure hypotheses without confusing correlation with ownership.
My degree is in Electronics Engineering, and my day job is in ops. These are the questions I keep coming back to: radio links, web security, infrastructure, and the occasional economic model.
A technical method for turning DNS, certificate logs, code, and client-side clues into testable infrastructure hypotheses without confusing correlation with ownership.
A practical derivation of wavelength, antenna gain, path loss, noise, multipath, and what a radio link budget can actually tell a security researcher.
A production-possibilities model for semiconductor design, fabrication, packaging, and the bottlenecks that make simple zero-sum stories misleading.
A close look at cron's privilege boundary: path resolution, file ownership, shell behavior, race conditions, safe auditing, and how to design jobs that do not inherit writable code.