Ticket #2505 (closed defect: fixed)

Opened 12 months ago

Last modified 10 months ago

libtorrent rejects a torrent which has a valid announce but a malformed announce-list

Reported by: anonymous Owned by: rakshasa
Priority: normal Component: libtorrent
Version: Severity: normal
Keywords: Cc:

Description

If libtorrent is asked to download a torrent which defines a valid announce URL, but a malformed announce-list, then it rejects it with the message "Tracker group list not a list".

See the attached torrent file as an example. This torrent contains fields as follows (in Python syntax):

{

"announce": " http://inferno.demonoid.com:3394/announce", "announce-list": [

{

0: {}

}

], "created by": "uTorrent/2000"

}

Clearly, this file is ludicrously and inexcusably malformed. Still, there is enough information to download it, it would be useful if libtorrent did so.

At present, the workaround is to use a hex editor to destroy the announce-list by turning the key into something unrecognised ("xnnounce-list" will do), so libtorrent ignores it.

Attachments

[isoHunt] mu-essentials.torrent Download (79.1 KB) - added by anonymous 12 months ago.
download_constructor.diff Download (0.6 KB) - added by maximilian.kuhnke@rankesoft.org 12 months ago.
Patch which will fix this problem

Change History

Changed 12 months ago by anonymous

Changed 12 months ago by maximilian.kuhnke@rankesoft.org

Patch which will fix this problem

Changed 12 months ago by maximilian.kuhnke@rankesoft.org

I have attached a patch,

works with libtorrent-0.12.7 and the current svn rev. 1191. It will make these kind of torrents work until a more qualified developer implements an adequate solution.

greets.

Changed 11 months ago by cygon

This issue is hitting me quite a lot recently - about one in three torrents fails to add with "tracker group list not a list". Probably some genius messed up the file format in one of the mainstream BitTorrent clients...

Changed 11 months ago by rakshasa

  • status changed from new to closed
  • resolution set to fixed

Changed 10 months ago by anonymous

Starting from which release version is this fix included? Thanks!

Changed 10 months ago by anonymous

I also don't find this bug fixed. rakshasa please tell us which version is correct.

Note: See TracTickets for help on using tickets.