I've been using deluge for some time and I am running it with the following setup:
deluged on my Raspberry PI running raspbian (which is based on Debian testing).
deluge-gtk on my desktop running debian unstable.
This worked fine until I updated both machines some days ago and deluged is now running 1.3.9 and deluge-gtk is 1.3.10.
Whenever I try to connect to deluged using deluge-gtk I get the following error:
Code: Select all
[INFO ] 13:20:18 rpcserver:203 Deluge Client connection made from: 192.168.1.120:41509
[INFO ] 13:20:18 rpcserver:223 Deluge client disconnected: [('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake failure')]
Is this related somehow? Or is it some kind of other bug I've encountered?commit 26f5be17609a8312c4ba06aa120ed208cd7876f2
Author: Calum Lind <...>
Date: Wed Oct 15 18:44:02 2014 +0100
[WebUI] Security update for POODLE vulnerability
WebUI with HTTPS enabled is vulnerable to POODLE (CVE-2014-3566), so switch from
SSLv3 to TLSv1.
Also I wonder if there is any policy regarding compatability between versions? Should all users be forced to use the exact same revision (for instance 1.3.10) on the client+daemon or should the users only be forced to use the same minor version (i.e. 1.3.X)?