Home arrow Site Administration arrow Managing Users Part 1

Managing Users Part 1

This first part of chapter 5 "Module 5: Managing Users" covers understanding user properties and user databases. It also examines the technique of managing users for a single host. It starts by exploring the actual database files that contain information about users and moves on to the system tools available to manage the files automatically. (from the book Linux Administration, A Beginner's Guide, third edition by Steven Graham and Steve Shah, McGraw-Hill/Osborne, ISBN:0072225629, 2002).

TABLE OF CONTENTS:
  1. Managing Users Part 1
  2. Critical Skill 1 - Understand User Properites
  3. Shells, Startup Scripts and Mail
  4. Critical Skill 2 - Understand the User Databases
  5. The /etc/shadow File and The /etc/group File
By: McGraw-Hill/Osborne
Rating: starstarstarstarstar / 7
June 23, 2004

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

LinuxAdminUnder Linux, every file and program must be owned by a user. Each user has a unique identifier called a user ID (UID). Each user must also belong to at least one group, a collection of users established by the system administrator. Users may belong to multiple groups. Like users, groups also have unique identifiers called group IDs (GIDs).

The accessibility of a file or program is based on its UIDs and GIDs. A running program inherits the rights and permissions of the user who invokes it. (SetUID and SetGID, discussed in “Understand SetUID and SetGID Programs” later in this module, create an exception to this rule.) Each user’s rights can be defined in one of two ways: a normal user or the root user. Normal users can access only what they own or have been given permission to run; permission is granted because the user either belongs to the file’s group or because the file is accessible to all users. The root user is allowed to access all files and programs in the system, whether or not root owns them. The root user is often called a superuser.

If you are accustomed to Windows, you can draw parallels between that system’s user management and Linux’s user management. Linux UIDs are comparable to Windows SIDs (system IDs), for example. In contrast to Windows NT, you may find the Linux security model maddeningly simplistic: either you’re root or you’re not. Normal users cannot have root privileges in the same way normal users can be granted administrator access under NT. You’ll also notice the distinct absence of Access Control Lists (ACLs) in Linux. Which system is better? Depends on what you want and whom you ask.

In this module, we will examine the technique of managing users for a single host. Managing users over a network will be discussed in Module 19. Let’s begin by exploring the actual database files that contain information about users. From there we’ll examine the system tools available to manage the files automatically.

This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today. Buy this book now.



 
 
>>> More Site Administration Articles          >>> More By McGraw-Hill/Osborne
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

SITE ADMINISTRATION ARTICLES

- Coding: Not Just for Developers
- To Support or Not Support IE?
- Administration: Networking OSX and Win 7
- DotNetNuke Gets Social
- Integrating MailChimp with Joomla: Creating ...
- Integrating MailChimp with Joomla: List Mana...
- Integrating MailChimp with Joomla: Building ...
- Integrating MailChimp with Joomla
- More Top WordPress Plugins for Social Media
- Optimizing Security: SSH Public Key Authenti...
- Patches and Rejects in Software Configuratio...
- Configuring a CVS Server
- Managing Code and Teams for Cross-Platform S...
- Software Configuration Management
- Back Up a Joomla Site with Akeeba Backup

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: