Suggestions from a long time Vuze user who recently swichted

Suggestions and discussion of future versions

Suggestions from a long time Vuze user who recently swichted

Postby Flow » Sat Apr 14, 2012 10:49 am

First I'd like to thank you for this great torrent client! I am really happy that I found deluge after searching for a replacement for my Vuze headless setup. There are a few suggestions that I came up with while switching to deluge:

default_daemon is not exported as setting to the web-ui
While configuring transdroid to use deluge I was confused by the fact that there are two steps needed for authentication: The first to connect to the web-ui and the seconds to connect to deluged. I wondered how transdroid should do the seconds step. This also come up in #deluge. And johnnyg added it as new FAQ entry: http://dev.deluge-torrent.org/wiki/Faq# ... ificdaemon
But I really like to see this as an setting in the web-ui. I think that many new deluge users are hit this issue, when they setup transdroid or chrome's remote torrent adder to connect to deluge web-ui, since the web-ui is really just a client to server part of deluge. There needs to be an easy way to configure the default_daemon.

Is there already a ticket for the issues above? If not, is it ok if I create one?

Used ports are not documented
Some ports that are used by deluge are not documented. At least I can't find information about the ports 6771, 46586, 49693, 59035 (all udp). Basically I'd like to know which port's are needed for forwarding for the DHT. But an explanation what the other ports are for would be helpful.
Code: Select all
netstat -lntup |grep 9404
tcp        0      0 0.0.0.0:6882            0.0.0.0:*               LISTEN      9404/python2.7     
tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN      9404/python2.7     
tcp        0      0 0.0.0.0:58846           0.0.0.0:*               LISTEN      9404/python2.7     
tcp6       0      0 :::6882                 :::*                    LISTEN      9404/python2.7     
udp        0      0 192.168.100.13:49693    0.0.0.0:*                           9404/python2.7     
udp        0      0 192.168.100.13:6771     0.0.0.0:*                           9404/python2.7     
udp        0      0 127.0.0.1:6771          0.0.0.0:*                           9404/python2.7     
udp        0      0 0.0.0.0:6771            0.0.0.0:*                           9404/python2.7     
udp        0      0 0.0.0.0:59035           0.0.0.0:*                           9404/python2.7     
udp        0      0 0.0.0.0:6882            0.0.0.0:*                           9404/python2.7     
udp        0      0 127.0.0.1:46586         0.0.0.0:*                           9404/python2.7


JSON-RPC Interface encrypted?
Is the communication via JSON-RPC encrypted? It's not really an issue, since I use the web-ui with ssl for communication via transdroid, but it would be good to know...

No Flattr Donation Button
This is the most important issue: I don't want to use and support paypal. But I am eager to give away my money via flattr. If you could add a flattr button, that would be awesome! :-)

Keep up the good work!
Flow
New User
New User
 
Posts: 2
Joined: Sat Apr 14, 2012 10:10 am

Re: RPC SSL and encryption

Postby benevolentsquirrel » Wed Feb 05, 2014 10:29 pm

I'm not sure if this is the correct board, but:

JSON-RPC Interface encrypted?


FWIW, I've wondered the exact same thing. A search of the site and forums here, as you no doubt have discovered, turns up no answer.

The docs describe the messages sent in the RPC protocol as "zlib compressed rencoded strings" so I'm guessing that at least they're not in plain text.
benevolentsquirrel
New User
New User
 
Posts: 6
Joined: Wed Feb 05, 2014 10:17 pm


Return to Development

Who is online

Users browsing this forum: Lumia and 4 guests