13,420
edits
Changes
no edit summary
{|width="40%" align="right"
|}
=== Part 2: Establishing a Safe SSH Connection: Public Key Authentication ===
As a system administrator, you have the ability to generate or create public and private keys to ensure safe and secure ssh connections. The system administer can generate these keys for the first time, of if they suspect that a hacker has compromised the server, can remove the existing keys and generate new keys. A common type of attack, Arp Poisoning (Man in the Middle Attack), can be used to redirect packets to a third party while maintaining the illusion that the connection is secure. Therefore, understanding about the generation and management of public/private keys are important to the security of servers.
{|width="40%" align="right"
|- valign="top"
|}
=== Part 2: How do you use ssh to tunnel X. ===
'''Perform the following steps:'''
=INVESTIGATION 3: SECURING THE SSH CONNECTION=
[[Image:Tunnel.png|thumb|right|600px|You can also use an ssh connection to '''tunnel other types of traffic'''. There could be different reasons for doing this. For example tunneling traffic for an unencrypted application/protocol through ssh can '''increase the security of that application''' (i.e. deceive potential hackers).<br><br>Alternatively you could use it to '''circumvent a firewall that is blocking traffic''' you wish to use but allows ssh traffic to pass through.]]
=== Part 1: How do you use ssh to tunnel other traffic. ===
To help harden (protect a server from attack or "penetration"), system or security administrators have the ability to "trick" or "mislead" a potential hacker in order to prevent system penetration.
