Centralized Authorization Using a Directory Service, Part II
This defines the primary group IDs for jane to be 42 and for joe to be 57.
With the NIS group map you can add additional, secondary group memberships for accounts. The group entry:
defines a new group projectX with no password (*), group ID 127 and two members. No comments are allowed in the group file.
If you now set up a directory with read/write/execute permissions for group projectX:
# mkdir /projects/X/ # chgrp projectX /projects/X/ # chmod g+wrx /projects/X/
every member in the projectX group has permission to read/write/execute files inside that file space. The user might need to do a newgrp projectX first.
Whenever you need to add or remove accounts to or from the group map, do it on your NIS master server by editing the /etc/NIS/group file and executing the commands:
% cd /var/yp % sudo make group
These generate a new group map that makes the changes visible instantaneously on all clients. There is no need to touch any client to make these changes. Everything now is centralized in one place on your NIS master server.
Netgroups are very different from groups. Netgroups come in two flavors, user netgroups and host netgroups. Both types of netgroups can contain netgroups as members, so netgroup definitions can be hierarchical. Both types of netgroups are defined in the same netgroup file. Comments are allowed in the netgroup file.
Host netgroup definitions in /etc/NIS/netgroup look like this:
# Group of project groups: projects \ projectA \ projectB \ projectX # Group of hosts for Project X projectX \ (host1.example.com,-,) \ (host2.example.com,-,) \ (host3.example.com,-,)
These host netgroup definitions now allow you to, for example, export NFS space only to subsets of your machines. In your NFS server's /etc/exports file, you can use constructs like these:
# export the /projects directory to all machines # in the "projects" netgroup /projects @projects(rw,root_squash) # export Project X' space only to machines # in the "projectX" netgroup /projects/X @projectX(rw,root_squash)
Again, adding or removing hosts or adding/deleting netgroups is a simple edit of the /etc/NIS/netgroup file on your NIS master server. Execute cd /var/yp; sudo make netgroup to update the NIS map, and the changes are visible everywhere instantly.
User netgroups, which are netgroups with accounts as members, typically are used to restrict login to computers. User netgroup definitions look slightly different from host netgroup definitions:
# Group of project user groups u-projects \ u-projectA \ u-projectB \ u-projectX # Group of users in Project X u-projectX \ (-,jane,) \ (-,joe,) \ (-,nick,)
The prefix u- in the names is a convention to distinguish user netgroups from host netgroups.
With these definitions in place, you now can grant or restrict login access to your computers with these kinds of entries in a machine's local /etc/passwd file. Remove a + at the very end of the passwd files if present:
Allow access for all accounts in the u-projects netgroup and no one else:
Allow access for only the u-projectX netgroup members and no one else:
Allow access to everybody in u-projects but not in u-projectX:
Order here is important. The first match determines what happens.
Allow everybody in u-projectA and also account nick
The information about nick (home directory, login shell and so on) comes out of the NIS passwd map. It is better to avoid putting explicit account names in here, because management of these entries is not centralized.
To make this +/- syntax work, your clients need to have the entry
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Secure Desktops with Qubes: Introduction
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Fancy Tricks for Changing Numeric Base
- Seeing Red and Getting Sleep
- Working with Command Arguments
- Secure Desktops with Qubes: Installation
- Chris Birchall's Re-Engineering Legacy Software (Manning Publications)
- The Italian Army Switches to LibreOffice
- The FBI and the Mozilla Foundation Lock Horns over Known Security Hole
- Petros Koutoupis' RapidDisk
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide