Notes on machine identity.
Short posts in plain words on certificates, keys and the machines that hold them, from the person building trstctl.
Every external fact links to its source. Every claim about trstctl links to the code or the design document it comes from, and is checked against the repository before it is published. Corrections are welcome as an issue on the trstctl repository.
Start here
All posts, newest first
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.
Self-hosted PKI and data residency
A certificate inventory is a map of your infrastructure, and the keys behind it are your infrastructure's identity. Where that data lives is a security decision and, in many places, a legal one. What leaves your network when certificate management is someone else's service, and what self-hosting has to guarantee to be worth it.
Proving a renewal happened
An auditor does not want to hear that renewals are automated. They want the record: who asked, who approved, what was issued, where it went, when it was verified, and proof the record has not been edited. What that evidence looks like when it is the system's own state.
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.
Six-day and IP certificates: what they are for
Let's Encrypt now issues certificates that live under a week and certificates for bare IP addresses. Neither is a curiosity. What each one is for, what it costs to run, and the profile menu that lets you choose.
A private CA in an afternoon
The certificates the public web cannot issue, for internal names, private addresses, client authentication and offline networks, need an authority you run. The tree, the ceremony, the constraints, and the one step that takes a quarter rather than an afternoon.
Post-quantum for the rest of us
Half the web's traffic already uses post-quantum key exchange, and not one public certificate does. What that split means, what to do now, what not to do, and why the hard part is the one nobody has shipped.
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.
Revocation is dead. Long live short lifetimes.
The largest certificate authority switched off OCSP. Chrome stopped asking long ago. Firefox replaced it with a local list. The industry's honest answer to a revocation check that never worked is a certificate that expires before anyone needs to revoke it.
What an MSP does with 300 customers' certificates
For a managed service provider the 47-day schedule is not a chore, it is a capacity problem: a book of business becomes tens of thousands of renewals a week. What one control plane for many customers has to guarantee, and the isolation you can prove rather than promise.
The wildcard six teams share
One certificate, six owners, zero accountability, and from 2029 twelve simultaneous renewals a year across every host that holds a copy. What a wildcard really is, when it is still the right tool, and how to stop it being the outage nobody can explain.
Let the CA tell you when to renew
ACME Renewal Information is the small protocol extension that turns renewal from a guess into an instruction: the authority publishes a window per certificate, and can pull it forward when something goes wrong. Why a cron job is the wrong tool, and what to do instead.
Renewal is not deployment
The certificate renewed. The endpoint is still serving the old one. The five places a new certificate has to reach, why each one is different, and the check that tells you it got there.
What breaks on 15 March 2027
The 100-day step is the first one that kills quarterly change tickets, 30-day expiry alerts, and manual domain validation. A dated checklist for the next cut in the schedule.
Your certificate inventory is wrong. Find out by Friday.
Three sources of truth that never agree: the public transparency logs, a scan of your own network, and the hosts themselves. A one-week method for finding the certificates nobody wrote down, and giving each one an owner.
Stop buying certificates. Start owning renewals.
A public TLS certificate has been free for ten years. What you are still paying for, whether you buy it or not, is the renewal. What free already covers, where a purchase still makes sense, and the five jobs that are yours either way.
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.
Why the signer is a separate process
Automation has to sign certificates all day. It should never hold the keys. How trstctl draws that line, what the line guarantees, and what it does not, with links to the code.
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.
47 days: what actually changes
The CA/Browser Forum has cut the lifetime of a public TLS certificate to 47 days by March 2029, and the proof that you own a name to ten days. The schedule, what breaks, and the four moves that make it a non-event.