Community « Discussion forum « Installation support « Permissions after incremental upgrade [fixed] «
Comment: Permissions after incremental upgrade [fixed]
YACS has to get rights to files to modify them. This includes scripts for software update and configuration changes. For normal operations, YACS only has to save files and images in respective directories with the same names.
This allows for several permission shemes, depending of run-time constraints.
Most of the time YACS rights to the file system are those of the user/group assigned to the web daemon. A common setup in the case of Apache is to have YACS rights inherited from
To achieve maximum security levels, you could change ownership of all of the YACS directory to the user/group set for the web daemon (e.g.,
Then use the
This allows for several permission shemes, depending of run-time constraints.
Most of the time YACS rights to the file system are those of the user/group assigned to the web daemon. A common setup in the case of Apache is to have YACS rights inherited from
www-data.To achieve maximum security levels, you could change ownership of all of the YACS directory to the user/group set for the web daemon (e.g.,
www-data/www-data is quite common), through the chown -R command to make it recursive.Then use the
chmod -R 770 to ensure that the world has no right on this part of the file system. To limit rights to the daemon user only you can even use chmod -R 700 which is the safest.
by Bernard on Dec. 17 2006
