Should the root account be disabled in Fedora 18?

In Linux and other UNIX-like computer operating systems, the root account is the administrator account. A user with root privileges can perform many tasks that a standard user account cannot. In current editions of Fedora 17, the idea of a disabled root account is a foreign one.

But come Fedora 18, the next stable release, the root account will be disabled by default. It is one of the many new features of Anaconda, the Fedora system installation program. That at least is what you see in the just released Fedora 18 Alpha.

In this screen shot, which from the main interface of Anaconda, you can see below the ROOT PASSWORD button, though not readily legible, a 4-word phrase that says, root account is disabled.
Fedora 18 Root Account

Clicking on the root account button in the previous image automatically enables it, provided you specify the password.
Fedora 18 Root Passwd

With the root account disabled, the user created during the installation process is assigned to the Administrators group by default. This, of course, gives this user all admin privileges.
Fedora 18 User Account

For visitors looking to get a site online this web hosting review site provides reviews of cheap, reliable hosting companies all of which operate in a Linux environment.

The thing that I do not understand is, why is it even necessary to disable the root account? Is there any disadvantage to having a system with the traditional root account enabled? I cannot think of any reasonable one, can you?

Related Posts

Install ROSA Launcher on Fedora 18 KDE SimpleWelcome is the default menu on ROSA Linux KDE. Like the Takeoff Launcher, it is a fullscreen menu, but with a few more features. This articl...
How to use fedora-tools image for Fedora Atomic Host Fedora Atomic Host is a container-native version of the Fedora distribution. It is one of several operating systems expressly designed for running con...
Fedora 23 Cinnamon: Screenshots Fedora 23, the latest edition of the Fedora Linux distribution, was released earlier today. It is the first edition of Fedora that features a Cinna...
How to improve the Fedora experience This article is a take on how to "Improving the Fedora boot experience," which was the subject of an email by Matthias Clasen to a Red Hat developer's...
How to custmize KDE’s window titlebar buttons If you are using the latest KDE edition of your favorite distribution, your window titlebar could be missing a button or two that you most certainly n...
Building a Fedora-Based VoIP Server There are not a whole lot of active Linux or BSD-based Telephony/IP-PBX distros, but the few we have are quite good and easy to setup and configure. O...

We Recommend These Vendors

Launch an SSD VPS in Europe, USA, Asia & Australia on Vultr's KVM-based Cloud platform starting at $5:00/month (15 GB SSD, 768 MB of RAM).

Deploy an SSD Cloud server in 55 seconds on DigitalOcean. Built for developers and starting at $5:00/month (20 GB SSD, 512 MB of RAM).


  1. Disabling root is just more security through obscurity. It doesn’t really make the system more secure — in fact by encouraging the proliferation of superuser accounts (via sudo) I would argue it makes the system marginally less secure. It’s an idea that sounds good at first but actually turns out to be one more complication in an already overly complex system. The real answer is better audit logging and, most importantly, changing the root password periodically (maybe even without advance warning). It is much more practical (and efficient) to keep track of password expiration and usage of one superuser account (root) across 100’s of machines machines than 20 or 30 on the same number, which is actually on the low side for the number of sysadmins who might need root privileges in many enterprise shops.

Leave a Comment

Your email address will not be published. Required fields are marked *