Machine identity
Beyond TLS: SSH certificates, secrets, client certificates, workload identities and AI agents, all moving to short lifetimes.
Harvest now, decrypt later: the quantum attack that starts before the computer exists
Anyone who records your encrypted traffic today can read it once a large enough quantum computer exists. What a recording exposes, how to tell whether it matters to you, the setting that fixes it, and the hardening habit that quietly turns it off.
Client certificates after the EKU split
Chrome is separating the public web's certificate hierarchy into server authentication only, and Let's Encrypt has stopped issuing certificates that can authenticate a client. If you used a public certificate for mutual TLS, that path is closing. Here is what replaces it.
AI agents need badges, not API keys
Agents appear fast, act with real privileges, and call other systems that call other systems. A long-lived API key in a config file is the wrong credential for that. What an agent's identity should look like, and how a delegation chain keeps every hop narrower than the last.
SSH keys are the certificates you forgot
Every server has a file of public keys that grant standing access, added by people who have since left. SSH certificates replace the file with one authority and a short-lived note per login. How they work, what OpenSSH already supports, and what changes.
Machine credentials beyond TLS
The 47-day schedule is the visible tip of a bigger shift: every credential a machine holds is moving to short lifetimes. SSH, secrets, tokens, workload identity, code signing and now AI agents, and why one inventory beats seven.
PKI in plain words
Certificates, private keys, authorities, chains, domain-control validation, ACME, expiry, revocation and transparency logs, explained for someone who owns more certificates than they can name.