[KDE] Ktorrent 5.1.0-2 banned from private tracker because it IDs itself incorrectly

[lao_an]

Hi gang,

I recently noticed that ktorrent was banned from a private tracker that I have been using. A few questions to the tracker admins, and a cursory Google search later revealed the problem:

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=875720

Log entries showed that ktorrent was reporting incorrectly to the tracker:

"Sun Dec 16 06:44:55 2018: Doing tracker request to url (via KIO): https://tracker.xxxxxxxxxx.xxx/...hash.../announce?peer_id=-KT50DV-"

This bug is already over a year old. My best bet would probably be to find out where ktorrent stores its peer_id string, and change it from "-KT50DV-" to "Ktorrent 5.1.0 2". A search of the "installed files" list provided by Muon did not reveal any config files that report peer_id. Is there a config file I can mod?

[claydoh]

https://bugs.kde.org/show_bug.cgi?id=370448

You would need to modify the source file mentioned in this bug and compile ktorrent from scratch.
dunno why they won't fix that








I a a big fan of Qbittorrent myself

[SpecialEd]

>>>

I a a big fan of Qbittorrent myself

Seconded.

[oshunluvr]

Transmission.

[lao_an]

Well...

Roll my own, or migrate everything to another client. Either way, it looks like I have my work cut out for me!

Thanks for the suggestions. If I figure out another way, I'll post my solution here.

P.S.: The same bug is in 5.1.1-1 as well!

老安

[jlittle]

You would need to modify the source file mentioned in this bug and compile ktorrent from scratch.

To make the point that this is feasible, here's how to do this.

$ sudo apt install git        # in case you don't have git already
$ sudo apt-get build-dep ktorrent
$ git clone git://anongit.kde.org/ktorrent
$ cd ktorrent
$ [i]  edit libktcore/ktversion.h, change bt::DEVEL to bt::NORMAL [/i]
$ cmake .
$ make -j8            # might take a while; maybe adjust the 8 to match your CPU's threads
$ cd ktorrent         # yes, again
$ ./ktorrent

I built and ran ktorrent like this, but I don't know a torrent for a "private tracker" with that restriction to check how it identifies itself.

[lao_an]

To make the point that this is feasible, here's how to do this.

$ sudo apt install git        # in case you don't have git already
$ sudo apt-get build-dep ktorrent
$ git clone git://anongit.kde.org/ktorrent
$ cd ktorrent
$ [i]  edit libktcore/ktversion.h, change bt::DEVEL to bt::NORMAL [/i]
$ cmake .
$ make -j8            # might take a while; maybe adjust the 8 to match your CPU's threads
$ cd ktorrent         # yes, again
$ ./ktorrent

I built and ran ktorrent like this, but I don't know a torrent for a "private tracker" with that restriction to check how it identifies itself.

Thanks, John! After I uncommented the "deb-src" entries in /etc/apt/sources.list, your instructions worked flawlessly.

Ktorrent log now reads:
"Sun Dec 16 18:34:32 2018: Doing tracker request to url (via KIO): https://tracker.xxxxxxxx.xxx/...hash...97%0A%A3%A9%A9
Sun Dec 16 18:34:32 2018: Selected tracker https://tracker.xxxxxxxx.xxx/...hash.../announce (tier = 1)"

Peer ID is now reading correctly, I suppose... BUT: when I click on the "Trackers" radio button on the lower right of the GUI, it says that I'm *still* banned by that private tracker.

Now it's time for another round with the admins there.

老安

[claydoh]

It is entirely possible that there is a build or cmake flag to set it as a Release version.

No idea what it would be tho

Sent from my LG-H931 using Tapatalk