SettingUpNISHowTo
Size: 6617
Comment: imported from the old wiki
|
Size: 6699
Comment: Question, completion
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= SettingUpNISHowTo = = SettingUpNISHowTo = |
|
Line 53: | Line 49: |
domain domainname server servername | domain <domainname> server <servername> |
Line 55: | Line 51: |
where domainname is the name of your domain (entered when you installed nis) and servername is the name of the server you're setting all this up on. (This lives in /etc/defaultdomain for the curious) |
where <domainname> is the name of your domain (entered when you installed nis) and <servername> is the name of the server you're setting all this up on. (This lives in /etc/defaultdomain for the curious) |
Line 153: | Line 148: |
Where "NFS server IP address" is the IP address of | ''Should this be '''NIS''' server IP address? --EvanProdromou'' Where "NFS server IP address" is the IP address of the NFS server. |
Line 184: | Line 182: |
CategoryDocumentation CategoryCleanup |
This needs to be written. It needs to be *easy*
link: http://tldp.org/HOWTO/NIS-HOWTO/index.html
See also the HOWTO in the package.
My attempt at satisfying the above:
NIS Server Config
[mailto:matt@mattcaron.net Matthew Caron]
Note: This assumes your server and clients have static IP addresses. NIS with dynamic IP addresses present a serious security hazard. See the "Security" section, below, for a discussion of security problems inherent with NIS and how to avoid them.
1. (Warty only) Add any client name and IP addresses to /etc/hosts. The server's IP should already be here. I do not mean 127.0.0.1, I mean the real IP available to the world. This ensures that NIS will still work even if DNS goes down. You could rely on DNS if you wanted, it's up to you.
2. Add the following line to hosts.allow:
portmap ypserv ypbind : list of IP addresses
Where the "list of IP addresses" string is, you need to make a list of IP addresses that consists of the server and all clients. These have to be IP addresses because of a limitation in portmap (it doesn't like hostnames).
3. Install NIS:
sudo apt-get install portmap nis
You will be asked for the name of your NIS domain. This can be anything; you're naming it. It just has to be the same domain for the server and all clients.
4. Edit /etc/default/portmap and comment out the ARGS="-i 127.0.0.1" line
5. Edit /etc/default/nis and set the NISSERVER line to NISSERVER = master
6. Edit /etc/yp.conf and add a server line of the form:
domain <domainname> server <servername>
where <domainname> is the name of your domain (entered when you installed nis) and <servername> is the name of the server you're setting all this up on. (This lives in /etc/defaultdomain for the curious)
7. Edit /var/yp/Makefile and read the instructions. It probably won't need a lot of modification. The only thing I changed was the MINGID line so that the group memberships would be propagated across the domain. I set it to 1.
8. Edit /etc/ypserv.securenets and add lines to restrict access to domain members. I use lines for specific hosts, like:
host 192.168.1.1 host 192.168.1.2 etc.
IMPORTANT!!!: comment out the 0.0.0.0 line. Otherwise, everyone gets access. (See "Security" below for discussion of why this is bad).
9. Build the DB for the first time, run:
sudo /usr/lib/yp/ypinit -m
and follow the instructions. This will probably throw some errors about not being able to talk to certain things. This is okay. (Other errors probably aren't).
10. Restart everything:
sudo /etc/init.d/portmap restart sudo /etc/init.d/nis restart
Note that I had some problems with portmap stopping and ended up having to kill -9 it.
11. If you change anything (add a user, etc.), make sure to do:
sudo make -C /var/yp
Security: NIS is a dangerous thing. Anyone who can get access to the daemon can dump your password lists. If they can do that, then they have your passwords. It doesn't matter that the passwords are encrypted; they are plaintext equivalent (since authentication is done with encrypted passwords, you don't need to know the text password, you just need to write an app to provide the encrypted one to the authentication system correctly). So, let's make sure that doesn't happen. How? Well, first, we restrict access:
1. Only allow domain members to talk to the appropriate services in hosts.allow. This implied that hosts.deny is set to domething like ALL:ALL in order for this to work.
2. Limit who the server will respond to by putting domain members in /etc/securenets
So, now we have the access restricted to specific IP addresses, we're good, right? Well, not quite. What if someone were to punt one of your machines off the network, assume it's IP address and dump the password file? You're still dead. Solution: IPSec (see the IPSecHowTo). You can set up all your domain members to only talk to each other over IPSec which will effectively authenticate that your client is who it says it is. How? Well, it encrypts traffic to the server with the server's key, and the server sends back all replies encrypted with the client's key. The traffic is decrypted with the respective keys. So, if the client doesn't have the keys that the client is supposed to have, it can't send or receive data. Provided the file containing the keys is reasonably secret (only readable by root), you can't get the keys unless you compromise the client. And, if you compromise the client, you can dump the password list anyway, so the attacker has got you (which is a flaw in most domain authentication systems).
NIS Client Config
[mailto:matt@mattcaron.net Matthew Caron]
A note about administration: Since the root user's account is disabled, make sure that whomever is to admin the machine is in the /etc/sudoers file on the client machine. It is also a good idea to have those users as local users on the client machine, with the same UID as is in the domain password list. It keeps things nice and consistent, and if there ever was a problem, you might need to have a local account to gain access to the machine.
1. Add server to /etc/hosts. This means that you can still find the server if there is a DNS failure.
2. Install the software you need
sudo apt-get install portmap nis
You will be asked for the name of your NIS domain. Enter the name of your NIS domain.
It is probably a good idea to then add a portmap line to /etc/hosts.allow for security reasons:
portmap : NFS server IP address
Should this be NIS server IP address? --EvanProdromou
Where "NFS server IP address" is the IP address of the NFS server.
3. Set up name services to use NIS:
Edit /etc/passwd to add a line at the end saying:
+::::::
Edit /etc/group to add a line at the end saying:
+:::
Edit /etc/shadow to add a line at the end saying:
+::::::::
This sets up those services to include NIS entries if a match isn't found in the file. You could change other services to use NIS by using the NIS service in /etc/nsswitch.conf, but these are the important ones.
4. Edit /etc/yp.conf and add the line:
domain domainname server servername
Where domainname is the name of your NIS domain and servername is the name of your NIS server.
5. Restart NIS:
/etc/init.d/nis restart
Note: sshd will need to be restarted to use the new authentication system. Just an FYI.
SettingUpNISHowTo (last edited 2008-08-06 16:27:15 by localhost)