Difference Between su and sudo and How to Configure sudo in Linux

Linux System is much secured than any of its counterpart. One of the way to implement security in Linux is the user management policy and user permission and normal users are not authorized to perform any system operations.

If a normal user needs to perform any system wide changes he needs to use either ‘su‘ or ‘sudo‘ command.

su vs sudo in Linux
Linux: su v/s sudo

NOTE – This article is more applicable to Ubuntu based distributions, but also applicable to most of the popular Linux distributions.

‘su’ Vs ‘sudo’

su‘ forces you to share your root password to other users whereas ‘sudo‘ makes it possible to execute system commands without root password. ‘sudo‘ lets you use your own password to execute system commands i.e., delegates system responsibility without root password.

What is ‘sudo’?

sudo‘ is a root binary setuid, which executes root commands on behalf of authorized users and the users need to enter their own password to execute system command followed by ‘sudo‘.

Who can execute ‘sudo’?

We can run ‘/usr/sbin/visudo‘ to add/remove the list of users who can execute ‘sudo‘.

$ sudo /usr/sbin/visudo

A screen shot of ‘/usr/sbin/visudo‘ file, looks something like this:


The sudo list looks like the below string, by default:

root ALL=(ALL) ALL

Note: You must be root to edit /usr/sbin/visudo file.

Granting sudo Access

In many situation, System Administrator, specially new to the field finds the string “root ALL=(ALL) ALL” as a template and grants unrestricted access to others which may be potentially very harmful.

Editing ‘/usr/sbin/visudo’ file to something like the below pattern may really be very dangerous, unless you believe all the listed users completely.

root ALL=(ALL) ALL
adam ALL=(ALL) ALL
mark ALL=(ALL) ALL

Parameters of sudo

A properly configured ‘sudo‘ is very flexible and number of commands that needs to be run may be precisely configured.

The Syntax of configured ‘sudo‘ line is:

User_name Machine_name=(Effective_user) command

The above Syntax can be divided into four parts:

  1. User_name: This is the name of ‘sudo‘ user.
  2. Machine_name: This is the host name, in which ‘sudo‘ command is valid. Useful when you have lots of host machines.
  3. (Effective_user): The ‘Effective user’ that are allowed to execute the commands. This column lets you allows users to execute System Commands.
  4. Command: command or a set of commands which user may run.

Suggested Read: 10 Useful Sudoers Configurations for Setting ‘sudo’ in Linux

Some of the Situations, and their corresponding ‘sudo‘ line:

Q1. You have a user mark which is a Database Administrator. You are supposed to provide him all the access on Database Server (beta.database_server.com) only, and not on any host.

For the above situation the ‘sudo‘ line can be written as:

mark beta.database_server.com=(ALL) ALL

Q2. You have a user ‘tom‘ which is supposed to execute system command as user other than root on the same Database Server, above Explained.

For the above situation the ‘sudo‘ line can be written as:

mark beta.database_server.com=(tom) ALL

Q3. You have a sudo user ‘cat‘ which is supposed to run command ‘dog‘ only.

To implement the above situation, we can write ‘sudo’ as:

mark beta.database_server.com=(cat) dog

Q4. What if the user needs to be granted several commands?

If the number of commands, user is supposed to run is under 10, we can place all the commands alongside, with white space in between them, as shown below:

mark beta.database_server.com=(cat) /usr/bin/command1 /usr/sbin/command2 /usr/sbin/command3 ...

If this list of command varies to the range, where it is literally not possible to type each command manually we need to use aliases. Aliases! Yeah the Linux utility where a long-lengthy command or a list of command can be referred as a small and easy keyword.

A few alias Examples, which can be used in place of entry in ‘sudo‘ configuration file.

User_Alias ADMINS=tom,jerry,adam
user_Alias WEBMASTER=henry,mark
Cmnd_Alias PROC=/bin/kill,/bin/killall, /usr/bin/top

It is possible to specify a System Groups, in place of users, that belongs to that group just suffixing ‘%’ as below:

%apacheadmin WEBSERVERS=(www) APACHE

Q5. How about executing a ‘sudo‘ command without entering password?

We can execute a ‘sudo‘ command without entering password by using ‘NOPASSWD‘ flag.


Here the user ‘adam‘ can execute all the commands aliased under “PROCS”, without entering password.

Suggested Read: Let Sudo Insult You When You Enter Incorrect Password

sudo” provides you a robust and safe environment with loads of flexibility as compared to ‘su‘. Moreover “sudo” configuration is easy. Some Linux distributions have “sudo” enabled by default while most of the distros of today needs you to enable it as a Security Measure.

To add an user (bob) to sudo just run the below command as root.

adduser bob sudo

That’s all for now. I’ll be here again with another Interesting article. Till then stay tuned and connected to Tecmint. Don’t forget to provide us with your valuable feedback in our comment section.

Hey TecMint readers,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE, RHCSA, LFCS, Learn Linux, and Awk, each worth $20!

Learn more about the contest and stand a chance to win by sharing your thoughts below!

A Passionate GNU/Linux Enthusiast and Software Developer with over a decade in the field of Linux and Open Source technologies.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.


