Hello, I've been working on an app to control multiple types of torrent servers
via their RPCs.
I'm filing this issue because the way I am currently controlling rTorrent, the
same way ruTorrent itself controls rTorrent, is via POSTing to /RPC2. I am
using this for testing purposes only, since RPC2 is unsecured and, if you knew
that someone else had ruTorrent on a certain port, you'd definitely be able to
wreak havoc upon their torrents.
So, to fix this issue before it is created, I would like to ask that you
implement two files, one called action.php and one called list.php, with list
returning all of the information that ruTorrent itself asks for with
d.multicall and action executing a method passed to it, e.g.
action.php?method=stop&hash=3B0D90E526DD21F768D.
The benefits of this will be that when a user uses an htaccess and an htpasswd
file, others will not be able to mess around with their torrents.
Original issue reported on code.google.com by carlo.to...@gmail.com on 1 Aug 2013 at 5:02
Original issue reported on code.google.com by
carlo.to...@gmail.com
on 1 Aug 2013 at 5:02