HTTPS Support in Web Client

[John Clay]

HTTPS support in the web client would be nice.

Ideally, you would be able to generate a self-signed certificate, or use a properly signed certificate.

[fijam]

Oh I dunno. It's fairly trivial to set up e.g. nginx as a https proxy. Here is an example configuration file with the added benefit of basic auth: ​http://pastebin.com/NQticLcq . On the transmission side: rpc-bind-address: 127.0.0.1

[Flow]

Currently the user credentials of transmission can easily be sniffed, when using for example Chrome's "Remote Torrent Adder" from an unsecured public WiFi? network. Allowing easy hijacking of the users transmission installation.

Sure, one could go the way with an preceding proxy to enable encryption. But SSL support should be a standard feature of every remote controllable service, given the fact that this is an important security feature. Twitter and Facebook had to learn it the hard way, why make the same mistake?

[jordan]

This won't happen until after libevent 2.1 switches to ​https://github.com/ellzey/libevhtp, which supports ssl

[alesnav]

Hello! Any news about this enhancement? Is there a date scheduled for this improvement?

Thanks

[bthusby]

Yes, we need this! I want to secure all the web interfaces on my Synology NAS. Transmission is the only one left unencrypted... Please :)