Linux Chmod Permissions Explained: Symbolic vs Octal Notation (755, 644, 700)

Every file and folder on a Linux or POSIX system maintains permission flags for three distinct user scopes: 1. **User (Owner):** The specific user account that owns the file. 2. **Group:** The collective group assigned to the file. 3. **Others (Public):** All other users on the operating system. Each scope has three independent permission bits: - **Read (`r`):** Value **4** (Allows viewing file contents or listing directory contents) - **Write (`w`):** Value **2** (Allows modifying file contents or adding/deleting files in a folder) - **Execute (`x`):** Value **1** (Allows executing the file as a program or traversing into a directory)

When novice developers encounter permission denied errors (`EACCES`), an unfortunately common impulse is running `chmod -R 777 .`. Setting permissions to **777** (`rwxrwxrwx`) gives every untrusted process, guest user, or compromised daemon on your machine the power to overwrite executable binaries, inject malicious shell scripts, or delete production logs. ### Production Permission Standards: - **Web Root Files (HTML, JS, CSS, PHP):** `644` (`rw-r--r--`) - **Web Root Directories:** `755` (`rwxr-xr-x`) - **SSH Private Keys (`~/.ssh/id_rsa`):** `600` (`rw-------`) - **SSH Directory (`~/.ssh`):** `700` (`rwx------`)