{"id":29133,"date":"2010-10-11T17:25:03","date_gmt":"2010-10-11T17:25:03","guid":{"rendered":"http:\/\/euvolution.com\/futurist-transhuman-news-blog\/unix-sysadmin-boot-camp-user-management\/"},"modified":"2010-10-11T17:25:03","modified_gmt":"2010-10-11T17:25:03","slug":"unix-sysadmin-boot-camp-user-management","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/planetology\/unix-sysadmin-boot-camp-user-management.php","title":{"rendered":"UNIX Sysadmin Boot Camp: User Management"},"content":{"rendered":"

\"RyanNow that you’re an expert when it comes to bash<\/a>, logs<\/a>, SSH<\/a>, and passwords<\/a>, you’re probably foaming at the mouth to learn some new skills. While I can’t equip you with the “nunchuck skills” or “bowhunting skills” Napoleon Dynamite<\/a> reveres, I can<\/em> help you learn some more important — though admittedly less exotic — user management skills in UNIX. <\/p>

Root User<\/h3>

The root user — also known as the “super user” — has absolute control over everything on the server. Nothing is held back, nothing is restricted, and anything can be done. Only the server administrator should have this kind of access to the server, and you can see why. The root user is effectively the server’s master, and the server accordingly will acquiesce to its commands. <\/p>

Broad root access should be avoided for the sake of security. If a program or service needs extensive abilities that are generally reserved for the root user, it’s best to grant those abilities on a narrow, as-needed basis.<\/p>

Creating New Users<\/h3>

Because the Sysadmin Boot Camp<\/a> series is geared toward server administration from a command-line point of view, that’s where we’ll be playing today. Tasks like user creation can be performed fairly easily in a control panel environment, but it’s always a good idea to know the down-and-dirty methods as a backup.<\/p>

The useradd<\/code> command is used for adding users from shell. Let’s start with an example and dissect the pieces:<\/p>

useradd -c \"admin\" -d \/home\/username -g users\\ -G admin,helpdesk -s\\ \/bin\/bash userid<\/code><\/p>

-c \"admin\"<\/code><\/strong> – This command adds a comment to the user we’re creating. The comment in this case is “admin,” which may be used to differentiate the user a little more clearly for better user organization.
-d \/home\/username<\/code><\/strong> – This block sets the user’s home directory. The most common approach is to replace username<\/code> with the username designated at the end of the command.
-g users\\<\/code><\/strong> – Here, we’re setting the primary group for the user we’re creating, which will be users<\/code>.
-G admin,helpdesk<\/code><\/strong> – This block specifies other user groups the new user may be a part of.
-s\\ \/bin\/bash userid<\/code><\/strong> – This command is in two parts. It says that the new user will use \/bin\/bash<\/code> for its shell and that userid<\/code> will be the new user’s username.<\/p>

Changing Passwords<\/h3>

Root is the only user that can change other users’ passwords. The command to do this is:<\/p>

passwd userid<\/code><\/p>

If you are a user and want to change your own password, you would simply issue the passwd<\/code> command by itself. When you execute the command, you will be prompted for a new entry. This command can also be executed by the root user to change the root password.<\/p>

Deleting Users<\/h3>

The command for removing users is userdel<\/code>, and if we were to execute the command, it might look like this:<\/p>

userdel -r username<\/code><\/p>

The –r<\/code> designation is your choice. If you choose to include it, the command will remove the home directory of the specified user.<\/p>

Where User Information is Stored<\/h3>

The \/etc\/passwd<\/code> file contains all user information. If you want to look through the file one page at a time — the way you’d use \/p<\/code> in Windows — you can use the more<\/code> command:<\/p>

more \/etc\/passwd<\/code><\/p>

Keep in mind that most of your important configuration files are going to be located in the \/etc<\/code> folder, commonly spoken with an “et-see” pronunciation for short. Each line in the passwd<\/code> file has information on a single user. Arguments are segmented with colons, as seen in the example below:<\/p>

username:password:12345:12345::\/home\/username:\/bin\/bash<\/code> <\/p>

Argument 1 – username<\/code> – the user’s username
Argument 2 – password<\/code> – the user’s password
Argument 3 – 12345<\/code> – the user’s numeric ID
Argument 4 – 12345<\/code> – the user group’s numeric ID
Argument 5 – \"\"<\/code> – where either a comment or the user’s full name would go
Argument 6 – \/home\/username<\/code> – the user’s home directory
Argument 7 – \/bin\/bash<\/code> – the user’s default console shell<\/p>

Now that you’ve gotten a crash course on user management, we’ll start going deeper into group management, more detailed permissions management and the way shadow file relates to the passwd<\/code> usage discussed above. <\/p>

-Ryan<\/p>

Related Posts:<\/h4>