Linux user, group, permission management
1. Basic knowledge:
1. 3A authentication: user authentication, authorization, audit
2. User category, identification, and name resolution database
1. User Category: administrator, ordinary user (ordinary users can be divided into: system users, login users).
2. User ID: UserID UID, generally expressed in 16bits binary (its range is: 0-65535);
Administrator ID: 0;
Ordinary user ID range: 1-65535
System User ID Range: 1-499 (centos6), 1-999 (centos7)
Login user ID range: 500-60000 (centos6), 1000-60000 (centos7)
When users log in, they need to convert their login name to UID. The resolution method is to find the name resolution database (/etc/passwd) in the system
passwd database information such as:
[root@localhost ~]# head -2 /etc/passwd
root:x:0:0:root :/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
[root@localhost ~]#
3. Group category, group identification, group Name resolution library
1. Group category classification 1: Administrator group, ordinary user group (ordinary user group is divided into: system group and login group)
1.1. Group identifier: GroupID, GID; generally represented by 16bits binary ( Its range is: 0-65535);
Administrator group ID: 0;
Ordinary user group ID range: 1-65535
System user group ID range: 1-499 (centos6), 1-999 (centos7 )
Login user I group D range: 500-60000 (centos6), 1000-60000 (centos7)
When using the group, you also need to resolve the group name into a GID. The resolution method is to find the name resolution database in the system ( /etc/group)
group database such as:
[root@localhost ~]# head -2 /etc/group
root:x:0: //root is the group name, 0 is the group id
bin: x:1:
[root@localhost ~]#
2. Group category classification two: user’s main group, user’s additional group.
3. Group category classification three: User private group (the group name is the same as the user name and contains only one user), public group (the group contains multiple users)
4. Authentication information: Password authentication ( password)
By comparing the pre-stored information with the information provided when logging in.
User password storage location: /etc/shadow
[root@localhost ~]# head -n 2 /etc/shadow
root:$6$GeKChJmIDB8KmeX2$UwylvnZwolmF7XyddqC5yp3CPd6grCw.aBdsqm8O7a1q3pVOmcXQPSAl7b.E1 TVl.gtOEo2RtkxCiH3TGEsUy.::0:99999: 7:::
bin:*:16659:0:99999:7:::
[root@localhost ~]#
Group password storage location: /etc/gshadow
[root@localhost ~ ]# head -n 2 /etc/gshadow
root:::
bin:::
[root@localhost ~]#

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
