Understanding SUID, SGID and Sticky Bit
SUID (Set-User-ID) Bit
Any binary file with SUID bit can be run by anyone as its user owner e.g., /usr/bin/passwd. It can be executed by anyone without sudo privilege to change their own password on a Linux system. The SUID bit can be set on any other file or directory and not restricted only to the executable binaries. But setting the SUID bit on a directory in a Linux system is not a common or recommended practice, and it typically doesn't serve a useful purpose in the same way it does for executable files. The SUID bit is mainly used for executable files to allow them to run with the privileges of the file owner rather than the user who executed the file. When applied to a directory, the SUID bit doesn't have the same meaning or functionality.
In a Linux system, the SUID bit is typically applied to executable files, not directories. The SUID bit on an executable file allows a user who runs the file to temporarily execute it with the permissions of the file's owner rather than their own. This can be useful in certain situations to grant users limited access to specific privileged actions without giving them full root access.
However, applying the SUID bit to a directory is not a common or recommended practice because directories don't execute code in the same way that executable files do. Directories primarily contain files and sub-directories, and they are used for organising and storing data.
If the SUID bit is set on a directory, it may not have any meaningful effect, as the operating system doesn't have a standard behaviour associated with it. Additionally, it could potentially create security risks or unexpected behaviour because it might affect how file operations are carried out within that directory.
In summary, setting the SUID bit on a directory is not a standard practice and is generally discouraged in Linux systems. If you have specific security or access control requirements for directories, it's typically better to use appropriate file permissions and ownership settings rather than relying on SUID. To scan all the files with SUID bit by using find command:
As shown in the output, /usr/bin/passwd is one of the binary files with SUID bit. Its permission looks like this.
It means that anyone on this Linux box can run passwd command as user owner root without sudo privilege escalation. In other word, you don't need to be root to execute this binary although root is the user and group owner of it. That's why you can run passwd command as non-root user or without sudo prefix.
Let's have a look at a binary file which doesn't have SUID bit on it. For example, you can't run parted command as non-root since its default permission is shown as below.
It is not quite usual to add SUID bit to a binary file like parted for everyone to run it as non-root user. But it can demonstrate the drastic affect by doing a strange thing like adding SUID bit to a system partition tool parted. To add SUID bit to the parted binary, you can use chmod command as below.
Now you can run parted as non-root user even though it complains about it as shown below.
SGID (Set-Group-ID) Bit
Any sub-files or sub-directories created inside a directory with SGID bit are owned by its group owner through inheritance although they are created by different user or group owner. It is an ideal situation to share a directory among team to collaborate for a group project. Only caveat is whoever has the access to write to the directory also can delete stuffs inside it although they don't own them or create them originally. Sometimes it is desired to let all users in a group to create and delete sub-files and sub-directories in a shared space for collaboration.
There are some binary files with SGID bit for some use cases like crontab. The crontab group has no members but it has a very unique usage. The binary file /usr/bin/crontab is owned by the crontab group with SGID bit set, and /var/spool/cron/crontabs directory's group owner is crontab with sticky bit T. When you check its directory, there is no file or directory exists as you can see below.
Now let's experiment creating a simple cron job as the user vagrant and verify if that makes any change in the /var/spool/cron/crontabs directory.
Upon checking its directory, you can see there is a new file called vagrant which is owned by the user owner vagrant and the group owner crontab with the permission of -rw-------. To scan all the files and directories with SGID by using find command:
To add SGID bit to a directory, you can again use chmod command as shown below.
Here is how it can be prepared to test how SGID bit works in terminal.
As you can see in the output, those newly created 'testfile' file and 'testdir' directory inherit the group owner 'dev' due to SGID bit set on /developers parent directory. It is quite clever to use the SGID bit for sharing a directory among team. But there is a downside with this permission since any other users of 'dev' group can remove or delete those file and directory created by 'testusr' account if that's not intended in the shared space. That's where the Sticky bit comes to save your bacon.
Sticky Bit
The sticky bit is a permission in Linux and Unix-like operating systems that can be set on directories to control who can delete or modify files within that directory. It has a specific and important role in shared directories, particularly in locations like /tmp, where multiple users may need to create and manipulate files.
When the sticky bit is set on a directory, it allows users to create files and directories within that directory, but they can only delete or modify their own files and directories. Users cannot delete or modify files or directories owned by other users, even if they have write permissions on the parent directory. Only the owner of a file or directory or the superuser (root) can delete or modify files within a directory with the sticky bit set.
The primary use cases for the sticky bit are:
Temporary Directories: The most common use of the sticky bit is on directories like
/tmp. By setting the sticky bit on/tmp, it ensures that any user can create temporary files and directories there, but they can only remove their own files, helping to prevent accidental or malicious deletion of other users' files.Shared Directories: In shared directories where multiple users have write access, the sticky bit can prevent one user from interfering with the files of others. For example, in a shared project directory, you may want to set the sticky bit to ensure that each user can manage their own files and subdirectories without impacting others.
To set the sticky bit on a directory, you can use the chmod command with the numeric mode or symbolic mode. For example, to set the sticky bit on a directory:
Or using numeric mode:
In the numeric mode, the number "1" in the thousands place represents the sticky bit. The "777" specifies the owner, group, and other permissions.
In summary, the sticky bit in Linux permissions is used on directories to restrict the deletion or modification of files and directories within that directory to their respective owners or the superuser. It helps maintain security and integrity in shared directories, especially temporary and public directories where multiple users have access.
When you only have SUID or SGID set, it displays rwS but rws when you have both SUID or SGID and executable(x) set for user or group. Likewise with Sticky bit, it displays rwT when you only set Sticky bit but rwt when you have both Sticky bit and executable(x) set for others.
Last updated
