Running transmission-daemon as nobody

Discussion in 'Tomato Firmware' started by menses, Apr 6, 2013.

  1. menses

    menses LI Guru Member

    Are there any drawbacks to running transmission-daemon as non-root for example as nobody?
    I feel uneasy that it's run as root by default.
  2. menses

    menses LI Guru Member

    Here's how I eventually did it.

    Installed sudo from Entware:
    opkg install sudo

    Added the appropriate sudo command as the value of the custom binary field at http://tomato/nas-bittorrent.asp
    sudo -u nobody /opt/bin
    This is a small hack that will generate the desired start up command in /tmp/

    And finally made sure the permissions were correct for the Transmission directory.
    chown -R root:nobody /tmp/mnt/harddisk/transmission/
    chmod -R g+w /tmp/mnt/harddisk/transmission/
    (Optionally you might want to play with the umask setting in Transmission's config file.)

    Works as expected.
  3. Monk E. Boy

    Monk E. Boy Network Guru Member

    ??? chown's format is user:group so in your example you've set root:nobody which means user "root" and group "nobody."

    If you were running as the user nobody you would want to chown nobody:nobody. root always has permissions to do everything on the system everywhere, so don't worry about giving root permissions.
  4. menses

    menses LI Guru Member

    I had some issues with samba if root was not the user.
    nobody as the group seems to work fine.

    Edit: But transmission-daemon creates all new files anyway with nobody:nobody so it's true that setting the whole directory as nobody:nobody would be more consistent. The problems with samba seem to be with files where others have no permissions at all. I should probably set transmission umask to 2 or 0.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice