sudo (/suːduː/[4]) is a program for Unix-like computer operating systems that enables users to run programs with the security privileges of another user, by default the superuser.[5] It originally stood for "superuser do",[6] as that was all it did, and this remains its most common usage;[7] however, the official Sudo project page lists it as "su 'do'".[8] The current Linux manual pages for su define it as "substitute user",[9] making the correct meaning of sudo "substitute user, do", because sudo can run a command as other users as well.[10][11]
Unlike the similar command su, users must, by default, supply their own password for authentication, rather than the password of the target user. After authentication, and if the configuration file (typically /etc/sudoers) permits the user access, the system invokes the requested command. The configuration file offers detailed access permissions, including enabling commands only from the invoking terminal; requiring a password per user or group; requiring re-entry of a password every time or never requiring a password at all for a particular command line. It can also be configured to permit passing arguments or multiple commands.
History
Robert Coggeshall and Cliff Spencer wrote the original subsystem around 1980 at the Department of Computer Science at SUNY/Buffalo.[12] Robert Coggeshall brought sudo with him to the University of Colorado Boulder. Between 1986 and 1993, the code and features were substantially modified by the IT staff of the University of Colorado Boulder Computer Science Department and the College of Engineering and Applied Science, including Todd C. Miller.[12] The current version has been publicly maintained by OpenBSD developer Todd C. Miller since 1994,[12] and has been distributed under an ISC-style license since 1999.[12]
In November 2009 Thomas Claburn, in response to concerns that Microsoft had patented sudo,[13] characterized such suspicions as overblown.[14] The claims were narrowly framed to a particular GUI, rather than to the sudo concept.[15]
Unlike the command su, users supply their personal password to sudo (if necessary)[18] rather than that of the superuser or other account. This allows authorized users to exercise altered privileges without compromising the secrecy of the other account's password.[19] Users must be in a certain group to use the sudo command, typically either the wheel group or the sudo group.[20] After authentication, and if the configuration file permits the user access, the system invokes the requested command. sudo retains the user's invocation rights through a grace period (typically 5 minutes) per pseudo terminal, allowing the user to execute several successive commands as the requested user without having to provide a password again.[21]
As a security and auditing feature, sudo may be configured to log each command run. When a user attempts to invoke sudo without being listed in the configuration file, an exception indication is presented to the user indicating that the attempt has been recorded. If configured, the root user will be alerted via mail. By default, an entry is recorded in the system.[22]
Configuration
The /etc/sudoers file contains a list of users or user groups with permission to execute a subset of commands while having the privileges of the root user or another specified user. The file is recommended[by whom?] to be edited by using the command sudo visudo. Sudo contains several configuration options such as allowing commands to be run as sudo without a password, changing which users can use sudo, and changing the message displayed upon entering an incorrect password.[23] Sudo features an easter egg that can be enabled from the configuration file that will display an insult every time an incorrect password is entered.[24]
Impact
In some system distributions, sudo has largely supplanted the default use of a distinct superuser login for administrative tasks, most notably in some Linux distributions as well as Apple's macOS.[25][26] This allows for more secure logging of admin commands and prevents some exploits.
visudo is a command-line utility that allows editing the sudo configuration file in a fail-safe manner. It prevents multiple simultaneous edits with locks and performs sanity and syntax checks.
Sudoedit is a program that symlinks to the sudo binary.[28] When sudo is run via its sudoedit alias, sudo behaves as if the -e flag has been passed and allows users to edit files that require additional privileges to write to.[29]
Microsoft released its own version of sudo for Windows in February 2024. It functions similar to its Unix counterpart by giving the ability to run elevated commands from an unelevated console session.[30] The program runas provides comparable functionality in Windows, but it cannot pass current directories, environment variables or long command lines to the child. And while it supports running the child as another user, it does not support simple elevation. Hamilton C shell also includes true su and sudo for Windows that can pass all of that state information and start the child either elevated or as another user (or both).[31][32]
doas, available since OpenBSD 5.8 (October 2015), has been written in order to replace sudo in the OpenBSD base system, with the latter still being made available as a port.[36]
gosu is a tool similar to sudo that is popular in containers where the terminal may not be fully functional or where there are undesirable effects from running sudo in a containerized environment.[37]
^"About Unix sudo and su commands". University Information Technology Services. June 18, 2019. Archived from the original on September 10, 2022. Retrieved September 10, 2022.
