img.png
Original information which was deleted by BTN staff and Reddit troll Mods. Full story and real story.
This isn't really something you can "patch". Some sort of protocol extension to authenticate peers as coming from a reliable source would be required. While drafts for such a thing exist[1], it is not an standard yet, and would require support from the tracker script's side too.
I can think of two workarounds:
- enabling the "randomize port on startup" option or similar in your client
- deliberately firewalling yourself to become off-limits to "foreign" peers, while you can still transfer to and from those received from the private tracker. It has the disadvantages we all know, of course (if everyone does it, you won't be able to download at all).
Other than that, you can't really do anything, because BitTorrent wasn't designed with private trackers in mind in the first place[2]. If I have your IP and port and know you're serving a torrent with a specific info_hash I already possess the metadata for, I can connect to you. You could notice my attempts and block my address, sure, but that's not a viable solution when you're potentially exposed to thousands of ghost leechers, as is the case here.
And for the record, this isn't a new tactic[3].
"I just remembered something that happened a long time ago."
merwais dont be a pussy and use your own account you already have here not some 1-day alt
giphy.gif
Last edited by 2501; 04-26-2015 at 08:34 AM.
@2501
the account was registered yesterday itself IPT
That was a good read, anon. Since I've only encountered it once, it does not seem to be too much of a problem.
----------------
Guys, Malways is above that...Wait. No he isn't. What was I thinking?!
Hi, Malways.
Bookmarks