#2149: deluge ignoring proxy settings

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by keretamalam):

I am about to leave and cannot look into this further right now, but I do
want to mention that relying on pkg-config itself is not a problem (as you
said, we also use it later), the problem is that on some systems, the .pc
file for pkg-config is supplying wrong information (whereas on yours, it's
botan-config that is wrong), so that's why I'm trying to make it work with
both (while one of them is bad).
[http://maskodoq.blogspot.com/2014/03/unit-link-terbaik-di-indonesia.html
Unit Link Terbaik di Indonesia Commonwealth Life Investra Link]
[http://maskodoq.blogspot.com/2013/07/CiptoJunaedy.html Cipto Junaedy]
[http://etnisjawa.blogspot.com/2013/08/apakah-cipto-junaedy-bohong.html
Cipto Junaedy]

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by sslx):

Deluge totaly ignores socks5 proxy.
I'm trying to use socks5 with privateinternetaccess.
My real ip shows up on the swarm, and Deluge starts downloading even if I
put wrong username password.
I tested on uTorrent, and it works as expected.
If I put correct info, my real ip doesn't show up, and if I put wrong
user/pass it doesn't work.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:23>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by WeissmanScore):

Woah. That's not good... So this is confirmed and there is no way to
mitigate? I am going to kill every instance I have running until I hear
this is resolved.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:25>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by thero):

Wow. How can a critical bug like this still be around 4 years later?

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:26>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by DeadlyKnapsack):

This is absolutely ridiculous. You are playing around with other people's
privacy. I will immediately stop using Deluge.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:27>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by dg7dg):

Tested via an account with PrivateInternetAccess.com, and then checking
access to a magnet link on http://ipmagnet.services.cbcdn.com/

This bug still occurs; the Socks5 proxy setting is ignored by Deluge.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:28>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by Cas):

Ok I think I see the issue, since 0.16 libtorrent has only one proxy
setting and the old way that Deluge sets the proxy settings using `peer`,
`web` etc when applied are overwriting the previous values so if `dht` is
empty that is likely to be the last item set which would clear the values.

The workaround for now is to set all the proxies `peer`, `web`, `tracker`,
`dht` to the same values.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:29>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: critical | Milestone: not applicable
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------------

Comment (by arliweng):

tested 1.3.14 with libtorrent-rasterbar 1.1.1 and 1.1.3(from github) on
archlinux, problem still, tracker proxy can't save

[INFO ] 17:37:39 main:130 Deluge ui 1.3.14
...
[DEBUG ] 17:37:39 preferencesmanager:496 Setting peer proxy settings:
{u'username': u'', u'password': u'', u'type': 0, u'port': 8080,
u'hostname': u''}
[WARNING ] 17:37:39 preferencesmanager:486 Using libtorrent >= 0.16
ignores proxy settings for tracker

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:30>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+--------------------
Reporter: rm | Owner:
Type: bug | Status: closed
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: Fixed | Keywords: proxy
-------------------------+--------------------
Changes (by Cas):

* status: new => closed
* resolution: => Fixed
* milestone: not applicable => 1.3.14


Comment:

Did you read my last comment? There is only one proxy now. So peer proxy
values are now used for all proxies. See #2991

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:31>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------
Changes (by DeadlyKnapsack):

* status: closed => reopened
* resolution: Fixed =>

Post by Deluge
Did you read my last comment? There is only one proxy now. So peer proxy

values are now used for all proxies. See #2991
And still the IP is leaked! Even with the latest version 1.3.15. No matter
what I do. It doesn't have to do with the settings. I can clearly see my
IP in the Torrent swarm, when checking from different client downloading
the same torrent. Why aren't you giving this more attention? This should
clearly be one of the highest priorities. The fact that I know it is
leaking, prevents me from using Deluge, so I can be safe. But what about
all the other users who perhaps unknowingly are unable to hide their IP in
the swarm?!

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:32>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------

Ok I think I see the issue, since libtorrent 0.16 there is only one

proxy setting and the old way that Deluge sets the proxy settings using
`peer`, `web` etc when applied are overwriting the previous values so if
`dht` is empty that is likely to be the last item set which would clear
the values.

