<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Censorship-Resistance on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/censorship-resistance/</link>
    <description>Recent content in Censorship-Resistance on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 29 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/censorship-resistance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MasterDnsVPN vs DNSTT vs SlipStream in 2026: Which DNS Tunnel Actually Survives a Hostile Network?</title>
      <link>https://www.pistack.xyz/posts/2026-10-29-dns-tunneling-masterdnsvpn-dnstt-slipstream-censorship-bypass/</link>
      <pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-29-dns-tunneling-masterdnsvpn-dnstt-slipstream-censorship-bypass/</guid>
      <description>&lt;p&gt;Your ISP blocks port 443 to anything that is not on its allowlist, UDP looks like it has been shaped into mush, and yet DNS still resolves — because if DNS broke, the whole network would break with it. That single fact is why DNS tunnels refuse to die. In 2026 the tooling around them changed dramatically: a Go implementation with resolver health checks and eight load-balancing modes, a Rust rewrite that moved the tunnel onto QUIC multipath, and the original research implementation that everything else is measured against.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