Leave a Reply
  1. Hi,

    Really very nice tutorial, I would like to know if there is a way to exclude some admin to run any configuration in ssh?

  2. Hi Ravi,

    I am facing one problem with /etc/sudoers or visudo, Actually, While I am adding a user with adduser command and while I am not providing any sudo access but commands are working without password or without any permission error.

    I am using e.g: Lucky ALL=(Lucky) NOPASSWD: /bin/*, !/bin/rm.

    and also I am restricting for rm command but rm command is working.

    Please help me brother and please clarify my doubts.

  3. These comments are based on a multi user environment. In the case of shared computers of truly multi-user systems, sudo makes sense. However for single user systems and administrator use, su makes more sense for a variety of reasons including convenience and environment configuration.

    I do understand the confusion in this regard, especially with younger users, as Ubuntu started this confusion by misusing sudo to give it a more Windows like admin configuration model for individual admin tasks as it utterly lacks any unified administration interface where you’d give the root password once to enter and configure the system.

    So for example, as an administrator of my system, I keep a terminal shell open in which I’ve su’d to root and use that shell for all admin tasks.

    If I wanted to allow other users of the system to have access to network configuration or printer setup, I’d use sudo to allow access to those tools.

  4. Hi Ravi Saive,

    Good evening.

    I have a doubt in the below line.
    mark beta.database_server.com=(tom) ALL

    My understanding is ‘mark’ and ‘tom’ both are the sudo users, both users have same (ALL commands )access on beta.database_server.com machine.

    Is this correct? or any difference is there in between ‘mark’ and ‘tom’ users in terms of privileges on beta.database_server.com machine?

    Thanks in advance.


  5. Could you please explain more about Q2, i didn’t quite catch that. As per to the question, user tom which is supposed to execute system command as user other than root on the same database server.

    mark beta.database_server.com=(tom) ALL

    Mark — Sudo User
    beta.database_server.com — machine name
    tom — effective user
    ALL — Any command can be executed

    After login with Mark user, try executing commands it says permission denied. Would you please provide more clarification

    • @Roger,
      That’s not possible, either add aliases to sudo user .bash_profile file, or for global use add in /etc/profile file.

    • @Mushthaq,
      That’s not possible, because both are different users with different home directories, you must enter password to login to user account..

      • What if the password is not set for neither of the users? It still prompting for password and what we have to give?

  6. I agree with Tomas,

    su means Substitute User. So we can use su to switch user temporarily. In this way we can switch to root user. The sudo one gives temporarily root privileges, using the normal user password.

    I really do not understand this article :(.

  7. What a misleading article name that is.

    You use “sudo” when you need to execute a command as a superuser. You use “su” when you want to switch to another user’s account, or, execute a command AS another user, not necessarily a superuser.

    Saying that “su forces you to share your root password to other users whereas sudo makes it possible to execute system commands without root password” shows you having no idea what the real purpose (and the difference) is.

    • 1. I read as far as the second mention of “editing the /usr/sbin/visudo file” .. The file you are editing is in fact /etc/sudoers. /usr/sbin/visudo is the binary you are running.

      2. As has been pointed out, su is mainly used to switch to another user’s shell. sudo is mainly there for scripts, but it also allows you to centralize configuration and as you describe, no additional password requirements.
      You can do with sudo exactly the same as you would with su ([sudo -u $newuser -i] for example is the same as [su – $newuser] – although you have to be weary of some environment variables).

      3. sudo may or may not be SUID (as SELinux becomes more popular, the settings are actually going in there rather than SUID).

      4. “Parameters of sudo” looks like it should actually be “Syntax of sudoers file” or “Syntax of sudo config”… Parameters are what you pass on the command line.

      5. adduser instead of useradd? You must really only know specific linux’s as useradd is the traditional Unix command (and adduser is actually a symbolic link to the correct useradd command… no idea why)

      6. It doesn’t look like you’ve stated you always need to use the full path name to the binary in the config file (dog will not do – it has to be /path/to/dog).

      7. “Linux System is much secured than any of its counterpart.” – I’m pretty sure several BSD fanatics will disagree with you there. BSD (kernel) is built with security more in mind – Linux (kernel) is built with more compromises and different ideals.

  8. One comment about the article, you dont need root password to use su

    su default is root but not only that

    if I want to change my user id to become user test I run

    su test

    and I need test user password not root password

    Best regards

    Rodrigo Gonzalez

  9. Dear Sir,

    I have a query. It’s not related to this post.

    How to assign hard quota to limited user in centos/Ubuntu ?

    Kindly let us know about this.

    Manoj Gupta

  10. If a newbie ask me what different between su and sudo, i simply answer that su require root password where sudo require your cyrrent password. :D

    • Dear Quovadis,
      we prepare our post after several hours of study, research, test before making it available to you. Our post is for Newbies as well as advanced users. Actually we write our contents from every possible user perspective.

      Keep connected to Tecmint for such detailed posts.

  11. Hello Sir,

    Thanks for this article, because i thought that both are same but this article clear me différence between both.



    • Dear Manoj,
      It was very pleasing to know our posts helped you.

      Keep connected to Tecmint for more such posts.
      Refer to your friends and colleagues.


Got Something to Say? Join the Discussion...

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.