<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Socks5 on Vitalii Zaiats</title>
    <link>https://vitalii-zaiats.com/tags/socks5/</link>
    <description>Recent content in Socks5 on Vitalii Zaiats</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vitalii-zaiats.com/tags/socks5/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chaining SOCKS5 UDP relays: self-loops, SSRF, and the amplification that isn&#39;t</title>
      <link>https://vitalii-zaiats.com/posts/chaining-socks5-udp-relays/</link>
      <pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://vitalii-zaiats.com/posts/chaining-socks5-udp-relays/</guid>
      <description>Final follow-up post debunking the &amp;ldquo;open UDP relay = DDoS amplifier&amp;rdquo; fear: chaining launders origin but de-amplifies at the target, self-looping only DoSes the relay itself, loopback forwarding is a UDP SSRF, and even a paid commercial proxy fails the RFC 1928 §6 source check — every behavior reframed as a single-packet detection fingerprint.</description>
    </item>
    <item>
      <title>Auth on TCP, open on UDP: the SOCKS5 relays scanners can&#39;t see</title>
      <link>https://vitalii-zaiats.com/posts/socks5-udp-open-relays/</link>
      <pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://vitalii-zaiats.com/posts/socks5-udp-open-relays/</guid>
      <description>Final version of the SOCKS5 open-UDP-relay teardown: de-quantified the scan-list phrasing, aligned a log comment to first-person voice, and thinned one forward-reference scaffold, with all tables, numbers, RFC references, and the &amp;ldquo;signals, not weapons&amp;rdquo; defensive framing preserved verbatim.</description>
    </item>
  </channel>
</rss>
