Centralized Authorization Using a Directory Service, Part II
to the file /etc/sysconfig/network.
Restrict access to your new NIS server by creating a file /var/yp/securenets with the content:
# netmask # network 255.255.255.0 192.168.0.0
This is a crucial security step. The world is able to query your NIS server if you don't have this file.
The next step is to define the things you would like to put into NIS. For the purpose of authorization, the /etc/group and /etc/passwd files as well as something called netgroup are sufficient. However, many more things are possible. To get an idea, have a look at the file /var/yp/Makefile on your NIS server.
Below, I show how the three files I've mentioned are configured to be distributed by way of NIS.
Adjust the Makefile generating the NIS map database files:
# cp /var/yp/Makefile /var/yp/Makefile.save # vi /var/yp/Makefile
Change the following two entries from true to false to prevent the merging of passwd and shadow files as well as group and gshadow files:
Change the directory name where NIS should look for its data sources:
YPSRCDIR = /etc/NIS YPPWDDIR = /etc/NIS
Comment all files from which the NIS databases should not be built. I left only these three files:
GROUP = $(YPPWDDIR)/group PASSWD = $(YPPWDDIR)/passwd NETGROUP = $(YPSRCDIR)/netgroup
Comment the line starting with all: that contains the list of all potential NIS maps. Add the new line:
all: passwd group netgroup
Watch out for TAB characters. In a Makefile, you must use only TAB characters, not spaces, to indent commands.
Now, create the data source directory defined in the Makefile:
# mkdir /etc/NIS/ # chmod 700 /etc/NIS
and put a passwd file in there:
# grep -v '^root' /etc/passwd > /etc/NIS/passwd
You should remove not only the root account but all system accounts from this file and leave only the real user accounts.
If you still are using /etc/passwd with encrypted passwords, it now is time to convert them to Kerberos 5, as described in the previous article [LJ, February 2005]. If you don't do this, your encrypted passwords are exposed on the network when the passwd file is distributed to the slave NIS servers or to the NIS clients.
Now, collect the local /etc/passwd files from all the machines that are to be members of your new NIS domain. Remove all system accounts and then merge them together with:
% cat passwd_1 passwd_2 passwd_3 ... > passwd_merge
Remove all duplicate entries with this command:
% sort passwd_merge | uniq > passwd_uniq
Check the consistency of the remaining entries with:
% cut -d':' -f1 passwd_uniq | sort | uniq -c | \ egrep -v "\s*1"
If this produces any output, you have two different entries with the same account name. If the difference is not in the UID or GID field, simply decide on one of the entries and remove the other one. If the difference is the UID or GID field, you need to resolve this conflict, which can be rather complex.
Another consistency check is to see whether any two different accounts have the same UID, which is the case if this command:
% cut -d':' -f3 passwd_uniq | sort | uniq -c | \ egrep -v "\s*1"
produces any output; the second number in the output is the duplicate UID. Resolving this conflict again can be rather complex. Do the same kind of merging and checking for all your /etc/group files.
Copy the resulting files to /etc/NIS/passwd and /etc/NIS/group. I will return to the netgroup file later. Leave it out for now.
Now, start your master NIS server with:
# service ypserv start
Initialize the NIS maps with the command:
# /usr/lib/yp/ypinit -m
and follow the printed instructions.
In order to have all the NIS maps available to your NIS master server, you probably want to set up this machine as an NIS client as well. Make sure this NIS client can bind only to the NIS master as server in order to prevent circular dependencies when booting all your machines, as after a power outage.
Pick up any e-commerce web or mobile app today, and you’ll be holding a mashup of interconnected applications and services from a variety of different providers. For instance, when you connect to Amazon’s e-commerce app, cookies, tags and pixels that are monitored by solutions like Exact Target, BazaarVoice, Bing, Shopzilla, Liveramp and Google Tag Manager track every action you take. You’re presented with special offers and coupons based on your viewing and buying patterns. If you find something you want for your birthday, a third party manages your wish list, which you can share through multiple social- media outlets or email to a friend. When you select something to buy, you find yourself presented with similar items as kind suggestions. And when you finally check out, you’re offered the ability to pay with promo codes, gifts cards, PayPal or a variety of credit cards.Get the Guide