Hi!
Thanks a lot for taking a look over the package.
As this is my first package, forgive me if I need a little
hand-holding here, especially with regards to the filesystem hierarchy
and safe permissions:
> I'm not overly joyed by seeing the symlink farm in /etc pointing
> to /usr/share though. This is simply wrong as the files are
> not configuration files (which is why they don't live in
> /etc to begin with). Whatever needs these files should IMHO
> be fixed up to look for the in the correct location (so
> you can drop the symlinks).
>
> Making /usr/share/ruTorrent world-writable is the main issue though.
> This will never end well. You need to think about security and
> how you manage permissions somehow. This is in my opinion a
> blocker for uploading your package.
So ruTorrent/share/settings, ruTorrent/share/torrents, and
ruTorrent/share/users are all supposed to be "accessible for reading
and writing for both rtorrent and webserver users."
This is why I placed them in /usr/share/ruTorrent/{settings, torrents,
users} and gave world-writable permissions.
But this was mostly just guesswork based on the filesystem hierarchy
standard manpages. Could you give me some advice on the correct
placement and permissions of such files that should be modifiable by
both the web-server and the user who is running the rtorrent CLI?
[Note: rTorrent != ruTorrent]
Reference:
https://github.com/Novik/ruTorrent/wiki/Config#multiuser-and-singleuser-configuration
> Not sure but if nginx has '*-available' '*-enabled' configuration
> pattern but I think it does and then maybe there's a way to
> provide a snippet for '*-available' that a user can in normal
> cases just enable. This should simplify for the user over having
> to read up and manually configure nginx.
Great idea. So just placing an nginx config file in rutorrent.examples
and suggesting that the user create a symlink from
/etc/nginx/sites-enabled to this file if they wish to use nginx +
default configuration?
Thanks so much for your help,
-Taylor
