<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Authenticated Denial on Nalar</title>
    <link>https://nalar.dev/tags/authenticated-denial/</link>
    <description>Recent content in Authenticated Denial on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/authenticated-denial/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NSEC3 Hashes DNSSEC Denial Records Without Hiding Guessable Names</title>
      <link>https://nalar.dev/nsec3-hashes-dnssec-denial-records-without-hiding-guessable-names/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/nsec3-hashes-dnssec-denial-records-without-hiding-guessable-names/</guid>
      <description>&lt;p&gt;A DNSSEC signature can authenticate data that exists, but a resolver also needs cryptographic evidence when a requested name or record type is absent. A plain unsigned &lt;code&gt;NXDOMAIN&lt;/code&gt; response cannot provide that property: an attacker able to alter DNS traffic could fabricate the same response. NSEC3 supplies signed denial records while replacing clear-text owner names in the denial chain with hashes.&lt;/p&gt;&#xA;&lt;p&gt;RFC 5155 defines NSEC3 as an alternative to NSEC for authenticated denial of existence. Its main privacy-related distinction is narrow but useful: walking an NSEC chain directly reveals neighboring owner names, whereas NSEC3 exposes hashes that require additional work to map back to candidate names.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