The workaround for now is to set all the proxies `peer`, `web`,

`tracker`, `dht` to the same values.

This definitely applies to lt 1.1. and 1.0.
libtorrent issue: https://github.com/arvidn/libtorrent/issues/1646
1.3-stable fix: [8565eccb3de9]

This is incorrect in my situation. Even with identical values for all the
proxies, the IP is visible.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:33>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------

Comment (by dg7dg):

Let us be honest here :) This bug has been open for five years. It's not a
stretch to say that you cannot trust Deluge with your privacy, now or in
the future.

Under no circumstances I blame the developers for not fixing the bug. I do
blame them for offering a no-working feature for five years.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:34>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Bruno Navert]

Well turns out this is pretty easy to fix. As mentioned above, deluge is
still parsing all 4 proxy settings and setting the blank ones, which
overwrites the actual proxy you set.

This can be changed directly in the Python script with a one-line change.

In my installation (raspberry pi, with deluged version 1.3.10-3+deb8u1) you
can find the line to modify per below.

Note I haven't tried installing the latest version (1.3.15) from source, I
merely hacked the installed 1.3.10 package and it worked for me.

$ grep -nA1 "setting .* proxy settings"
/usr/lib/python2.7/dist-packages/deluge/core/preferencesmanager.py
482: log.debug("setting %s proxy settings", k)
483- getattr(self.session, "set_%s_proxy" %
k)(proxy_settings)

Then just edit this file:

sudo nano /usr/lib/python2.7/dist-packages/deluge/core/preferencesmanager.py

Type Ctrl+_ then 482 to go to the line 482 (change per grep output if yours
differs)

Then, change lines 482 & 483 like this (add the if statement above line
482, then indent by 4 spaces the two lines following - this is important,
Python is indentation sensitive)

if len(proxy_settings.hostname) > 0:
log.debug("setting %s proxy settings", k)
getattr(self.session, "set_%s_proxy" % k)(proxy_settings)

Only the first line (the "if") is new, the rest you just indent them 4
spaces to the right

Then kill and restart the deluge daemon, and voila, proxy settings now work.

You can verify using the torrent IP checkers like this one:
http://checkmytorrentip.upcoil.com/

Post by Deluge
#2149: deluge ignoring proxy settings
-------------------------+----------------------
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------
Let us be honest here :) This bug has been open for five years. It's not a
stretch to say that you cannot trust Deluge with your privacy, now or in
the future.
Under no circumstances I blame the developers for not fixing the bug. I do
blame them for offering a no-working feature for five years.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:34>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------

Post by Deluge
Let us be honest here :) This bug has been open for five years. It's not

a stretch to say that you cannot trust Deluge with your privacy, now or in
the future.

Post by Deluge
Under no circumstances I blame the developers for not fixing the bug. I

do blame them for offering a no-working feature for five years.

Oh, I blame them for claiming the fix works. As a user, I should not be
doublechecking the security.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:35>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------
Changes (by andrewsomething):

* cc: a.starr.b@… (added)


--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:36>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------

Comment (by slajerek):

Wow, I did not expect that. Does not work for me either:

[INFO ] 23:59:01 daemon:124 Deluge daemon 1.3.10

It is completely ignoring my Proxy settings.

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:37>
Deluge <http://deluge-torrent.org/>
Deluge Project

[Deluge]

#2149: deluge ignoring proxy settings
-------------------------+----------------------
Reporter: rm | Owner:
Type: bug | Status: reopened
Priority: critical | Milestone: 1.3.14
Component: libtorrent | Version: 1.3.5
Resolution: | Keywords: proxy
-------------------------+----------------------

Comment (by andocromn):

try using the ltConfig plugin to set the anonymous_mode and force_proxy
settings, this should accomplish what you want. references below

http://forum.deluge-torrent.org/viewtopic.php?f=9&t=42887
http://www.libtorrent.org/reference-Settings.html

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149#comment:38>
Deluge <http://deluge-torrent.org/>
Deluge Project