<?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>Systems on Syed Anwaruddin</title>
    <link>https://syed-anwar-uddin.github.io/tags/systems/</link>
    <description>Recent content in Systems on Syed Anwaruddin</description>
    <generator>Hugo -- 0.145.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://syed-anwar-uddin.github.io/tags/systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unified L4&#43;L7 bandwidth governance: rethinking Internet-scale TLS scanning</title>
      <link>https://syed-anwar-uddin.github.io/posts/lynx-unified-bandwidth-governance/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://syed-anwar-uddin.github.io/posts/lynx-unified-bandwidth-governance/</guid>
      <description>&lt;p&gt;When you&amp;rsquo;re scanning the IPv4 space for TLS certificates, the bottleneck isn&amp;rsquo;t usually the SYN sweep or the TLS handshakes individually. It&amp;rsquo;s the interaction between them, and the standard tooling doesn&amp;rsquo;t model that interaction.&lt;/p&gt;
&lt;p&gt;The canonical research pipeline is ZMap piped through ZTee into ZGrab2. ZMap fires SYNs at a configured L4 rate. ZGrab2 reads verified hosts off the pipe and runs TLS handshakes at a configured worker count. They share an interface, a kernel, and an uplink, but they don&amp;rsquo;t share a rate budget. The result on dense CDN ranges is that ZGrab2&amp;rsquo;s certificate traffic can dwarf ZMap&amp;rsquo;s SYN stream, with no mechanism for the L7 surge to throttle the L4 cannon. On global anycast prefixes the same dynamic causes something more interesting: per-AS scanner detection at the CDN that neither tool would trigger alone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
