Changes

| '''cloning-source.ops335.org''' || '''164.30.20.100''' || '''Cloning -source''' used to create other servers for other assignments.

<ol><li value="5">You should use the options that you used in your lab1 to setup the static network, plus you should use the DOMAIN parameter to set the '''ops335.org''' domain for your cloning-source.</li><li> Make certain your cloning -source can connect to the Internet using the newer static configuration.</li><li>Run a '''yum update''' for this cloning source.</li><li>Make certain that SELinux is set to '''enforcing'''.</li><li>Do not install software on your cloning source: you are expected to install other software on your "cloned" VMs instead.<br>(For example, if you are required to install bind in a clone, install it in the clone as opposed to the "cloning source")</li><li>If you have created a '''regular user''' when you installed this machine, '''delete that regular user''' (you are only to access this server via root account).</li><li>Set up an SSH server on this "cloning source". Make sure that '''PermitRootLogin''' is set to '''yes''' for this server. Also make sure that only the root account is permitted to login using key authentication. If other users are required to be created in a later assignment, they should be permitted to log in with a their username and password.</li><li>Generate a key pair on your '''Host Machine for your root account''' (leave the pass-phrase blank).</li><li>Make sure you can log in from your '''root account''' on your '''Host Machine''' to the '''root account''' on the '''cloning source''' virtual machine (without a pass-phrase).</li><li>Do '''not''' place that newly-generated private key on the "cloning source" VM.</li></ol>