pc486 Posted June 9, 2008 Report Share Posted June 9, 2008 As a forewarning I do not use uTorrent or Windows. I cannot test the latest beta even if I wished to do so. Hopefully someone can test the latest beta and verify if the bug still exists for me. That said...uTorrent 1.8 beta appears to make torrent files with an invalid bencoding. I have found a few torrents in the wild where:1. The torrent's 'created by' key is 'uTorrent/180B'.2. The torrent supports multiple trackers ('announce-list' key).3. The torrent's base dictionary is not in lexicographical order, as defined by the BitTorrent specification.I'm trying to avoid breaking forum rules, so here's a sample key list as they appear in an invalid uTorrent 1.8 torrent:announce-listannouncecreated bycreation dateencodinginfo length name piece length piecesThe correct lexicographical order on these keys would be:announceannounce-listcreated bycreation dateencodinginfo length name piece length piecesThe difference is the key order is the swapping of 'announce' and 'announce-list'I have identified wild uTorrent 1.7 files that are valid ('announce' before 'announce-list').My apologies if this bug is already fixed. Link to comment Share on other sites More sharing options...
jewelisheaven Posted June 9, 2008 Report Share Posted June 9, 2008 Dunno, depends on the version it was made with. As you see in the changelog they changed their parser a few times thusfar. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted June 9, 2008 Report Share Posted June 9, 2008 I do not use uTorrent or Windows. I cannot test the latest beta even if I wished to do so.I find that very hard to believe. Link to comment Share on other sites More sharing options...
pc486 Posted June 9, 2008 Author Report Share Posted June 9, 2008 Testing stuff under Wine is far more hassle than it's worth. Ideally I'd have a Windows VM for this kind of thing, but I don't have one (no time or money). Link to comment Share on other sites More sharing options...
jewelisheaven Posted June 9, 2008 Report Share Posted June 9, 2008 Then it sounds like the problem is fixed. Thanks for the report even if it didn't include useful data like when the torrents were made. Link to comment Share on other sites More sharing options...
Firon Posted June 9, 2008 Report Share Posted June 9, 2008 A report without knowing what build number was used is completely useless. Link to comment Share on other sites More sharing options...
greylion Posted July 4, 2008 Report Share Posted July 4, 2008 I recently came across some torrents which were created with "uTorrent/180B", which didn't work with the bittorrent and bittornado clients in Debian (4.0r3). Luckily I found a workaround; edit them with http://torrenteditor.com/I either remove one tracker or rearrange the list of trackers, and the edited torrent works fine in the clients I mentioned.It was kind of hard to find out if this problem had been fixed in the current utorrent 1.8 Beta, as the incompatible torrents don't contain any build number, and I (also) don't use windows, except when there's absolutely no other way (wine and similar stuff not included).I had to go dust off an old pc, install XP and other necessary stuff, and utorrent 1.8 Beta (build 11200), create a torrent with it, transfer it to my debian box and try it out with the bit[torrent/tornado] clients.As you might already have guessed, that torrent worked just fine.Anyway, feel free to point out the torrenteditor.com workaround, if other people should happen to complain about incompatible torrents created with "uTorrent/180B". Link to comment Share on other sites More sharing options...
Firon Posted July 4, 2008 Report Share Posted July 4, 2008 Some older betas sorted keys improperly, but the current build doesn't. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.