<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Certificates on Nalar</title>
    <link>https://nalar.dev/tags/certificates/</link>
    <description>Recent content in Certificates on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/certificates/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OCSP Stapling Moves Revocation Evidence Closer to the TLS Handshake</title>
      <link>https://nalar.dev/ocsp-stapling-moves-revocation-evidence-closer-to-the-tls-handshake/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/ocsp-stapling-moves-revocation-evidence-closer-to-the-tls-handshake/</guid>
      <description>&lt;h1 id=&#34;ocsp-stapling-moves-revocation-evidence-closer-to-the-tls-handshake&#34;&gt;OCSP Stapling Moves Revocation Evidence Closer to the TLS Handshake&lt;/h1&gt;&#xA;&lt;p&gt;A browser can receive a valid certificate chain, verify every signature, confirm the hostname, and still face one more question: has the issuing certificate authority revoked the leaf certificate since it was issued? That question is awkward because the certificate itself cannot carry a fresh answer. Its signed validity interval is fixed at issuance, while revocation is an event that can happen later.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
