<?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>Telegram on Vitalii Zaiats</title>
    <link>https://vitalii-zaiats.com/tags/telegram/</link>
    <description>Recent content in Telegram on Vitalii Zaiats</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vitalii-zaiats.com/tags/telegram/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wire-to-WiFi correlation, part two</title>
      <link>https://vitalii-zaiats.com/posts/wire-air-correlation-part2/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://vitalii-zaiats.com/posts/wire-air-correlation-part2/</guid>
      <description>The monitor radio from last post&amp;rsquo;s shopping list showed up, so I stopped driving synthetic beacons and pointed it at a real Telegram video call — captured twice at once: from the air, encrypted, and from inside the target, decrypted, as ground truth. The call&amp;rsquo;s shape crossed the encryption at r = 0.8–0.9, a wrong-window null stayed dark, and the whole thing was legible without reading one byte of content. Then the honest half: a background stream drowned the call until it got loud, the downlink data frames stayed as unreadable as ever, and a clever one-way ICMP trick failed a null control cleanly.</description>
    </item>
  </channel>
</rss>
