We should put them in /var/run like other daemons. Makes things more secure and also easier to handle in SELinux.
Most of the work was done on bug 4780, but there is some cleanup and testing left that can be done on this bug.
Committed in r28235. Going to do a test with a nightly build before I close the bug.
Nightly build works. Tester should verify that you can still log in. SELinux should be enforcing, and you should verify that the socket files and intermediate directories get the correct context.
Tested using server build 4290 on CentOS 6.4 with selinux enforcing. /var/run/thinlinc/master is populated with user socket with the correct SELinux context and there is no problems with logons.. Also verified that tlwebadm creates a user socket for root user when logging into Web admin ui.
Creation of the intermediate directories do not compensate for a restrictive umask.
(In reply to comment #8) > Creation of the intermediate directories do not compensate for a restrictive > umask. r28979. Besides retesting the normal stuff, the tester should make sure things work with a restrictive umask (e.g. 0077 or 0777). Remember to remove /var/run/thinlinc, and to verify that vsmserver actually gets the expected umask (need to hack /etc/bashrc on RH systems for example).
(In reply to comment #9) > (In reply to comment #8) > > Creation of the intermediate directories do not compensate for a restrictive > > umask. > > r28979. > > Besides retesting the normal stuff, the tester should make sure things work > with a restrictive umask (e.g. 0077 or 0777). Remember to remove > /var/run/thinlinc, and to verify that vsmserver actually gets the expected > umask (need to hack /etc/bashrc on RH systems for example). Tested on RHEL 6 - Edited /etc/profiles and added umask 77 - Installed rc2 - Verified that /var/run/thinlinc have wrong permissions; 700 - Verified that a login with native client failed with permission denied in tlclient.log. - Updated installation with rc3 - Deleted /var/run/thinlinc between each restart of services and verified that each service created the directories with correct permissions. - Verified that i successfully could log into a session.
(In reply to comment #10) Also verified that tlwebaccess and tlwebadm (tlstunnel) works as expected.