Why permissions protect system security in Linux CLI - Quick Recap

Recall & Review

beginner

What is the main purpose of file permissions in Linux?

File permissions control who can read, write, or execute a file, protecting the system from unauthorized access or changes.

beginner

What do the letters 'r', 'w', and 'x' stand for in Linux permissions?

'r' means read permission, 'w' means write permission, and 'x' means execute permission.

beginner

How do permissions help protect system security?

Permissions limit access to files and commands, so only trusted users can change or run important system files, preventing accidental or malicious damage.

beginner

What happens if a file has no execute permission?

Users cannot run the file as a program or script, which helps prevent unauthorized code from running.

intermediate

Why should system files have strict permissions?

Strict permissions prevent unauthorized users from changing or deleting important files, keeping the system stable and secure.

Which permission allows a user to change the contents of a file?

A Write

B Read

C Execute

D Delete

Write permission lets a user modify or change a file's contents.

What does execute permission allow a user to do?

A Change file ownership

B Read the file

C Delete the file

D Run the file as a program

Execute permission lets a user run a file as a program or script.

Why is it important to restrict permissions on system files?

A To allow everyone to edit them

B To prevent unauthorized changes that could harm the system

C To make files invisible

D To speed up the system

Restricting permissions protects system files from unauthorized changes that could cause problems.

If a user has only read permission on a file, what can they do?

A View the file contents

B Run the file as a program

C Delete the file

D Modify the file

Read permission allows viewing the file contents but not changing or running it.

What is the risk of giving write permission to everyone on a system file?

A No risk at all

B Files become read-only

C Users can accidentally or intentionally change or delete important files

D Files will run faster

Write permission for everyone can lead to accidental or malicious damage to important files.

Explain how Linux file permissions help protect system security.

Think about what each permission allows and why limiting them matters.

Describe what could happen if system files had no permission restrictions.

Consider the risks of everyone having full access.

Practice

1. Why are file permissions important for system security in Linux?

easy

A. They delete unused files to save disk space.

B. They speed up the computer's processing power.

C. They automatically update software to the latest version.

D. They control who can read, write, or execute files, preventing unauthorized access.

Solution

1. Step 1: Understand the role of permissions

   Permissions decide who can read, write, or run files, which controls access.

2. Step 2: Connect permissions to security

   By limiting access, permissions stop unauthorized users from changing or viewing files.

3. Final Answer:

   They control who can read, write, or execute files, preventing unauthorized access. -> Option D

4. Quick Check:

   Permissions protect access = A [OK]

Hint: Permissions limit file access to protect security [OK]

Common Mistakes:

• Thinking permissions speed up the computer
• Believing permissions update software
• Assuming permissions delete files automatically

2. Which command correctly changes a file's permissions to allow the owner to read and write, but no permissions for others?

easy

A. chmod 600 filename

B. chmod 777 filename

C. chmod 644 filename

D. chmod 755 filename

Solution

1. Step 1: Understand chmod numeric codes

   600 means owner can read/write (6), group and others have no permissions (0).

2. Step 2: Match permissions to requirement

   Only chmod 600 filename sets owner read/write and no permissions for others.

3. Final Answer:

   chmod 600 filename -> Option A

4. Quick Check:

   600 = owner rw, others none [OK]

Hint: 600 means owner rw, others none [OK]

Common Mistakes:

• Choosing 777 which gives all permissions to everyone
• Confusing 644 with no permissions for others
• Using 755 which allows execute permission

3. What will be the output of the command ls -l secret.txt if the file has permissions -rw------- and you are logged in as a different user?

medium

A. You will get a 'Permission denied' error when trying to read the file.

B. You will see the file details but cannot read the file.

C. You will see the file details and can read the file.

D. The file will not appear in the directory listing.

Solution

1. Step 1: Analyze file permissions

   -rw------- means only owner has read/write, others have no permissions.

2. Step 2: Understand ls -l behavior

   ls -l displays file metadata (permissions, owner, size) without needing read permission on the file; assumes directory allows access.

3. Final Answer:

   You will see the file details but cannot read the file. -> Option B

4. Quick Check:

   ls -l shows details, read denied [OK]

Hint: ls -l shows details despite no read permission [OK]

Common Mistakes:

• Thinking file won't show in listing
• Assuming read access is allowed
• Confusing file details visibility with read permission

4. You run chmod 755 myscript.sh but the script still cannot be executed by others. What is the most likely problem?

medium

A. The file is owned by root and others have no execute permission.

B. The script has syntax errors stopping execution.

C. The file system is mounted with 'noexec' option preventing execution.

D. The user forgot to save the file after editing.

Solution

1. Step 1: Check permissions set by chmod

   chmod 755 sets execute permission for owner, group, and others.

2. Step 2: Consider other causes for execution failure

   If permissions are correct but execution fails, 'noexec' mount option may block running scripts.

3. Final Answer:

   The file system is mounted with 'noexec' option preventing execution. -> Option C

4. Quick Check:

   Permissions okay but noexec blocks execution [OK]

Hint: Check mount options if permissions allow but execution fails [OK]

Common Mistakes:

• Assuming ownership blocks execution with 755 permissions
• Blaming script syntax for permission errors
• Forgetting about file system mount options

5. You want to secure a directory so only the owner can list and access files inside, but others can still enter the directory without seeing contents. Which permission setting achieves this?

hard

A. chmod 711 directory

B. chmod 777 directory

C. chmod 755 directory

D. chmod 700 directory

Solution

1. Step 1: Understand directory permissions

   Read (r) allows listing contents, execute (x) allows entering the directory.

2. Step 2: Match permissions to requirement

   711 means owner has rwx, others have execute only (can enter but not list files).

3. Final Answer:

   chmod 711 directory -> Option A

4. Quick Check:

   Execute only for others = enter but no list [OK]

Hint: Execute without read lets others enter but not list [OK]

Common Mistakes:

• Using 700 which blocks others from entering
• Using 755 which allows others to list files
• Using 777 which gives full access to everyone