<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ocsp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ocsp/</link>
    <description>Recent content in Ocsp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ocsp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted OCSP Responder &amp; Certificate Revocation: CFSSL vs Smallstep vs EJBCA CRL</title>
      <link>https://www.pistack.xyz/posts/2026-05-06-self-hosted-ocsp-responder-certificate-revocation-cfssl-smallstep-ejbca-crl/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-06-self-hosted-ocsp-responder-certificate-revocation-cfssl-smallstep-ejbca-crl/</guid>
      <description>&lt;p&gt;Certificate revocation is one of the most overlooked aspects of self-hosted PKI infrastructure. When a TLS certificate is compromised, expired, or issued in error, the certificate authority must provide a mechanism for clients to verify that the certificate is no longer trusted. Without proper revocation checking, compromised certificates remain valid until their natural expiration date — potentially months or years.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
