We are still actively working on the spam issue.

Ghostleech

From InstallGentoo Wiki
Revision as of 21:33, 25 April 2016 by Anon SBI (talk | contribs) (Created page with "'''Warning: /ghostleeching/ *IS* considered cheating by private trackers. Use your head or lose your account''' __TOC__ ==What is ghostleeching?== The bittorrent protocol i...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Warning: /ghostleeching/ *IS* considered cheating by private trackers. Use your head or lose your account


What is ghostleeching?

The bittorrent protocol is inherently insecure. This means that if I know the info_hash of a torrent and the IP+ Port that your torrent client is running on, I can connect to you and download the torrent from you, EVEN if I am NOT a member of your private tracker

Case 1: You are NOT a Member of a Private Tracker, but your Friend Is

If your IRC friend is on a /good/ private tracker and you are not. Just ask him for:

a) the torrent info_hash (eg: c12fe1c06bba254a9dc9f519b335aa7c1367a88a&dn)

b) an ip address:port of a seedbox user

Convert the infohash to a magnet link:

magnet:?xt=urn:btih:INFOHASH

magnet:?xt=urn:btih:c12fe1c06bba254a9dc9f519b335aa7c1367a88a&dn

and add that magnet link into your torrent client of choice and add the Peer using the given ip address:port

Congratulations! You are enjoying private tracker speeds, without private tracker autism

Case 2: You ARE a Member of a Private Tracker

Perhaps you want to download some files without taking a ratio hit:

1. Grab a torrent.

2. Pause the torrent or severely limit the download speed

3. Write down all /fast/ peers (IP and Port)

On a different IP:

4. Add the torrent to your client

5. Remove the tracker (which has your passkey and identifying information)

6. Add the Peers and you are good to go!

Warning 1: It looks suspicious if you grab many .torrent files, but dont actually download anything (because you /ghostleeched/ it all). Mix up actual downloading with /ghostleeching/

Warning 2: It is /unsafe/ and /suspicious/ to add a .torrent, let it announce to a tracker (get peers) and then stop it. What you want to do is CULTIVATE A LIST(IP+Port) of seedbox owners and "Archivers". The best way to do this is to download a torrent the /normal/ way, but log all traffic. Sort by speed and you have your seedbox users

With this list you can bypass steps 1-3. Add your torrent (IN A STOPPED STATE), remove the tracker, add your peers

Warning 3: It is risky to /ghostleech/ on small swarms (<10 peers + Old torrents). Let the size of the swarm protect you

FAQ

Is this unethical?

Piracy is unethical. Hoarding stolen work is even more unethical. With /ghostleeching/ you are giving back to the community and standing up to the hypocrisy

Scrapping Peers

You want to build a list of seedboxes and Archivers. Don't do this manually. Download for a week normally, but log all your activity with iptraf or iftop. Then sort by speed to get your list

I Can't Add Peers

Some clients prevent adding peers if you remove the private tracker. You have 4 solutions:

1) Use a DHT-Patched client (utorrent serenity)

2) Use a utorrent DHT Patcher

3) Use an /old/ Azureus Peer Injector

4) Get the info_hash, convert to magnet link and add the magnet URl

It Takes Awhile for the torrent to start

It can take up to 5 minutes. If the torrent hasn't started by than your peers are bad

How Can I Detect if I was /ghostleeched/

No method at the moment. If you have a seedbox assumed you were /ghostleeched/.

How Can I Prevent /ghostleeching/

Due to the protocol there is no easy way (other than stop using private trackers). You can try changing your ports every day. However this is not a reliable method, since the /ghostleecher/ will just grep your IP in the network logs to find the new port.

Notable Cases

IPT was involved with a similar technique. They took peers from PTP/BTN, added them to their own tracker and gavethem to their own swarm (the IPT users)

Can I Be Banned for this

Yes. However, as a /ghostleecher/ in Case 1 you have nothing to worry about since you can get a new IP. If you are providing the info_hashes+peers use your head.