Tracker message encryption

[dchardware]

Hi!

Is there any option, or any method supported by utorrent, that makes possible to encrypt not just the bittorrent traffic between peers, but the tracker-client messages too?

I didn't find any info about this. I heard somewhere, that vesions above 1.7 are supporting tracker messages via https (using SSL). This is true?

Thank you!

Dchard

[DreadWingKnight]

Assuming the tracker supports https, uTorrent can use https with it.

If not, there's no way to force it.

[dchardware]

This means that all traffic is enrcypted, if the tracker using https, and the clients forcing protocol encryption?

If the tracker CAN use https (means no requiring using https on web login or tracker messages), is there any way to configure utorrent to use https instead of http?

I write the full story to understand: in Hungray UPC and other ISPs causing many trouble by traffic shaping and other attacks to the bittorrent network. We want to make a tracker fully secure, but I don'T know clients using many uploader (rtorrent, libtorrent etc.) are also can decode https tracker messages like utorrent can. This traffic shaping thing is not a problem of the uploaders at all.

So we want that the supporter clients CAN connect to, and get messages from the tracker via https, but if some client do not support this option, it can still connect using regular http messages. Like a web page: I can conect via http or https if my browser supports it.

Is this possible?

Thank you!

Dchard

[Firon]

Uh, if the tracker supports https, change the tracker url to that.

[dchardware]

Firon: you mean if the tracker supports https, the user should change the tracker url http://.... to https://... in torrent settings, and it will work?

Can you tell me what type of https utorrent can work with? (http over SSL, http over TLS), or any other specification we need to know to set this up properly?

And another thing: I know that this is not a feature request topic, but I think a switch next where protocol encryption's options are, should be very good. Something like this:

Tracker message encryption:

- Regular (unsecure)

- Secured (using SSL, TLS or whatever utorrent supports)

So if the tracker supports it, I can switch it on in the client.

Can you say something about this?

Thank you!

Dchard

[Firon]

SSL and TLS are basically the same thing.

And yes, just change the url to https (and remove the port number if specified, some trackers add :80). Very few support it, though.

And no, that option is a bad idea.

[dchardware]

"Very few support it"

Why? I mean if this is the final hole to fix, and give a fully encrypted p2p network to the public, then why very few tracker support it? Is it resource consuming or why?

"that option is a bad idea"

For me it is very annoying to change http to https on many torrents manually one by one. But maybe there is another option to speed up this manual method. If so, please tell me.

Probably a better option, if utorrent can do a simple check on the tracker, and if it support https, then use the message encryption default. (maybe a switch for this should be nice either).

Please expand me why is this a bad idea.

Thank you!

Dchard