The New Improvements of uTorrent 2.0 (Final)

anon-sbi said:
Using a hex-editor is easy. It's like Notepad, but deeper. You can find a good one here:
http://mh-nexus.de/en/hxd/
Note the official uTorrent EXEs are compressed with UPX, so you'll need to download the "uncompressed" builds or unpack them yourself using UPX or QUnpack before you can edit them.



I remove the following things in my mods:
Code: 
239.192.152.143
239.255.255.250
http://www.utorrent.com/report_problem.php
http://update.utorrent.com/checkupdate.php
http://update.utorrent.com/updatestats.php
llsw.download3.utorrent.com
ll.download3.utorrent.com
http://update.utorrent.com/installstats.php
http://download.utorrent.com/offers/tb_ask-1.5.1.0.exe
http://%s/offers/tb_ask-1.5.1.0.exe
http://download.yandex.ru/yandex-pack/utorrent/YandexPackSetup.exe
http://download.yandex.ru/yandex-pack/utorrent/YandexPackSetup-utorrent-20090724.exe
http://search.utorrent.com/search.php?q=%U&e=%U&u=1

You can replace the IPs with 000.000.000.000, and simply fill the rest with null bytes.



a. both use the same IPs: 67.215.242.138, 67.215.242.139
b. yes, you can add them to your PeerBlock blocklist and they should no longer be contacted.

3)
a)What's the purpose of the dht.dat file? and
b)why do you need to get one from a friend?
Click to expand...

a. the dht.dat file contains the addresses of other peers uTorrent will connect to to form part of the DHT after start-up.
b. the "router.*.com" hosts give you some peers to get you started when you've just installed uTorrent. If you're a bit paranoid, you'll block them, but then you'll be unable to bootstrap (connect) until you get your hands on a dht.dat file - so I recommend asking a friend for his. If your DHT is already working, there's nothing to worry about.

4) Do you have to do both of these methods, or would one suffice?
Click to expand...

If you're paranoid, you should do both :lol: Personally, I only block the call-homes and don't touch the "router.*.com" addresses. But then again my country is outside the MPAA's reach for the time being.
Click to expand...

Thanks so MUCH for taking the time to post all that info. will editing the exe cause any problems with privates sites that have specific allowed clients? i.e., would it look like a cheater mod to them or an unallowed version?

also, if you only use private sites do you still need that file to initialize the DHT?
 
lysine said:
lol, please give us a link where that happened. exactly, you're just making up stuff and spreading FUD now...
Click to expand...
Here are just a couple of points for you:

* uTorrent was purchased by bittorrent.com, a site affiliated with the MPAA. Google it to check for yourself.
* Try installing uT 1.7, enable DHT, and wireshark for bittorrent.com IPs (I suggest: 67.215.242.138-9, 38.114.167.69, 208.72.193.198) to see what's the bootstrap entry point for their mainline DHT tracker implementation.

The above means BitTorrrent.com (read: MPAA) has access to your torrents' info hash, i.e. pretty much a 1:1 correlation between IPs and downloaded torrent files.
 
Too bad DHT is not allowed on private tracker torrents, so its a non issue for most of us. If your using public trackers and DHT then they can already see everything you do anyway, so who cares.
 
Yummy!! I'm gonna have fun with this!


I couldn't help not to forward that to my friends, oh that quote is gonna make to history books, be happy!

Can you please describe in what scenario/design/schema you'd separate DHT nods to be servers or clients? I really want to hear more about that, you know, to consider DHT as "client-side" protocol.
Please read this
http://en.wikipedia.org/wiki/Client-side
""Client-side refers to operations that are performed by the client in a client-server relationship in a computer network""



While info is available for harvesting on public trackers, it is not fed with a spoon to the MPAA.
Click to expand...
Do you have anything to back those claims?

if concerned, just block those IPs and ask a friend for his dht.dat file.
Click to expand...
+1
 
pro267 said:
Obviously they're sure, otherwise there wouldn't be any discussions with the uT dev team.
Click to expand...

Maybe they only suspect v2.0's favoritism behavior exists and are checking it with the uTorrent development team. :unsure:

Personally, I seriously doubt the new version is giving preference to others of its same kind.
 
I've personally tested uTorrent 2.0, and since 1.8 I've been interested in uTP, and version after version, build after build I see no change in the performance regarding/concerning private trackers in terms of ratio stuff.
I guess I'm gonna stand with anon-sbi on this
 
Just to give some info, there are plans for the uTP specification to go open. If that ever happens, every client could potentially support it. What would tracker admins do then, ban all new client versions?

kurdt said:
Thanks so MUCH for taking the time to post all that info. will editing the exe cause any problems with privates sites that have specific allowed clients? i.e., would it look like a cheater mod to them or an unallowed version?
Click to expand...

Changing the things I mentioned (and only those) shouldn't affect the way uTorrent reports itself or your stats to the tracker. Now, if you change anything else other than what I posted, do it at your own risk.

also, if you only use private sites do you still need that file to initialize the DHT?
Click to expand...

If you use private sites only, you have no need for DHT. Just disable it.
 
pro267 said:
* Try installing uT 1.7, enable DHT, and wireshark for bittorrent.com IPs (I suggest: 67.215.242.138-9, 38.114.167.69, 208.72.193.198) to see what's the bootstrap entry point for their mainline DHT tracker implementation.
Click to expand...

router.utorrent.com and router.bittorrent.com? Those servers deliver some DHT nodes for you to bootstrap after installing. If concerned, just block those IPs and ask a friend for his dht.dat file.
 
:facepalm:

That's the best you could do? Try to semantically dispute the usage of the term client-side? And even if you did, what exactly does that quote prove, lmfao, that the action is performed by the clients themselves without involving the server/tracker side? (which is exactly what I said)

You've posted nothing about the facts themselves. Typical.

AdrianPhoto said:
While info is available for harvesting on public trackers, it is not fed with a spoon to the MPAA.
Click to expand...
Do you have anything to back those claims?
Click to expand...
Learn to read first, then return to the thread above. You'll get all the answers you need.

Why do I even bother anymore.. :dabs:
 
looking good.. is it be better than older version we'll see. I think adding more options is better for people who know something in IT but for those who not mhm i really don't know.
 
to see what's the bootstrap entry point for their mainline DHT tracker implementation.
Click to expand...
If you don't know how DHT works, then please.. for the love of every god men ever believed in.. Don't write just to sound like you know.

let's look at this:

1- Private tracker, you're safe! DHT disabled
2- Public tracker, your IP & Info hash for files you're downloading are distributed anyway, on any version of uTorrent or any other BitTorrent client.

I suggest reading this
http://wiki.theory.org/BitTorrentDraftDHTProtocol
 
2).Others more likely the bigger sites will allow UT2 and put pressure on other clients to update to UTP or risk banning their clients.
Click to expand...

wcd and waffles banning Deluge and azureus/vuze, two big players staring the cull.
 
Under the excuse those clients are used to cheat. A Deluge cheating mod doesn't even exist, and since the Vuze one can spoof most other allowed clients, this won't really stop cheating. :huh:
 
Back
Top