su vs sudo: Which Linux Privilege Command Should You Use?

1. su command

The su (switch user) command changes the current user to another account, typically requiring the root password. After entering the password, the user gains the target account’s privileges, for example: su When the password is entered, the session switches to the root user with full root privileges.

2. sudo command

The sudo command runs a specific command with superuser (root) privileges. Unlike su , it allows a regular user to execute privileged operations using their own password, without knowing the root password. The command is prefixed with sudo: sudo apt-get update After entering the user’s password, the command runs with elevated rights.

3. Comparison

3.1 User identity

su requires the root password and switches the entire session to another user. sudo lets a normal user perform privileged actions using their own password.

3.2 Permission scope

su grants all permissions of the target user. sudo can be limited via the sudoers file to allow only specific commands or users.

3.3 Security

Because su shares the root password, it poses a security risk if the password is disclosed. sudo avoids sharing the root password, enhancing system security.

3.4 Logging

sudo records each privileged command, including the command executed and the invoking user, aiding audit and traceability. su has no built‑in logging.

3.5 Usage method

To use su , type the command and then the target user’s password. To use sudo , prepend sudo to the desired command and enter your own password for confirmation.

4. Use cases

Use su when you need a prolonged session as another user, such as working extensively in that user’s environment. Use sudo for temporary privileged tasks like installing software, updating the system, or performing critical maintenance.

5. Conclusion

Both su and sudo are essential Linux commands for switching users and executing privileged operations. su requires the root password, while sudo allows regular users to act with elevated rights using their own password, avoiding password sharing, providing detailed logs, and improving overall security. Choose the command that best fits your security requirements and workflow.