Sudo (su “do”) allows a system administrator to delegate authority to give certain users (or groups of users) the ability to run some (or all) commands as root or another user while providing an audit trail of the commands and their arguments. Sudo operates on a per-command basis, it is not a replacement for the shell. Its features include: The ability to restrict the commands a user may run on a per-host basis.| About Sudo on Sudo
National Language Support, or NLS, means that a program’s informational, warning and error strings are stored in a message catalog which can be translated into the native language of the program’s users. Beginning with version 1.8.2, sudo supports NLS using the gettext family of functions. NLS Translations for sudo are coordinated through the Translation Project. If you would like to contribute a translation for sudo, please join a translation team at the Translation Project instead of co...| About Sudo on Sudo
Starting with version 1.8.0, sudo supports a modular framework that supports third-party policy and I/O logging plugins. In this framework, when a user runs sudo, the front-end queries a policy plugin to determine whether or not the command is to be allowed. If it is allowed, the policy plugin returns a description of how to run the command along with the argument vector and environment to pass to the execve() system call. While the command is being run, the I/O plugin, if any, is passed all ...| About Sudo on Sudo
Sudo Sandwich Logo The current sudo logo, © 2019 by Mark Stillman and licensed under CCBY 4.0. It was inspired by xkcd 149. Sudo Shield Logo The previous sudo logo, © 2010 by Trent Badger and licensed under CCBY 4.0.| About Sudo on Sudo
Use of encryption Prior to version 1.9.0, Sudo did not include support for encrypting data and was not subject to any export controls. However, starting with version 1.9.0, Sudo supports encrypted connections between the sudo_logsrvd daemon and the sudoers plugin. Specifically, TLS 1.2 or higher is used which supports strong encryption. The actual encryption algorithms used depend on the Sudo configuration as well as the version of OpenSSL or LibreSSL sudo is linked with (sudo does not includ...| Sudo
The Early Years Sudo was first conceived and implemented by Bob Coggeshall and Cliff Spencer around 1980 at the Department of Computer Science at SUNY/Buffalo. It ran on a VAX-11/750 running 4.1BSD. An updated version, credited to Phil Betchel, Cliff Spencer, Gretchen Phillips, John LoVerso, and Don Gworek, was posted to the net.sources Usenet newsgroup in December of 1985.| Sudo
The following list of people, sorted by last name, have contributed code or patches to this implementation of sudo since I began maintaining it in 1993. This list is known to be incomplete–if you believe you should be listed, send a note to sudo@sudo.ws. Ackeret, Matt Adler, Mark Allbery, Russ Anderson, Jamie Andrew, Nick Andric, Dimitry Barron, Danny Bates, Tom Behan, Zdeněk Bellis, Ray Benali, Elias Beverly, Jamie Boardman, Spider Bos, Sander Bostley, P.J. Bowes, Keith Boyce, Keith Garry...| Sudo
Sudo is distributed under the following license: Copyright (c) 1994-1996, 1998-2025 Todd C. Miller Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL T...| Sudo