12.1. User-oriented network security12.1.1. Trusted hosts and trusted users12.1.2. Enabling transparent access12.1.3. Using netgroups12.2. How secure are NIS and NFS?12.3. Password and NIS security12.3.1. Managing the root password with NIS12.3.2. Making NIS more secure12.3.2.1. The secure nets file12.3.3. Unknown password entries12.4. NFS security12.4.1. RPC security12.4.2. Superuser mapping12.4.3. Unknown user mapping12.4.4. Access to filesystems12.4.5. Read-only access12.4.6. Port monitoring12.4.7. Using NFS through firewalls12.4.8. Access control lists12.4.8.1. ACLs that deny access12.4.8.2. ACLs and NFS12.4.8.3. Are ACLs worth it?12.5. Stronger security for NFS12.5.1. Security services12.5.2. Brief introduction to cryptography 12.5.2.1. Symmetric key encryption12.5.2.2. Asymmetric key encryption12.5.2.3. Public key exchange12.5.2.4. One-way hash functions and MACs12.5.3. NFS and IPSec12.5.4. AUTH_DH: Diffie-Hellman authentication12.5.4.1. Old terms: AUTH_DES, secure RPC, and, secure NFS12.5.4.2. Diffie-Hellman key exchange12.5.4.3. How RPC/DH works12.5.4.4. RPC/DH state and NFS statelessness12.5.4.5. Enabling NFS/dh12.5.4.6. Public and private keys12.5.4.7. Creating keys12.5.4.8. Establishing a session key12.5.4.9. NFS/dh checklist12.5.4.10. How secure is RPC/DH?12.5.5. RPCSEC_GSS: Generic security services for RPC12.5.5.1. Kerberos V512.5.5.2. SEAM: Kerberos V5 for Solaris12.5.5.3. Enabling Kerberized NFS12.5.5.4. Security and performance12.5.5.5. Combining krb5, krb5i, krb5p12.5.5.6. IPSec versus krb5i and krb5p12.5.6. Planning a transition from NFS/sys to stronger NFS security12.5.7. NFS security futures12.6. Viruses