<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>PKI Zero to Hero: new chapters, guides and changes</title>
<link>https://pkizerotohero.com/</link>
<atom:link href="https://pkizerotohero.com/feed.xml" rel="self" type="application/rss+xml" />
<description>New and updated PKI Handbook chapters and how-to guides, and what is changing in PKI. Published by PKI Zero to Hero, by Duyutech BV.</description>
<language>en</language>
<lastBuildDate>Tue, 20 Oct 2026 08:00:00 GMT</lastBuildDate>
<item>
<title>Chapter 1: Symmetric encryption: one shared key</title>
<link>https://pkizerotohero.com/handbook/symmetric-encryption/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/symmetric-encryption/</guid>
<description>Symmetric encryption scrambles data with one secret key, and only someone who holds that same key can turn the scrambled data back into readable text.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 2: The key-distribution problem</title>
<link>https://pkizerotohero.com/handbook/key-distribution/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/key-distribution/</guid>
<description>A shared secret key must reach each partner without anyone else seeing it, and every pair needs its own key, so sharing secret keys does not scale.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 3: Key pairs: public and private keys</title>
<link>https://pkizerotohero.com/handbook/key-pairs/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/key-pairs/</guid>
<description>A key pair is two keys: a public key anyone may have and a private key only you hold, so strangers can encrypt to you without sharing a secret first.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 4: Key exchange and hybrid encryption</title>
<link>https://pkizerotohero.com/handbook/key-exchange/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/key-exchange/</guid>
<description>Two parties can agree a shared secret over an open network without ever sending it, then derive fast symmetric keys from it to protect the actual data.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 5: Hashes and fingerprints</title>
<link>https://pkizerotohero.com/handbook/hashes/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/hashes/</guid>
<description>A cryptographic hash turns any data into a short, fixed-size fingerprint; any change gives a completely different fingerprint, and you cannot run it backwards to get the data.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 6: Digital signatures</title>
<link>https://pkizerotohero.com/handbook/digital-signatures/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/digital-signatures/</guid>
<description>A digital signature is a value only the private-key holder can compute for a message, and anyone with the public key can check that it matches that exact, unchanged message.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 7: Whose key is it? Binding identity to keys</title>
<link>https://pkizerotohero.com/handbook/binding-identity/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/binding-identity/</guid>
<description>Encryption and signatures only help if you use the right person's public key, so something you already trust must vouch that a key belongs to a name.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 8: Anatomy of an X.509 certificate</title>
<link>https://pkizerotohero.com/handbook/x509-certificates/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/x509-certificates/</guid>
<description>An X.509 certificate is a public, signed record that ties one public key to names for a fixed period, and you can read every field with openssl.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 9: Names and jobs: SANs, wildcards, key usage and the CA flag</title>
<link>https://pkizerotohero.com/handbook/names-and-key-usage/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/names-and-key-usage/</guid>
<description>A certificate is valid only for the names in its Subject Alternative Name list, and only for the jobs that its key usage, extended key usage and CA flag allow.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 10: Asking for a certificate: key generation and the CSR</title>
<link>https://pkizerotohero.com/handbook/csr/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/csr/</guid>
<description>You generate a key pair, keep the private key, and send the CA a certificate signing request (CSR) carrying only your public key and the names you want.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 11: Proving you own the name: DV, OV, EV and CAA</title>
<link>https://pkizerotohero.com/handbook/domain-validation/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/domain-validation/</guid>
<description>Before issuing, a CA checks that you control each name, using a file, a DNS record or a TLS response, and reads CAA records; OV and EV check the organisation.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 12: Who do we trust? CAs, trust stores and self-signed certificates</title>
<link>https://pkizerotohero.com/handbook/trust-stores/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/trust-stores/</guid>
<description>Every client trusts only the root certificates in its own trust store, so a certificate is accepted only if its chain ends at one of them; being self-signed earns nothing.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 13: Certificate chains and path validation</title>
<link>https://pkizerotohero.com/handbook/certificate-chains/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/certificate-chains/</guid>
<description>Servers must send their leaf and intermediate certificates; clients link them by name and key identifier up to a trusted root and check every signature, date and constraint.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 14: Two roads to the same root: cross-signing and root expiry</title>
<link>https://pkizerotohero.com/handbook/cross-signing/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/cross-signing/</guid>
<description>Cross-signing gives one CA key two certificates from different issuers, so a chain can reach either an old or a new root; clients must pick a path that is valid.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 15: The TLS 1.3 handshake</title>
<link>https://pkizerotohero.com/handbook/tls-handshake/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/tls-handshake/</guid>
<description>In one round trip, client and server agree fresh keys with ECDHE, the server proves it holds the certificate's key by signing the handshake, and both confirm nothing was altered.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 16: Taking it back: CRLs, OCSP and stapling</title>
<link>https://pkizerotohero.com/handbook/revocation/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/revocation/</guid>
<description>Revocation lets a CA cancel a certificate before it expires, but many clients check late, softly or not at all, so short lifetimes now do much of the work.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 17: Certificate Transparency</title>
<link>https://pkizerotohero.com/handbook/certificate-transparency/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/certificate-transparency/</guid>
<description>Certificate Transparency records every publicly trusted TLS certificate in public, append-only logs, so anyone can spot a certificate for their name that they never asked for.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 18: Famous failures and what changed</title>
<link>https://pkizerotohero.com/handbook/famous-failures/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/famous-failures/</guid>
<description>Real PKI failures, from a hacked CA to expired certificates, follow one pattern: a weak point breaks trust, someone notices, and the rules or practices change.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 19: Inventory, expiry and renewal</title>
<link>https://pkizerotohero.com/handbook/certificate-lifecycle/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/certificate-lifecycle/</guid>
<description>Every certificate expires and lifetimes keep shrinking, so you need an inventory, an owner for each certificate, monitoring of what servers really send, and automated renewal.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 20: ACME and the 47-day schedule</title>
<link>https://pkizerotohero.com/handbook/acme/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/acme/</guid>
<description>ACME lets software prove control of a name, then fetch, renew and install certificates automatically: the only practical way to live with very short certificate lifetimes.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 21: Guarding the keys: HSMs and key ceremonies</title>
<link>https://pkizerotohero.com/handbook/hsm-and-key-ceremonies/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/hsm-and-key-ceremonies/</guid>
<description>A CA is only as trustworthy as its private keys, so they live in certified hardware, are created in witnessed ceremonies and are used only under multi-person control.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 22: A CA of your own: private two-tier PKI</title>
<link>https://pkizerotohero.com/handbook/private-ca/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/private-ca/</guid>
<description>A private CA lets you issue certificates for internal systems under your own rules, built safely as an offline root plus an online issuing CA with clear policies and templates.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 23: Both sides show ID: mutual TLS</title>
<link>https://pkizerotohero.com/handbook/mutual-tls/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/mutual-tls/</guid>
<description>In mutual TLS the client also proves who it is, with a certificate and a signature from its private key, so both ends are authenticated before any data flows.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 24: Signed and sealed: code and document signing</title>
<link>https://pkizerotohero.com/handbook/code-signing/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/code-signing/</guid>
<description>A code or document signature proves who signed a file and that nobody changed it since; a trusted timestamp keeps that proof valid after the signing certificate expires.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 25: Machines with passports: device identity</title>
<link>https://pkizerotohero.com/handbook/device-identity/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/device-identity/</guid>
<description>A device certificate, installed at the factory with its private key locked in secure hardware, lets a machine prove what it is and who made it, for its whole life.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Chapter 26: Post-quantum cryptography</title>
<link>https://pkizerotohero.com/handbook/post-quantum/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/post-quantum/</guid>
<description>A large quantum computer would break RSA and elliptic-curve cryptography, so key exchange is already moving to ML-KEM, and signatures and certificates come next.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Glossary: PKI terms in plain words</title>
<link>https://pkizerotohero.com/handbook/glossary/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/glossary/</guid>
<description>Every PKI and TLS term used on this site, from ACME to X.509, each with a one-line answer, a fuller explanation and the chapter that teaches it.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Cheat sheet: the certificate commands you actually need</title>
<link>https://pkizerotohero.com/handbook/cheat-sheet/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/cheat-sheet/</guid>
<description>Tested OpenSSL, curl, keytool, Windows and Kubernetes commands for everyday certificate work, grouped by the task you are trying to do.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>File formats: PEM, DER, PKCS #12 and friends</title>
<link>https://pkizerotohero.com/handbook/file-formats/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/file-formats/</guid>
<description>The formats are wrappings of the same data: DER is binary, PEM is DER in Base64, PKCS #12 bundles a key with its certificates, and PKCS #7 carries certificates only.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Timeline: how PKI got here</title>
<link>https://pkizerotohero.com/handbook/timeline/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/timeline/</guid>
<description>From the first public-key papers in the 1970s to ever-shorter certificate lifetimes and post-quantum key exchange: the milestones and incidents that shaped how certificates work today.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>Standards index: the rules behind every chapter</title>
<link>https://pkizerotohero.com/handbook/standards/</link>
<guid isPermaLink="true">https://pkizerotohero.com/handbook/standards/</guid>
<description>The RFCs, CA/Browser Forum documents, root program policies, NIST standards and EU rules that this handbook relies on, each with what it covers and where to read it.</description>
<category>Handbook</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to inspect a certificate with OpenSSL</title>
<link>https://pkizerotohero.com/guides/inspect-certificate-openssl/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/inspect-certificate-openssl/</guid>
<description>You will have read a certificate file or a server's certificate with OpenSSL and found its names, dates, issuer, key and fingerprint.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to check the certificate chain a server sends</title>
<link>https://pkizerotohero.com/guides/check-remote-certificate-chain/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/check-remote-certificate-chain/</guid>
<description>You will have listed every certificate a server sends, checked their order and links, and verified the chain with a strict client instead of a browser.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to check when a certificate expires, and monitor it</title>
<link>https://pkizerotohero.com/guides/check-certificate-expiry/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/check-certificate-expiry/</guid>
<description>You will have read expiry dates in files, live servers and certificate stores, and set up a check that warns before any certificate in a chain runs out.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to check that a private key matches a certificate</title>
<link>https://pkizerotohero.com/guides/check-key-matches-certificate/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/check-key-matches-certificate/</guid>
<description>You will have proved, without exposing the key, that a private key, its CSR and a certificate share one public key, or found the file that does not belong.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to create a key and a CSR with OpenSSL (with SANs)</title>
<link>https://pkizerotohero.com/guides/create-csr-openssl/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/create-csr-openssl/</guid>
<description>You will have a new private key that never leaves your server, and a verified certificate signing request that lists every name your certificate needs.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to create a CSR on Windows (certreq and IIS)</title>
<link>https://pkizerotohero.com/guides/create-csr-windows/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/create-csr-windows/</guid>
<description>You will have a CSR with all your names, whose private key stays inside the Windows key store, and know how to install the certificate when it returns.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to create a CSR with Java keytool</title>
<link>https://pkizerotohero.com/guides/create-csr-java-keytool/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/create-csr-java-keytool/</guid>
<description>You will have a key pair in a PKCS #12 keystore, a CSR whose SAN list really reaches the CA, and the signed certificate chain installed under the same alias.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to convert PFX (PKCS #12) to PEM and back</title>
<link>https://pkizerotohero.com/guides/convert-pfx-pem/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/convert-pfx-pem/</guid>
<description>You will have split a PFX into PEM files for the certificate, the chain and the key, or packed PEM files into a PFX that Windows and Java can import.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to convert between DER and PEM</title>
<link>https://pkizerotohero.com/guides/convert-der-pem/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/convert-der-pem/</guid>
<description>You will have identified whether a file is DER or PEM and converted certificates, keys, CSRs, CRLs and bundles between the two, with proof that nothing changed.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to convert a Java keystore (JKS) to PKCS #12</title>
<link>https://pkizerotohero.com/guides/convert-jks-pkcs12/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/convert-jks-pkcs12/</guid>
<description>You will have moved every key and trusted certificate from a JKS keystore into a standard PKCS #12 file that Java, OpenSSL and Windows can read, and updated your settings.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to build the full chain file your server needs</title>
<link>https://pkizerotohero.com/guides/build-fullchain/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/build-fullchain/</guid>
<description>You will have one PEM file with your certificate followed by its intermediates in the right order, verified offline and proven to work with a strict client.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to work behind a TLS-inspecting corporate proxy, safely</title>
<link>https://pkizerotohero.com/guides/corporate-proxy-certificates/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/corporate-proxy-certificates/</guid>
<description>You will have confirmed that your traffic is inspected, obtained your company's inspection root through a trusted channel, and made each tool trust it with verification still on.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to trust a private root CA on Windows</title>
<link>https://pkizerotohero.com/guides/add-root-ca-windows/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/add-root-ca-windows/</guid>
<description>Your Windows computer, or a whole fleet, trusts your organisation's private root CA, and you know which apps still need their own setting.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to trust a private root CA on macOS</title>
<link>https://pkizerotohero.com/guides/add-root-ca-macos/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/add-root-ca-macos/</guid>
<description>Your Mac, or every managed Mac, trusts your organisation's private root CA in the System keychain, and you know which apps need their own setting.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to trust a private root CA on Linux</title>
<link>https://pkizerotohero.com/guides/add-root-ca-linux/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/add-root-ca-linux/</guid>
<description>Your Linux server, desktop or container image trusts your organisation's private root CA system-wide, and you know which programs keep their own list.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to add a CA to a Java trust store (cacerts)</title>
<link>https://pkizerotohero.com/guides/add-root-ca-java/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/add-root-ca-java/</guid>
<description>Your Java program trusts your private root CA, either through the JDK's cacerts or through its own trust store, and you have proved it with a real connection.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to make Python, Node.js and npm trust a private CA</title>
<link>https://pkizerotohero.com/guides/trust-ca-python-node/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/trust-ca-python-node/</guid>
<description>Python, pip, requests, Node.js and npm trust your private root CA, through the operating system's store or a bundle file, with verification still fully on.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to install a certificate in nginx</title>
<link>https://pkizerotohero.com/guides/install-certificate-nginx/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/install-certificate-nginx/</guid>
<description>nginx serves your certificate and its full chain on port 443, with a key that matches, and you have proved it from the outside with OpenSSL and curl.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to install a certificate in Apache httpd</title>
<link>https://pkizerotohero.com/guides/install-certificate-apache/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/install-certificate-apache/</guid>
<description>Apache httpd serves your certificate with its full chain from one SSLCertificateFile, with a matching key, and you have proved it from outside.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to install a certificate in IIS</title>
<link>https://pkizerotohero.com/guides/install-certificate-iis/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/install-certificate-iis/</guid>
<description>IIS serves your certificate with its private key and intermediate on an HTTPS binding with SNI, and renewed certificates get rebound instead of silently expiring.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to install a certificate in Tomcat and other Java servers</title>
<link>https://pkizerotohero.com/guides/install-certificate-tomcat/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/install-certificate-tomcat/</guid>
<description>Tomcat, or a Spring Boot or other Java server, serves your certificate with its full chain from PEM files or a PKCS #12 keystore, verified from outside.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to get and renew Let's Encrypt certificates with certbot</title>
<link>https://pkizerotohero.com/guides/certbot-lets-encrypt/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/certbot-lets-encrypt/</guid>
<description>certbot gets a Let's Encrypt certificate for your Linux server, installs it, renews it automatically on the CA's schedule, and reloads your web server each time.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to automate certificates in Kubernetes with cert-manager</title>
<link>https://pkizerotohero.com/guides/kubernetes-cert-manager/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/kubernetes-cert-manager/</guid>
<description>cert-manager issues Let's Encrypt certificates for your Kubernetes Ingresses or Certificate resources, stores them in Secrets and renews them before they expire.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to automate certificates on Windows with win-acme</title>
<link>https://pkizerotohero.com/guides/win-acme-windows/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/win-acme-windows/</guid>
<description>win-acme gets Let's Encrypt certificates for your IIS sites, binds them, and renews them every day from a scheduled task that follows the CA's renewal advice.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to get a wildcard certificate with DNS-01</title>
<link>https://pkizerotohero.com/guides/wildcard-dns-01/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/wildcard-dns-01/</guid>
<description>You will have a publicly trusted certificate for *.example.com and example.com, issued through the ACME DNS-01 challenge with a narrowly scoped DNS key, and renewing by itself.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to set CAA records for your domain</title>
<link>https://pkizerotohero.com/guides/caa-records/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/caa-records/</guid>
<description>You will have DNS CAA records that let only the CAs you really use issue certificates for your names, with separate wildcard rules and an address for violation reports.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to monitor Certificate Transparency for your domains</title>
<link>https://pkizerotohero.com/guides/monitor-certificate-transparency/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/monitor-certificate-transparency/</guid>
<description>You will have a scheduled check that lists every new publicly trusted certificate for your domains and flags any certificate issued by a CA you did not allow.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to configure TLS securely (versions, ciphers, HSTS)</title>
<link>https://pkizerotohero.com/guides/tls-configuration/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/tls-configuration/</guid>
<description>You will have a web server that offers only TLS 1.2 and 1.3 with forward-secret ciphers, staples OCSP only where it still applies, sends HSTS safely, and passes testing.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to set up mutual TLS (nginx and curl)</title>
<link>https://pkizerotohero.com/guides/mutual-tls-setup/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/mutual-tls-setup/</guid>
<description>You will have an nginx endpoint that accepts only clients holding a certificate from your own client CA, lets in only the clients you name, and is tested with curl.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to run a small private CA with step-ca (lab)</title>
<link>https://pkizerotohero.com/guides/private-ca-step-ca/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/private-ca-step-ca/</guid>
<description>You will have a lab CA running smallstep's step-ca that issues and renews 24-hour certificates, speaks ACME, and refuses names outside your lab domain.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to build a test CA with OpenSSL (lab only)</title>
<link>https://pkizerotohero.com/guides/openssl-test-ca/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/openssl-test-ca/</guid>
<description>You will have a two-tier test CA built with openssl ca: a root, a name-constrained issuing CA, server and client certificates, a revocation and working CRLs.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to sign code with signtool and cosign</title>
<link>https://pkizerotohero.com/guides/code-signing-signtool-cosign/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/code-signing-signtool-cosign/</guid>
<description>You will sign and timestamp a Windows program with SignTool, sign a release file with Sigstore cosign, and verify both, including who signed and when.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to use SSH certificates instead of known_hosts</title>
<link>https://pkizerotohero.com/guides/ssh-certificates/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/ssh-certificates/</guid>
<description>You will have OpenSSH host and user certificates signed by your own CAs, so clients trust servers without first-use prompts and servers trust short-lived user certificates.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to test post-quantum hybrid TLS</title>
<link>https://pkizerotohero.com/guides/post-quantum-tls-test/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/post-quantum-tls-test/</guid>
<description>You will know whether your servers and network negotiate the X25519MLKEM768 hybrid key exchange, and how to read, force and troubleshoot it with OpenSSL 3.5.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>How to prepare for short-lived certificates: a checklist</title>
<link>https://pkizerotohero.com/guides/prepare-47-day-certificates/</link>
<guid isPermaLink="true">https://pkizerotohero.com/guides/prepare-47-day-certificates/</guid>
<description>You will have a dated plan that moves every public TLS certificate to automated renewal, with an inventory, owners, ARI, independent monitoring and a budget, before lifetimes shrink.</description>
<category>How-to guides</category>
<pubDate>Tue, 20 Oct 2026 08:00:00 GMT</pubDate>
</item>
<item>
<title>What's changing in PKI</title>
<link>https://pkizerotohero.com/changes/</link>
<guid isPermaLink="true">https://pkizerotohero.com/changes/</guid>
<description>Dated, plain summary of what is changing in certificates and PKI: 47-day lifetimes, OCSP, clientAuth, Let's Encrypt, post-quantum and EU rules.</description>
<category>Changes</category>
<pubDate>Mon, 19 Oct 2026 08:00:00 GMT</pubDate>
</item>
</channel>
</rss>
