You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

First of all, you cannot create more than one root user. The closest you can get, probably, is to let one user use sudo to accomplish the tasks which need superuser privileges. In this matter it's wise to only grant superuser privileges to the commands you'll be needing -- not to everything. What use would it be if you disabled your root account and then created another one? The point in disabling the root account is that all the other accounts are non-privileged to do most of the things root can do. Then, with sudo, certain users can be given the chance to, by giving their password when starting sudo, run some things as root (but not everything, since that would compromise the whole idea).

List the things you need to do, grant some user sudo rights for them, disable root account and keep a hard eye on your logs. And do NOT let anyone use sudo without passwords. More importantly, don't let anybody use sudo if it's really not needed. The less root privileges, the less trouble.

What use would it be if you disabled your root account and then created another one?

The main reason is to block bruteforce attacks using root as the username. I'd want to keep a difficult username and an difficult password and yes I would keep an eye on all root logins. However, we have a company firewall which only allows SSH/Telnet connections internally so chance to anyone getting through is less, this is just an extra security measure.

If you are using telnet then the extra security measure will not help since passwords are sent as clear text. You should disable telnet and root logins for ssh. Login with regular user then su for admin tasks.