Deluge client assumes uses local file system when connected to server over ssh tunnel

[rpglover64]

I am using Deluge 1.3.5 with libtorrent 0.15.9.0 for the gtk frontend as well as for the server backend.

If I use ssh -L 58846:localhost:58846 server to forward the deluge port and connect to the server's deluged process with the gtk frontend, and then try to set the download directory, it lets me browse the directory tree on the client, not on the server.

Worse, it the download directory that has been set does not exist on the client, the client changes it.

[Calum]

The ​Thinclient guide recommends 127.0.0.2 for ssh connections.

[rpglover64]

That feels like a horribly hacky workaround (although it does solve the problem). Couldn't the hostlist.conf file have an additional parameter on a host for if it's local or not? The hostlist ui could have a checkbox, which defaults to local for localhost and remote for everything else, but can be toggled.

[Calum]

Adds unnecessary complexity to the code as the RPC connection is already secure.

[rpglover64]

There are reasons to use ssh forwarding other than security; in particular, I'm using it to avoid forwarding that port in my router.

It's also plausible that I don't have root on the machine I'm running the client on (for example, a public Ubuntu desktop).