How to Manage File Permissions in Kali Linux? The Complete Guide

Key takeaways

• Read permissions as three triplets for owner, group and others; chmod 640 gives the owner read-write, the group read and others nothing.
• Avoid chmod 777 as a quick fix, and use the recursive flag on directories only after checking the path twice.
• Learn SUID, SGID and the sticky bit, plus umask, to understand why new files get default permissions and why SUID files matter.

File permissions decide who can read, change or run each file. On Kali, where you often handle wordlists, scripts and captured data, getting them right protects your work and your system. This guide covers reading permissions, changing them, the special bits most tutorials skip, and the mistakes that cause real problems.

What file permissions mean in Linux

Every file and directory has permissions for three classes of user: the owner, the group, and others (everyone else). Each class can have three permissions:

• Read (r): view a file's contents, or list a directory.
• Write (w): change a file, or add and remove files in a directory.
• Execute (x): run a file as a program, or enter a directory (cd into it).

Execute means different things for files and directories, and this trips up beginners. A directory needs execute permission before you can open anything inside it, even files you can otherwise read.

How do I view file permissions in Kali Linux?

Use ls -l. Each line starts with a ten-character string that encodes the type and permissions.

ls -l
-rwxr-xr-- 1 user group 1024 Jan 17 10:00 example.sh

Read -rwxr-xr-- in four parts:

To see a directory's own permissions rather than its contents, add -d: ls -ld /path.

How to change permissions with chmod

You can set permissions two ways: symbolic (letters) or numeric (digits). Both do the same job; pick whichever is clearer for the task.

Symbolic mode

Symbolic mode changes one part at a time, which is good for small tweaks. The form is chmod [who][operator][permission] file.

# Add execute for the owner
chmod u+x example.sh
# Remove write for others
chmod o-w example.sh
# Set group to exactly read and execute
chmod g=rx example.sh

Numeric (octal) mode

Numeric mode sets all three classes at once. Add the values for each class: read 4, write 2, execute 1.

# rwx r-x r-- (owner all, group read+execute, others read)
chmod 754 example.sh
# rw- r----- (owner read+write, group read, others nothing): a private config
chmod 640 config.env

Changing ownership with chown and chgrp

Permissions decide what each class may do; ownership decides who the owner and group are. Changing ownership usually needs sudo.

# Change the owner
sudo chown john example.sh
# Change owner and group together
sudo chown john:developers example.sh
# Change only the group
sudo chgrp developers example.sh

Applying changes to a whole directory

The -R option applies a change to a directory and everything inside it. Use it carefully: a recursive chmod on the wrong path can break a system.

sudo chown -R john:developers /srv/project

Do not apply a single file mode recursively to a mixed tree. chmod -R 777 is the classic mistake: it makes everything world-writable and also strips the execute bit logic that directories need. If you must set directories and files differently, target them separately:

# Directories need execute to be enterable; files usually do not
find /srv/project -type d -exec chmod 755 {} \;
find /srv/project -type f -exec chmod 644 {} \;

The special bits most guides skip: SUID, SGID and the sticky bit

Beyond rwx, three special bits matter for security, and they appear often in Kali work.

In an ls -l listing these appear as s or t in place of an x. Auditing a system for unexpected SUID binaries is a standard security check, which is why this matters more on Kali than on an ordinary desktop. You can list them with find / -perm -4000 -type f 2>/dev/null.

Why new files get the permissions they do: umask

New files do not appear with random permissions. The umask value subtracts permissions from a default (666 for files, 777 for directories). A typical umask of 022 gives new files 644 and new directories 755. Check yours with umask, and set a stricter 077 if you want new files readable only by you.

Common mistakes and how to fix them

Good habits for permissions on Kali

1. Least privilege: give the smallest access that works, and widen only if something genuinely needs it.
2. Protect secrets: keys, tokens and config files with credentials should be 600 (owner read/write only).
3. Do not live as root: modern Kali uses a normal user by default. Keep it that way and use sudo.
4. Audit regularly: check for world-writable files and unexpected SUID binaries as part of routine hardening.

Permissions are one layer. For the bigger picture, see our guides on managing users and permissions for secure access control and securing a Linux server. To understand where files actually live, read the Kali Linux file system hierarchy.

Next step

Create a test file, change its permissions in both symbolic and numeric mode, and confirm each change with ls -l until the ten-character string reads instantly to you. That fluency is what you will rely on in every later Kali task. If you are still finding your way around the system, start with our guide to learning Kali Linux for beginners.

Related reading

• Linux File Permissions Explained for Beginners | Understanding rwx, chmod, 777, and Octal Binary Modes with Practical Examples
• How to Use Shell Scripting in Kali Linux for Automation? The Complete Guide
• How to Manage Users and Groups in Kali Linux? Best Practices for Security Professionals