libtorrent 1.x.x (IP Leak)

[doadin]

Hello, i just wanted to first says thanks for adding the request i made for anonymous mode. Theres one more though that i think should be taken into consideration. And that is the "force-proxy". This setting unlike anon mode isnt available with ltconfig and poses a privacy risk when paired with libtorrent 1.0+ builds. And as some users are using 1.0+ and you have made a ppa for linux users available it might see more use. Under 1.0+ without "force-proxy" and only anon mode things such as dht can be enabled and leak a users IP. Adding this while for what ever reason isnt possible in ltconfig it does work from preferences as seen by my own personal build.

[Cas]

The fact it's not in ltconfig means that it's missing from the python bindings, I am surprised that you can actually set it. I have asked the lt dev if he can add it before the next release.

[doadin]

Yea i noticed it a while ago and then like a week ago the qbittorrent devs did the same for their client. Im not 100% sure but in my testing it seemed to work with deluge too i havent done anything with like wireshark or anything but with just anon mode DHT was able to connect to nodes, with the force-proxy added to prefferences it didnt work despite it still being enabled in preferences which is exactly what the issue was in qbittorrent. In qbittorrent they have it set to disable things like dht in prefferences to avoid leaks however a user noticed if they changed the config manually it could still be enabled.(since in libtorrent1.0+ anon mode acts different) And since the options are seperate in libtorrent1.0 it was able to make connections. In deluge there is no check like that so haveing deluge + libtorrent1.0+, the same can be done just from the UI. If the next stable version of deluge is going to be still based on lt0.16.xx you may want to consider adding a check like qbittorrent has to set DHT to false if anon mode/proxy is set.

[doadin]

Its in there now.
http://sourceforge.net/p/libtorrent/code/10269/