13,420
edits
Changes
no edit summary
<ol><li value="6">Switch back to the original terminal and re-run the netstat pipeline command again. Any change to the connection status?</li><li>Return to the second terminal, and logout of your ssh connection by typing <b><code><span style="color:#3366CC;font-size:1.2em;">exit</span></code></b>.
<li>Run the netstat command in the original terminal and check the state of the connection after logging out. Wait a few minutes and then check again. Record your observations.</li>
<li>Make certain to exit all connections, and that your shell is located in switch to your <u>'''centos3</u> server''' VM. You can verify this Verify that you are in the correct VM by entering the command: <b><code><span style="color:#3366CC;font-size:1.2em;">hostname</span></code></b><li>Use the Internet to search for "'''TCP 3 way handshake" ''' to see how TCP connections are established and closed.<br><br></li>
</ol>
::So far, we have learned to establish an ssh connection to another host using a password to establish your identity. But '''passwords are not the only or even the best way of authenticating your identit'''y. We can also use '''Public/Private key encryption'''.
::'''Public Key authentication''' is a method of establishing identity using a '''pair of encryption keys that are designed to work together'''. One key is known as your '''private key''' (which as the name suggests should remain private and protected) and the other is known as the '''public key''' (which as the name suggests can be freely distributed) The keys are designed to work together to encrypt data asymmetrically, that is to say that when we '''encrypt data with one of the keys it can only be decrypted with the other key''' from the pair.
::While it doesn't mean the message is <u>secure</u> as anybody could decrypt it with the public key, it does establish my <u>identity</u>, if the host can successfully decrypt the message then it must have come from the one person in possession of the private key.
<br>
