Hi! i am silentp33r and this is my blog. i think i love the idea of freedom although i have not yet understood what freedom is fully. whatever simply this is the place where i talk all the shit that i want to talk about. My interests are FOSS/open source, hacking(http://en.wikipedia.org/wiki/Hacker or http://www.catb.org/~esr/faqs/hacker-howto.html), music, p2p!!!… etc
well i guess thats enough for the about page… see you around 
August 12, 2007 at 2:42 pm |
hello nice to read “Ghost Leeching”.
this thing i discovery without U and other help. its nice 2 hack/cheat little in torrent.
i using utorrent.
August 12, 2007 at 3:00 pm |
well i didn’t ‘discover’ this… it has been around for some time, i have just ‘rediscovered’ it
lol…
yeah i know what you mean man. its really cool to cheating torrenting… specially in those nazy type trackers!
September 14, 2007 at 7:46 pm |
Hi,
I was just looking for a way of cheating on Oink.cd… I’ve already been banned for 5 times (lol)… nice, nop ? Anyway, they’ve a very good protection against cheaters
. Btw, your article “Ghost leeching” gave me a tremendous idea, but I confess that I didn’t really understand how “client B” can start leeching if he doesn’t possess the torrent file :S… You’ve the list of peers (I guess, you inject a peer in azureus), but how to know which file the client want to download ?
Cheers
September 14, 2007 at 11:18 pm |
well client B will have to possess a torrent file! he should get it from a ‘friend’ who has access to oink. after all he have to receive the peer list through a friend who is already in the swarm and have a good peer list….
once B get the torrent file he can modify the tracker URL so that no tracker communication is made. and inject the peers and start leeching
September 15, 2007 at 10:37 am |
Ok, now it’s clearer. Here’s my idea. Suppose A,B,C,D 4 peers, with A,B the same as before (A leech and give the peer list to B which is outside the tracking system). C,D are seeding peers and are part of the list that A gives to B.
Suppose now that you apply this on oink.cd. It is quite easy to implement a “cheater script”: sum of all outgoing bytes == sum of all incoming bytes, since the overall sum (for each file/torrent) MUST be always the same (=constant). Of course, we add a fault tolerance, for example of 1%. If outgoing != incoming => there’s a problem, proabably a cheater.
Using this technique, C,D will upload to B, which is not known by the tracker. It figures out that C&D will probably report a higher upload rate to the tracker (since they uploaded files to B) and they will look suspicious => They will get banned.
Suppose we do this for 200-300 peers, Oink.cd will have the obligation to desactive their fuc**** scripts…
September 18, 2007 at 3:36 am |
Sorry for the late reply was busy with a ‘interesting’ project of mine
yes, you are correct by using this method we risk other’s accounts… but the thing is if we download from multipal clients… the amounts they “fake” report would be little… so it won’t be that easy for oink to capture them… cause how would oink know that it was not two people who faked, but it was three? cause the faked amount of traffic may have come from multipal sources… etc etc…
i would doubt whether oink would ever really care for those who get banned… they are Nazi types… they don’t care
but anyways, if the numbers grow bigger they will be compelled to do something about this yes…
then they can always try to ban the ip’s of the ghost peers… if they can identify them..
they can make a black list and pass it around…
and hey when we leech as ghost peers we can also seed as ghost seeders!!! lolz… this would make it harder for oink to catch ‘cheaters’… and will surely make the situation more complex
what do you think?
September 18, 2007 at 12:07 pm |
What I think ? we should try this ABSOLUTLY
. Moreover it’s so easy to change an IP address… What we could do is the following: we donwload a file with many peers, and we get the list of all these peers. Once we have the list of peers, we start leeching from only 1 peer at a time. Once the file has been downloaded, we take the next peer, etc. Thus, we can automatize this task. By doing this in a university (for example), where there’s a huge bandwith, it will accelerate the process. Naturally, it would be nice to trick an admin/staff 
or a big uploader… Even if they’re nazist (as you say 
), I’m sure they’ll reflect twice before banning them…
I don’t guess that Oink will make a “black list” to pass at each user, it seems too difficult to achieve this, moreover, lot of user would not know how to insert it in their bittorrent client.
.
Btw, I let my mail if you’re interested to test this