Linux Permissions Explained: A Beginner’s Guide to File Security Commands

Steven P. Sanderson II, MPH

10 hours ago

[This article was first published on Steve's Data Tips and Tricks, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)

Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

< section id="introduction" class="level1">

Introduction

Understanding Linux permissions is crucial for anyone working with Linux systems. Whether you’re a new system administrator, developer, or Linux enthusiast, mastering file permissions is essential for maintaining system security and proper file access control.

< section id="understanding-basic-permission-concepts" class="level1">

Understanding Basic Permission Concepts

< section id="user-group-and-others" class="level2">

User, Group, and Others

Linux implements a hierarchical permission system with three levels of access:

User (u): The file’s owner
Group (g): Members of the file’s assigned group
Others (o): Everyone else on the system

< section id="read-write-and-execute-permissions" class="level2">

Read, Write, and Execute Permissions

Each permission level has three basic rights:

Read (r): Value of 4
Write (w): Value of 2
Execute (x): Value of 1

# Example file permissions display
-rwxr-xr-- 1 user group 4096 Nov 1 2024 example.txt

< section id="numeric-permission-notation" class="level2">

Numeric Permission Notation

Permissions can be represented numerically:

7 (rwx) = 4 + 2 + 1
6 (rw-) = 4 + 2
5 (r-x) = 4 + 1
4 (r–) = 4

< section id="essential-permission-commands" class="level1">

Essential Permission Commands

< section id="the-chmod-command" class="level2">

The chmod Command

# Symbolic mode
chmod u+x script.sh    # Add execute permission for user
chmod g-w file.txt     # Remove write permission for group
chmod o=r document.pdf # Set others to read-only

# Numeric mode
chmod 755 script.sh    # rwxr-xr-x
chmod 644 file.txt     # rw-r--r--

< section id="understanding-umask" class="level2">

Understanding umask

The umask command sets default permissions for new files and directories:

# Check current umask
umask

# Set new umask
umask 022  # Results in 755 for directories, 644 for files

< section id="working-with-su-and-sudo" class="level2">

Working with su and sudo

# Switch to root user
su -

# Execute single command as root
sudo apt update

# Edit system file with sudo
sudo nano /etc/hosts

< section id="managing-ownership-with-chown" class="level2">

Managing Ownership with chown

# Change owner
chown user1 file.txt

# Change owner and group
chown user1:group1 file.txt

# Recursive ownership change
chown -R user1:group1 directory/

< section id="your-turn-practical-exercise" class="level1">

Your Turn! Practical Exercise

Try this hands-on exercise:

Problem: Create a script that needs to be executable by the owner only, readable by the group, and inaccessible to others.

Create a new file:

touch script.sh

Your task: Set the appropriate permissions using chmod.

Solution:

# Create the file
touch script.sh

# Set permissions (owner: rwx, group: r--, others: ---)
chmod 740 script.sh

# Verify permissions
ls -l script.sh

< section id="quick-takeaways" class="level1">

Quick Takeaways

Permissions are divided into user, group, and others
Basic permissions are read (4), write (2), and execute (1)
chmod modifies permissions
umask sets default permissions
su and sudo provide elevated privileges
chown changes file ownership

< section id="common-permission-scenarios" class="level1">

Common Permission Scenarios

< section id="web-server-permissions" class="level2">

Web Server Permissions

# Standard web directory permissions
chmod 755 /var/www/html
chmod 644 /var/www/html/*.html

< section id="shared-directories" class="level2">

Shared Directories

# Create a shared directory
mkdir /shared
chmod 775 /shared
chown :developers /shared

< section id="troubleshooting" class="level1">

Troubleshooting

< section id="common-permission-issues" class="level2">

Common Permission Issues

Permission Denied

# Check file permissions
ls -l problematic_file
# Check current user and groups
id

Cannot Execute Script

# Make script executable
chmod +x script.sh

< section id="faqs" class="level1">

FAQs

Q: Why can’t I modify a file even as the owner? A: Check if the file has write permissions for the owner using ls -l. Use chmod u+w filename to add write permissions.
Q: What’s the difference between su and sudo? A: ‘su’ switches to another user account completely, while ‘sudo’ executes single commands with elevated privileges.
Q: How do I recursively change permissions? A: Use chmod with the -R flag: chmod -R 755 directory/
Q: What’s the safest permission for configuration files? A: Usually 644 (rw-r–r–) or 640 (rw-r—–) depending on security requirements.
Q: How do I check my current user and group memberships? A: Use the id command to display all user and group information.

< section id="references" class="level1">

References

< section id="conclusion" class="level1">

Conclusion

Understanding Linux permissions is fundamental to system security and proper file management. Practice these commands regularly, and always consider security implications when modifying permissions.

< section id="try-this-exercise-then-share-your-experience" class="level2">

Try this Exercise! Then, Share Your Experience

Start by auditing your important files’ permissions using ls -l. Create a test directory to practice these commands safely. Share your experience or questions in the comments below!

Happy Coding! 🚀