Replies: 2 comments
-
You can share the entire runtime directory instead. Anyways, with the implementation of JSON-RPC, I think it is safe now to send raw torrent metadata directly via socket, so there is no need for rTorrent to access Flood's temporary directory. I plan to implement the change in the next minor release. This basically reverts to the pre-4.0 behavior, and, unfortunately, as a result, XMLRPC users may encounter troubles with larger torrents. On the other hand, the change would eliminate many cases of filesystem access/context issues. It also makes it possible to tighten access control of Flood's runtime directory: https://github.com/jesec/flood/projects/7#card-54370342 . |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply :) Yes, right now I share Flood's Anyway, I'm genuinely very happy to see that this project will switch to using XMLRPC implementation for sending torrent/magnets : it feels more 'cloudy' by using the filesystem less. Oh god, I can't wait to use Flood's future release ! Also, it's nice to see that this project is getting more and more 'security measures' : thoses should be more appreciated, and it should be more seen elsewhere. I noticed that at a lot of people thinks that using docker/k8s is just a way to forget about security. Have a nice day :) |
Beta Was this translation helpful? Give feedback.
-
Hello,
In config.ts we can see that
tempPath
is build by using<rundir>/temp/
directory : this directory seems to be used for sending magnets and torrents.Would it be possible to have a
--tempdir
orFLOOD_OPTION_tempdir
to customize this directory ?This way, using docker : we will be able to share this directory using volumes.
For example, with a small docker-compose.yml configuration :
Thank you and have a nice day :)
Beta Was this translation helpful? Give feedback.
All reactions