The New Improvements of uTorrent 2.0 (Final)

[anon]

Actually, he's right... uTorrent contacts that host after installation to get some peers and bootstrap the DHT.

[Cabalo]

All this uT crap started back at 1.6.1
I also faced it as a scare tactic to force upgrades to the newer versions.
As I read on the webz, there was a lot of coliding views on those same nasty rumours, so I couldn't be arsed and moved on to Vuze until today.

It is heavy, but it easily has more features than any other client I know of.
Utorrent 2.0 isn't seducing me yet, so let's wait until the dust settles to make a valid opinion.

[anon]

As I read on the webz, there was a lot of coliding views on those same nasty rumours, so I couldn't be arsed and moved on to Vuze until today.

It is heavy, but it easily has more features than any other client I know of.

Took the easy exit, huh

But I agree. Vuze is a great, very tweakable client. And while it's not a feather like uTorrent when it comes to resource usage, you won't feel it's there with enough RAM and a decent processor.

[pro267]

to see what's the bootstrap entry point for their mainline DHT tracker implementation.

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

First, let me answer the claims:

1. No, you're not safe in a private tracker; that's another misconception of people who have no idea what they're talking about. Now, if you would've actually known what you were talking about, you would know that DHT is a client-side protocol that has nothing to do with the tracker being private or not.

The only thing private sites can do is turn on the private flag in torrent files and count on the clients to respect that by turning off DHT, peer exchange and local peer discovery. Once they do, it's totally up to the client to respect (or not) that flag. In fact, the uT version I've specified above did NOT respect the private flag and multicasted info hashes to organization-local addresses. By the way, another client (BitComet) was banned from various private sites for disregarding the privacy bit.

2. While info is available for harvesting on public trackers, it is not fed with a spoon to the MPAA.

Oh, and since you were nice enough to comment on my knowledge of the subject, may I suggest that in the future, you actually try to read that DHT draft before posting mindless spam..

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.

That's one possible solution for people who know about this issue. Most people are not aware of it.

[AdrianPhoto]

Yummy!! I'm gonna have fun with this!

you would know that DHT is a client-side protocol that has nothing to do with the tracker being private or not.

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.

Do you have anything to back those claims?

if concerned, just block those IPs and ask a friend for his dht.dat file.

+1

[pro267]

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"

: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.

While info is available for harvesting on public trackers, it is not fed with a spoon to the MPAA.

Do you have anything to back those claims?

Learn to read first, then return to the thread above. You'll get all the answers you need.

Why do I even bother anymore..

[anon]

AdrianPhoto, pro267 is right regarding DHT being a client-side protocol in the sense the tracker as we know it isn't involved. (Technically, every DHT node is a tracker, but that's outside the scope of this discussion)

Regarding the MPAA call-homes, you can find info in the first pages of this thread, or by doing a simple Google search.

[kurdt]

It's easy to remove them (or at least most of them) by unpacking the executable and using a hex-editor. so I'm still using it

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.

i'm using uT 1.8.5. Can you (or anyone) give me specific instructions how to make these tweaks (or provide a link where i can learn about this), please.

Here's what i don't understand:

1) I know how to use a hex editor. What are the specific things that need to be removed from the exe?

2)
a)What are the IP ranges for router.utorrent.com and router.bittorrent.com?
b)If I knew them, can I just plug them into a custom peerblock list?

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

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

thanks

[anon]

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.

Here's what i don't understand:

1) I know how to use a hex editor. What are the specific things that need to be removed from the exe?

I remove the following things in my mods:

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.

2)
a)What are the IP ranges for router.utorrent.com and router.bittorrent.com?
b)If I knew them, can I just plug them into a custom peerblock list?

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?

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?

If you're paranoid, you should do both 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.

[AdrianPhoto]

I apologize to pro267 for my nonsense behavior.