A ctlplne studio product
Topic · 9 posts

PKI fundamentals

Certificates, keys, authorities, validation and revocation, in plain words, for people who own more certificates than they can name.

  1. 22 October 2026 · 5 min read

    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.

    Post-quantumMachine identityPKI fundamentals

  2. 22 October 2026 · 3 min read

    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.

    PKI fundamentalsMachine identityPrivate PKI

  3. 22 October 2026 · 3 min read

    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.

    Private PKIPKI fundamentalsKey protectionSelf-hosting

  4. 22 October 2026 · 5 min read

    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.

    Post-quantumPKI fundamentalsPrivate PKI

  5. 22 October 2026 · 3 min read

    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.

    PKI fundamentalsThe 47-day schedulePrivate PKI

  6. 22 October 2026 · 3 min read

    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 automationThe 47-day schedulePKI fundamentals

  7. 21 September 2026 · 6 min read

    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.

    Renewal automationThe 47-day schedulePKI fundamentals

  8. 21 September 2026 · 5 min read

    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.

    PKI fundamentalsKey protectionMachine identity

  9. 21 September 2026 · 5 min read

    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.

    The 47-day scheduleRenewal automationPKI fundamentals