Technical writing on software engineering, systems design, and the tools that make it possible.
Part 1 left one question open: does the RLS timing oracle survive the network? Against a live Supabase PostgREST API it does. Paired requests cancel jitter, and the network path only sets the price in requests.
Postgres row-level security guarantees the result set, not the execution time. LEAKPROOF operators let the planner visit withheld rows before the policy runs, and range predicates turn that timing difference into a binary search. Auto-generated REST layers hand ordinary clients exactly those predicates.
Constrained decoding guarantees a model's output has the right shape. It guarantees nothing about what a free-text field holds. Agent-to-agent pipelines that read schema-valid as validated inherit an injection surface the schema was never built to close.
RFC 9849 finalizes Encrypted Client Hello, encrypting the one field most enterprise firewalls used to inspect encrypted traffic. What breaks, what still works, and how to rebuild detection without reviving blanket TLS interception.
A four-stage PoC — from a benign tool registration to one agent exfiltrating a second, more privileged agent's secrets — shows how AI agents bridge systems using authority they already legitimately hold, bypassing lateral-movement defenses built for network paths and stolen credentials.
Encryption secures the ciphertext. The schema answers questions the privacy contract never considered — sharing graphs, behavioral timelines, search-token frequency maps. How to read a database the way an attacker does.