isn't there a setting I could have turned on/off that would have prevented that?Quote:
Originally Posted by stan
Printable View
isn't there a setting I could have turned on/off that would have prevented that?Quote:
Originally Posted by stan
Quote:
Originally Posted by megabytemeisn't there a setting I could have turned on/off that would have prevented that?Quote:
Originally Posted by stan
Sorry but no. It is not an individual thing. The whole 3-6000 IPT swarm was exposed till IPT staff killed the passkey.
The BTN thing is different. Changing your client port number kills the connection.
That's interesting. Surprised it isn't a bigger issue then. Maybe one of the masterminds of the community (paging anon, anon to the white courtesy phone, please :) ) can come up with a patch.Quote:
Originally Posted by stanQuote:
Originally Posted by megabyteme
Sorry but no. It is not an individual thing. The whole 3-6000 IPT swarm was exposed till IPT staff killed the passkey.
The BTN thing is different. Changing your client port number kills the connection.
Attachment 159994
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.Quote:
Originally Posted by megabyteme
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].
merwais dont be a pussy and use your own account you already have here not some 1-day alt
Attachment 160004
@2501
:lol: the account was registered yesterday itself IPT :P
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. :dry:
Quote:
Originally Posted by piercerseth
and now it appears to be PassThePopcorn's turn
Quote:
Originally Posted by stanQuote:
Originally Posted by piercerseth
and now it appears to be PassThePopcorn's turn
Anyone from PTP here? I've been a member for years. I can't get in.
"You have failed the snatchlist challenge too many times."
My emails offered to send a password reset are refused.