#1089: authentication
--------------------------+-------------------------------------------------
Reporter: martinlindhe | Owner: damoxc
Type: bug | Status: accepted
Priority: major | Milestone: 1.3.0
Component: webui | Version: 1.2.0_rc4
Keywords: |
--------------------------+-------------------------------------------------
Comment(by martinlindhe):
Okay thanks for the clarification.
I think i got confused because i assumed the architecture was that the
ui's where clients connecting to the deluge server:
deluged <-authentication-> gtk-ui
\--> web-ui
but correct me if i'm wrong, the architecture is now rather
deluged <-authentication-> gtk-ui
\--> deluge-web (daemon too) <-authentication 2->
web-ui
i can see this allows me to setup one web-ui where i can control multiple
deluge servers.
however it breaks the security model by assuming a setup with multiple
username&passwords compromised by only one password to the web ui.
also that ability to control multiple machines running deluge quite a
power-user feature. it's quite odd to me to first connect to a server (a
web server), then using the web application in order to connect to the
server (me and most other users are running the deluged and deluge-web
dameons on the same machine).
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/1089#comment:3>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
