Updated to rTorrent 0.9 settings (missed one)

Andrés Suero
2019-12-06 17:08:38 -03:00
parent 55632b110e
commit aa5fcc94f6
+1 -1
@@ -117,7 +117,7 @@ The web server will now route xmlrpc requests to rtorrent, which is listening on
:bangbang: **Never** bind the SCGI port to anything *but* 127.0.0.1. Anyone who can send rtorrent xmlrpc commands does have the ability to execute code with the privileges of the user running rtorrent. If you want to be more secure on principle, use UNIX domain sockets instead of TCP ports (see below).
You may also use `scgi_local = /foo/bar` to create a local domain socket, which supports file permissions. Set the rw permissions of the directory the socket will reside in to only allow the necessary processes. This is the recommended way of using XMLRPC with rtorrent, though not all http servers support local domain sockets for scgi.
You may also use `network.scgi.open_local = /foo/bar` to create a local domain socket, which supports file permissions. Set the rw permissions of the directory the socket will reside in to only allow the necessary processes. This is the recommended way of using XMLRPC with rtorrent, though not all http servers support local domain sockets for scgi.
## Test and usage