chmod 700 vs 755

Property chmod 700 chmod 755
Octal 700 755
Symbolic rwx------ rwxr-xr-x
Owner read/write/execute read/write/execute
Group no access read/execute
Others no access read/execute
Risk Level Restrictive Low Risk
Typical Use The ~/.ssh directory storing keys and host credentials Standard Linux directories and folder structures
Advertisement

Key Difference

Which Should You Use?

The choice between chmod 700 and chmod 755 represents the boundary between private administrative directories and publicly accessible folders. Mode 700 reserves all permissions (read, write, execute) exclusively for the owner, rendering the directory completely invisible and inaccessible to all other users and background services. This extreme restriction is essential for the ~/.ssh directory, private backup folders, and personal script repositories where unauthorized browsing must be blocked. On the other hand, chmod 755 allows group members and public users to enter (cd) the directory and inspect its file names, while reserving write access strictly for the owner. Mode 755 is the bedrock of public web roots, /usr/bin system folders, and documentation archives that must be universally readable.

Advertisement

Frequently Asked Questions

Is 700 more secure than 755?

Yes, 700 is significantly more secure because it hides the directory contents from all non-root users on the system, preventing unauthorized listing and entry.

Can I convert 700 to 755?

Yes. To open read and traverse access to group and world users, run "chmod 755 /path/to/dir" or "chmod go+rx /path/to/dir".

Which is better for web servers?

Mode 755 is required for public web directories so the web daemon can traverse folders. Mode 700 causes immediate 403 Forbidden errors if used on a web document root.

Related Permissions & Comparisons

Read in-depth breakdowns for chmod 700 (rwx------) and chmod 755 (rwxr-xr-x), or browse other permission comparisons:

Advertisement