Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#2233 closed feature-request (WontFix)

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

Reported by: rpglover64 Owned by:
Priority: minor Milestone: Future
Component: GTK UI Version: 1.3.5
Keywords: Cc:

Description

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.

Change History (6)

comment:1 Changed 5 years ago by rpglover64

  • Component changed from other to gtkui
  • Version changed from other (please specify) to 1.3.5

comment:2 Changed 5 years ago by Cas

  • Resolution set to invalid
  • Status changed from new to closed

The Thinclient guide recommends 127.0.0.2 for ssh connections.

comment:3 Changed 5 years ago by rpglover64

  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Type changed from bug to feature-request

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.

comment:4 Changed 5 years ago by Cas

  • Resolution set to wontfix
  • Status changed from reopened to closed

comment:5 Changed 5 years ago by Cas

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

comment:6 Changed 5 years ago by 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).

Note: See TracTickets for help on using tickets.