As an experienced CMS website operation personnel in the field of information security, I am well aware of the importance of system stability and permission management for website security and operational efficiency. Regardingstart.shThe user identity and permission management of the AnQiCMS process running script, I can elaborate on it in detail.
AnQiCMS as a system developed based on the Go language, its operation and permission settings are different from traditional PHP applications, but the core security concept is the same: the principle of least privilege.start.sh脚本作为AnQiCMS在Linux环境下的启动和守护脚本，其运行的用户身份直接关系到AnQiCMS进程在操作系统层面的权限。
start.shThe main responsibility of the script is to check if the AnQiCMS process is running, if not, start it and run it in the background. The user identity of the executor of this script and the AnQiCMS main process started thereby is usually determined in the following ways:
In the hosting environment, such as Baota panel or aaPanel and other server management panels, when deploying AnQiCMS, these panels usually provide an option to specify the user for the website or Go project to run. According to the documentation, the deployment guide of Baota panel explicitly states that the 'Running User Selection'}]wwwThis means that in these managed panel environments,start.shthe script and the AnQiCMS main program it starts will bewwwThe identity of a user (or similar low-privileged Web service user) is running. This is a**practical, becausewwwUsers usually only have the most basic permissions required to run web services, thereby effectively limiting the potential system damage even if the AnQiCMS process is compromised.
While deploying AnQiCMS manually or in a command-line environment,start.shthe user running the script depends on how you configure and execute it. If you run the command ascrontab -ecommand forstart.shAdd scheduled task, then the task will run under the identity of the creator of thecrontabentry. Normally, we do not recommend running AnQiCMS or any web service process withrootUsers run with identity, becauserootUsers have the highest system privileges, and if misused, it can lead to catastrophic consequences. It is recommended to create a dedicated low-privileged user (for exampleanqicmsorwww), and willstart.shThe schedule task configuration is under this user, or throughsudo -u <username> start.shthis method to execute as the specified user.
Regardless of which deployment method is used,start.shThe AnQiCMS process started by the script, the access permissions to the file system are crucial. The user account running AnQiCMS must have the following permissions:anqicmsBinary files andstart.shscript execution permissions; for system log files (such ascheck.log/running.log) and AnQiCMS is used for storing user uploaded files, cache data, configuration information, and other directory write permissions.The correct permission settings are the foundation for the stable operation and data security of AnQiCMS.
Transcending the process user identity at the operating system level, AnQiCMS also establishes a fine-grained application layer permission management mechanism in itself.The document explicitly states that the system supports "admin group and permission divisionThis means that in the AnQiCMS backend, you can create different user groups and assign specific operation permissions to each user group, such as content editing, content publishing, template modification, system settings, etc.This hierarchical permission control greatly enhances the operational security of the website, ensuring that each backend user can only perform operations within their scope of responsibility, thereby reducing the risk of accidental or malicious operations.
AnQiCMS's permission management is also reflected in the multi-site management function.An AnQiCMS instance can manage multiple independent websites, each of which may have its own administrator account and password, achieving data isolation and independent permission systems.In addition, the built-in 'User Group Management and VIP System' further expands the application scenarios of permission management, allowing access permissions to specific content to be restricted based on user identity or payment status, thereby supporting content monetization and membership services.In summary, AnQiCMS provides comprehensive permission control capabilities from the operating system process user to the application layer background user, aiming to build a safe and efficient content management environment for users.
Frequently Asked Questions
Does AnQiCMS process support running as root user?From a technical perspective, the AnQiCMS process can be run as the root user, but it is strongly not recommended to do so.The root user has the highest system privileges. Once AnQiCMS or its dependent components have a security vulnerability, an attacker may exploit this vulnerability to completely control the entire server.wwwusers) to run the AnQiCMS process.
How to change the running user identity of AnQiCMS process?The process of changing the running user identity of AnQiCMS depends on your deployment method.If you use panel management tools such as Baota Panel or aaPanel, you can directly select or specify the running user in the project configuration of the panel.crontabdaemon, you need to make sure that thestart.shscript is added to the required user'scrontab(specified bycrontab -e(Executed under this user)，or use it before the start commandsudo -u <username>to specify the running user.
What permissions does the AnQiCMS process need on the file system?
The AnQiCMS process needs appropriate permissions for the following files and directories: for the AnQiCMS main program binary file andstart.shScript read and execute permissions; for log files (such ascheck.log/running.log）、User uploaded file directory, cache directory, and directories containing configuration information, etc., have write permission.Ensure that these directories and files are owned by the user running the AnQiCMS process, and the permission settings follow the principle of least privilege to avoid unnecessary global write permissions.