I just saw the new release and first thing I did was read the change log from 4.4 up. I got excited when I saw that it was not longer running as root and then disappointed when I saw it returned. I have been running as a subsonic user for about a year myself and I'm hoping I can help to resolve the problems people had with leaving the root user behind. I wanted to start a new thread since the issues I have found seem to be mixed with other topics and I think it would be easier to work on this problem separately.
One of the problems I saw was updating album covers. I run into this problem myself on occasion if I copy a new folder into my music folder. The permissions follow the folder which has my user and group listed on it. Check the User and Group owners of the folder and then pick one of the 4 ways to fix this, substitute words in all caps for your info:
1. Change the user to subsonic "sudo chown -R subsonic FOLDER" and make sure it has write permissions "sudo chmod -R u+rw FOLDER"
2. Add the subsonic user to the group that owns the files "sudo adduser subsonic GROUP", and make sure the group can write "sudo chmod -R g+rw FOLDER"
3. Change the group to one subsonic is already a member "sudo chgrp -R GROUP FOLDER", and make sure the group can write "sudo chmod -R g+rw FOLDER"
4. Give everyone write access "sudo chmod -R a+rw FOLDER"
In my case since my music is already in my mythtv directory, I choose method 2, added subsonic to the mythtv group and made sure the group has write access. The "-R" stands for recursive which sets the options for all the subfolders and files.
The second issue I saw was accessing USB drives and using https. I believe this could be fixed with the correct groups. Can anyone who had this problem list the groups that subsonic is a member of "groups subsonic"? I'm thinking adding subsonic to the plugdev group may fix this. If not, a good way to test would be to add subsonic to all the groups, then remove them one at a time until it no longer works. I'll try and create this situation and test when I get some time.
The last issue I saw was not able to create https/ssl while running as subsonic. I'm not sure a group permission would resolve this, but it would probably be the www-data group if so.. This might take modifing some code or script to initiate the https/ssl as root seperately from running the subsonic thread.
Imho, https adds extra processing where it is not needed. I personally use 3 levels of passwords, complex for computer logins/email accounts, moderate for social sites/IMs and simple passwords for things I'm not worried to much about like forums. I use and admin account for modifying users and settings in subsonic with a complex password that I rarely log in with and usually only on my lan, then a simple password for my daily account which can play and download music only. If you crack my simple password the worst you could do is mess up my playlists, but good luck cracking my admin account. That's just my preference though.
Please bring any other issues you have had on linux with the 4.4 beta2 on linux as well and hopefully we can help to create a root free subsonic!
ralyon
