Open Access Articles- Top Results for Superuser


In computing, the superuser is a special user account used for system administration. Depending on the operating system (OS), the actual name of this account might be: root, administrator, admin or supervisor. In some cases the actual name is not significant but is an attribute of the user, and on Unix-like systems the user with an UID of zero is the superuser, regardless on the name of that account.[1]

In OSes which have the concept of a superuser, it is generally recommended that most application work be done using an ordinary account which does not have the ability to make system-wide changes.

Unix and Unix-like

In Unix-like computer OSes, root is the conventional name of the user who has all rights or permissions (to all files and programs) in all modes (single- or multi-user). Alternative names include baron in BeOS and avatar on some Unix variants.[2] BSD often provides a toor ("root" written backward) account in addition to a root account.[3] Regardless of the name, the superuser always has a user ID of 0. The root user can do many things an ordinary user cannot, such as changing the ownership of files and binding to network ports numbered below 1024.

The name "root" may have originated because root is the only user account with permission to modify the root directory of a Unix system. This directory was originally considered to be root's home directory,[4] but the Linux Filesystem Hierarchy Standard now recommends that root's home be at /root.[5] The first process bootstrapped in a Unix-like system, usually called init, runs with root privileges. It spawns all other processes directly or indirectly, which inherit their parents' privileges. Only a process running as root is allowed to change its user ID to that of another user; once it's done so, there is no way back. Doing so is sometimes called dropping root privileges and is often done as a security measure to limit the damage from possible contamination of the process. Another case is login and other programs that ask users for credentials and in case of successful authentication allow them to run programs with privileges of their accounts.

It often recommended that no-one use root as their normal user account,[6][7] since simple typographical errors in entering commands can cause major damage to the system. Instead, a normal user account should be used, and then either the su or sudo commands used. The su approach requires the user to know the root password, while the sudo method requires that the user has been setup with the power to run "as root" within the /etc/sudoers file, typically indirectly by being made a member of the wheel,[8] admin, or sudo group. For a number of reasons, the sudo approach is now generally preferred - for example it leaves an audit trail of who has used the command and what administrative operations they performed.[9]

Some OSes, such as OS X and some Linux distributions (most notably Ubuntu[6]), automatically give the initial user created the ability to run as root via sudo - but configure this to ask them for their password before doing administrative actions. In some cases the actual root account is disabled by default, so can't be directly used.[6] In mobile platform-oriented OSs such as Apple iOS and Android, the device's security systems must be exploited in order to obtain superuser access. In a few systems, such as Plan 9, there is no superuser at all.

Setting the default root password is done via:[10]

sudo passwd root

Microsoft Windows

In Windows NT and later systems derived from it (such as Windows 2000, Windows XP, Windows Server 2003, and Windows Vista/7/8), there must be at least one administrator account (Windows XP and earlier) or one able to elevate privileges to superuser (Windows Vista/7/8 via User Account Control).[11] In Windows XP and earlier systems, there is a built-in administrator account that remains hidden when a user administrator-equivalent account exists.[12] This built-in administrator account is created with a blank password.[12] This poses security risks, so the built-in administrator account is disabled by default in Windows Vista and later systems due to the introduction of User Account Control (UAC).[12]

A Windows administrator account is not an exact analogue of the Unix root account - some privileges are assigned to the "Local System account". The purpose of the administrator account is to allow making system-wide changes to the computer (with the exception of privileges limited to Local System).[11]

The built-in administrator account and a user administrator account have the same level of privileges. The default user account created in Windows systems is an administrator account. Unlike OS X, Linux, and Windows Vista/7/8 administrator accounts, administrator accounts in Windows systems without UAC do not insulate the system from most of the pitfalls of full root access. One of these pitfalls includes decreased resilience to malware infections.

In Windows Vista/7/8 administrator accounts, a prompt will appear to authenticate running a process with elevated privileges. Usually, no user credentials are required to authenticate the UAC prompt in administrator accounts but authenticating the UAC prompt requires entering the username and password of an administrator in standard user accounts. In Windows XP (and earlier systems) administrator accounts, authentication is not required to run a process with elevated privileges and this poses another security risk that lead to the development of UAC. Users can set a process to run with elevated privileges from standard accounts by setting the process to "run as administrator" or using the "runas" command and authenticating the prompt with credentials (username and password) of an administrator account. Much of the benefit of authenticating from a standard account is negated if the administrator account's credentials being used has a blank password (as in the built-in administrator account in Windows XP and earlier systems).

In Windows NT, 2000 and higher, the root user is the LocalSystem builtin service account (SYSTEM). This user account runs all system processes. Currently, only 3rd party methods exist to run programs as the SYSTEM user.[13]

Novell NetWare

In Novell NetWare, the superuser was called "supervisor", later "admin".


In OpenVMS, "SYSTEM" is the superuser account for the OS.

Network operations

Most configuration, testing and maintenance of networked systems has the potential to adversely affect multiple systems. In an effort to prevent inexperienced and disruptive individuals from causing problems, OS network utilities often require superuser authority. For example stress testing, if done at inappropriate times or without clear understanding of the effects, can deny users access to portions or all of the services of multiple computers. This is more of a problem than the original implementers of some utilities envisioned since it is now common for novices to build systems they own and have the ability to use the superuser account.

Older personal systems

Many older OSes on computers intended for personal and home use, including MS-DOS and Windows 95, do not have the concept of multiple accounts and thus have no separate administrative account; anyone using the system has full privileges. The lack of this separation in these OSes has been cited as one major source of their insecurity.[14]

Regular user

Non superusers are usually called regular users. [15][16]

See also


External links