Custom Query (2449 matches)
Results (379 - 381 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2784 | Fixed | [Execute] Escape call parameters for Windows | ||
| Description |
From: http://forum.deluge-torrent.org/viewtopic.php?f=9&t=48203&p=221405 To expand on my prior post, I'm talking about escaping required by the Windows OS command line. Unless an ampersand is escaped, Windows interprets it as separating 2 commands, so it runs everything before the ampersand as one command and everything after it as another command (ref: http://www.robvanderwoude.com/condexec.php). So when the execute plugin tries to run a command and the filename has an ampersand in it, Windows tries to run it as 2 separate and partial commands. I have tested my script by calling it manually, and if it is called with the ampersand properly escaped, my script works fine. So the problem isn't my script as you suggested. And it's not an encoding issue. It's a Windows-specific command line escaping issue with the plugin. |
|||
| #2783 | Fixed | Case insensitive sorting for column Name | ||
| Description |
As per title, was fixed already for WebUI: #2103 |
|||
| #2782 | Fixed | HTTPS negotiates with incorrect cipher | ||
| Description |
Snippet from original forum thread: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=51545 I recently updated to v 1.3.12 and noticed that the problem was still occurring which brought me back here. It's been quite a while since I looked at this but, my recollection of the problem was that the web-ui server was using some old/weird stuff to initialise twisted which meant it wasn't getting a full list of available safe cipher suites. I believe the problem was caused by the "safe" cipher suites provided by the latest version of openssl not overlapping particularly well with those being allowed by the implementation of twisted in place in deluge and those that firefox would allow. I removed the ServerContextFactory class (which was what I saw causing the problem) and re-wrote start_ssl() to set the certificate options itself and let twisted handle everything else like deciding which cipher suites were OK to use. This added a whole bunch of additional cipher suites available for negotiation. With the current configuration the cipher that is negotiated is TLS_RSA_WITH_AES_128_CBC_SHA which probably shouldn't be used even if it did work, with my update it negotiates TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. At the time I had planned on submitting a patch to the git repository but I wasn't able to get the develop branch to run even before I implemented my changes so I just left it as there didn't seem to be any active development at the time. |
|||
