[bittorrent] 8-bytes transaction id

Alan McGovern alan.mcgovern at gmail.com
Thu Apr 5 03:44:02 EDT 2007

You should not reply to nodes which send invalid transaction ID's. Any node
which does *not* send back the transaction ID you sent it exactly as you
sent it should be dropped.

It's not "not-so-standard", it's just wrong.

There was a thead about this a while ago which tried to clarify exactly how
the transaction ID's and tokens should be encoded. Check that out.


On 4/5/07, Stas Khirman <staskh at comcast.net> wrote:
> Quite often , I see some of the DHT nodes are responding with 8-bytes
> transaction ID despite the fact that queries have only 2-bytes ID.
> Apparently,  all responses in question a pretty similar format : two first
> bytes are correct transaction ID, then 4 bytes of 0x000018FF and then two
> more bytes (often similar between different peers). For example:
> xxxx000018FFyyyy
> xxxx000018FFyyyy
> It seems to be a behavior of some "not-so-standard" implementation - does
> anyone know what client have such behavior? What is a meaning of the last
> 6
> bytes? Version?
> Regards
> Stas
> _______________________________________________
> BitTorrent mailing list
> BitTorrent at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/bittorrent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ibiblio.org/pipermail/bittorrent/attachments/20070405/4d29ac3b/attachment.html 

More information about the BitTorrent mailing list