<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bittorrent on Simon Waite</title>
    <link>https://simonwaite.com/tags/bittorrent/</link>
    <description>Recent content in Bittorrent on Simon Waite</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Apr 2012 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://simonwaite.com/tags/bittorrent/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BitTorrentDHT</title>
      <link>https://simonwaite.com/posts/bittorrent-dht/</link>
      <pubDate>Mon, 16 Apr 2012 12:00:00 +0000</pubDate>
      <guid>https://simonwaite.com/posts/bittorrent-dht/</guid>
      <description>&lt;p&gt;Post date: Apr 16, 2012 12:00:00 PM&lt;/p&gt;&#xA;&lt;p&gt;The specification for identifying mainline clients is the &amp;ldquo;v&amp;rdquo; key in the root dictionary of every message.&lt;/p&gt;&#xA;&lt;p&gt;These are in the wild. I noticed a South Korean client that claimed that it was a uTorrent client (UTz\xAD) that:&lt;/p&gt;&#xA;&lt;p&gt;114.200.XX.XX:345YY v:UTz\xAD is trying to convince me I&amp;rsquo;m: 114.200.XX.XX:440ZZ&lt;/p&gt;&#xA;&lt;p&gt;The port was correct, but the ip was the buggy/malicious clients own.&lt;/p&gt;&#xA;&lt;p&gt;A Vietnamese &amp;lsquo;uTorrent&amp;rsquo; client (UTy\xA3) claimed that I was 192.168.1.1:440ZZ, which while it had the port correct, thought I was on an internal network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
