Changes

← Older edit

OPS235 Lab 7 - CentOS7 - HD2

34,939 bytes removed, 06:32, 26 April 2018

Redirected page to OPS235 Lab 7 - CentOS7 - SSD2

~~= LAB PREPARATION =~~ ~~===Purpose / Objectives of Lab 7===[[Image:firewall.png|thumb|right|180px|Protecting a computer network from unauthorized access is one of the many day-to-day operations for a Linux system administrator and/or security specialist]]~~ Setting up a computer network is very important, but there are many other operations that occur on a daily basis that can include '''trouble-shooting''', '''repairing network connection issues''' as well as '''maintaining network security'''. System administrators need to '''protect or "harden" their computer networks from "penetration" from unauthorized computer users'''. Hardening a computer system can range from running an '''IDS''' (Intrusion Detection System) to monitoring and flagging suspicious activity to implementing screen savers on workstations. In this lab, you will learn how to install and configure the SSH service on a VM to allow users to securely access and share data between authorized personnel. In addition, you will learn various methods of running and configuring an ssh server which include: using '''Public Key Authentication''', setting up an '''SSH tunnel''' in order to securely run graphical applications safely among computers in the network, '''disabling root login''', and '''changing the default ssh communication port''' to mislead potential penetration testers (also known as "pen-testers" or "hackers"). You will also learn how to setup a firewall using the '''iptables''' command in order to control the flow of packets throughout your computer server. ~~Main Objectives~~ * To set up, configure Secure Shell Services ('''ssh/sshd''')* To customize '''sshd''' to create a more private, secure system* Use ssh to '''tunnel X applications'''* To tunnel network traffic via other communication ports* Learn the basics of the '''iptables''' command used to configure and maintain a firewall for protection and troubleshooting a Linux server ~~{|cellpadding="15" width="100%" cellspacing="0"~~ ~~|- valign="top"~~ ~~|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;"|Minimum Required Materials ~~ ~~|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;padding-left:20px;"|Linux Command Reference ~~ ~~|- valign="top"~~ ~~| |[[Image:harddrive.png|thumb|left|75px|Removable SATA Hard Disk]]~~ ~~|style="padding-left:20px;"|[[Image:ubs-key.png|thumb|left|85px|USB key (for backups)]]~~ ~~|style="padding-left:20px;"|[[Image:log-book.png|thumb|left|70px|Lab7 Log Book]]~~ ~~|style="padding-left:20px;" |Networking Utilities [http://man7.org/linux/man-pages/man1/ssh.1.html ssh] [http://man7.org/linux/man-pages/man1/ssh-keygen.1.html ssh-keygen] [http://linux.die.net/man/1/ssh-copy-id ssh-copy-id] [http://man7.org/linux/man-pages/man1/scp.1.html scp] [http://man7.org/linux/man-pages/man1/sftp.1.html sftp] [http://man7.org/linux/man-pages/man8/netstat.8.html netstat] [http://man7.org/linux/man-pages/man8/ifconfig.8.html ifconfig] [http://man7.org/linux/man-pages/man8/ping.8.html ping] [http://man7.org/linux/man-pages/man8/arp.8.html arp] [http://zenit.senecac.on.ca/wiki/index.php/IPTables iptables] ~~ ~~|style="padding-left:20px;"|Additional Utilities [http://man7.org/linux/man-pages/man7/hostname.7.html hostname] [http://linux.die.net/man/8/restorecon restorecon] [http://linux.die.net/man/8/chkconfig chkconfig] Configuration Files [http://linux.about.com/library/cmd/blcmdl5_ssh_config.htm ssh_config] [http://linux.about.com/od/commands/l/blcmdl5_sshdcon.htm sshd_config] |style="padding-left:20px;"|SSH Reference [http://support.suso.com/supki/SSH_Tutorial_for_Linux A good ssh tutorial] [http://it.toolbox.com/blogs/locutus/shh-securing-ssh-howto-10640 A good HOW-TO to make ssh more secure]~~|} ~~=INVESTIGATION 1: INSTALLING AND MAINTAINING AN SSH SERVER=~~ So far, you have learned to use the '''ssh''' utility to establish a secure connection to a remote server to perform tasks, administer the server. For these common operations, you have issued the ''ssh'' command, which is actually the '''client''' application for ssh. In order to connect to a remote server (like your VMs, Matrix, etc) they need to be running the SSH service (i.e. the ssh daemon). In this section, you will learn how to install and configure an SSH server on an existing VM. You will also learn how to generate private and public keys in order to allow secure connections between your Linux machines (host as well as VMs). ~~=== Part 1: Confirming sshd service is Running on VMs. ===~~ ~~:'''Perform the following steps:'''~~ ~~# Launch your c7host machine and ALL of your VMs.# Switch to your '''c7host''' VM.# Create a file in your current directory with some text in it called: myfile.txt~~# Issue the following command (using your Matrix login id): <code>scp   myfile.txt   yourmatrixid@matrix.senecac.on.ca:/home/yourmatrixid</code> and enter your Matrix password. What did this command do?# Issue the following sngle command (using your Matrix login id): <code>ssh   myfile.txt yourmatrixid@matrix.senecac.on.ca   ls /home/yourmatrixid</code> and enter your Matrix password. What did this command do? How does it differ from using issuing the ssh command without the ls command? How is this useful? The client ssh application contains the utlities: '''ssh''', '''scp''' and '''sftp''' (learned in ULI101) to connect to remote Linux servers in order to issue commands or transfer files between Linux servers. You can install the SSH service on your Linux server, although this has already been performed upon installation. We will now confirm that the ssh service is running on all of your VMs. ~~# OpenSSH should have been installed by default. Let's confirm this by issuing the command: <code>rpm -qa | grep ssh</code># You should see a number of packages installed including openssh-clients and openssh-server~~ # <code>openssh-server</code> installs a service called '''sshd'''. Confirm that this service is running by issuing the command: <code>systemctl status sshd</code><ol><li value="9">Now that you know the service is running, investigate what '''port number''' and '''protocol''' sshd uses by issuing the command: <code>netstat -atunp | grep sshd</code> What protocol and port is the sshd process using? What is the state of the port? Why would you think that UDP ports don't have a state?</li>~~<li>Reissue the <code>netstat</code> command without the '''-n''' option. What is the difference?</li><li>Make sure the '''sshd''' service is running on '''all 3 of your VM's'''</li><li>Remember that you can view the '''/etc/services''' file in case you need to reference a service with a corresponding port number.</li></ol>~~ ~~===Part 2: SSH Server Security Configuration===~~ Any time you configure your computer to allow logins from the network you are leaving yourself '''vulnerable to potential unauthorized access''' by so called "hackers". Running the sshd service is a fairly common practice but '''care must be taken to make things more difficult for those hackers that attempt to use "brute force" attacks to gain access to your system. Hackers use their knowledge of your system and many password guesses to gain access'''. They know which port is likely open to attack (TCP:22), the administrative account name (root), all they need to do is to "guess" the password. Making your root password (and all other accounts!) both quite complex but easy to remember is not hard. ~~The Linux system administrator can also '''configure the SSH server to make the SSH server more secure'''. Examples include not permitting root login, and change the default port number for ssh.~~ ~~:'''Perform the following steps:'''~~ ~~# For this section, you will still be using your '''c7host''' and '''centos1''' VMs.# The next change you can make is to prevent the root account from logging in to sshd altogether.# Change to your '''centos1''' VM and open a terminal.~~ # Edit the file '''/etc/ssh/sshd_config''' and look for the option <code>PermitRootLogin</code>. '''Un-comment the option''' (or add the option if it does not appear) and change the option value to <code>no</code>. '''NOTE:''' Now any hacking attempt also has to guess an account name as well as the password. If you need to ssh with root access, ssh as a regular user and use '''su -''' to become root. # Even better, it is possible to restrict access to just specific users that require it: Edit the file '''/etc/ssh/sshd_config''' and add a new option of <code>AllowUsers account</code> using '''your''' login account for account # In order for these changes to take affect, you need to restart the sshd daemon. Issue the following command to restart the '''sshd''' service: <code>systemctl restart sshd</code># Try SSHing from your '''c7host''' VM to your '''centos1''' VM as '''root'''. Where you successful? Now try SSHing from your c7host VM to your centos1 VM as a regular user that was permitted to connect via ssh. Did it work? What would happen for other user accounts that were not permitted?~~# Next, let us "fool" potential penetration testers by changing the default port number that sshd uses from port 22 to port 2200.~~ # Edit the '''/etc/ssh/sshd_config''' file again, un-comment the port option and change the '''port number''' it uses from ''22'' to <code>2200</code>. ~~# Restart the '''ssh''' service.~~ ~~# Confirm the new port is being used with the '''netstat''' command.# Switch to your '''centos1''' VM.# Issue the commmand: <code>ssh username@centos1</code>. What happens? What port do you think that command is using by default?# Now issue the following command to ssh via port "2200": <code>ssh -p 2200 username@centos1</code>. Where you able to connect?<ol><li value="17">Finally, as a system administrator, you should periodically monitor your system logs for unauthorized login attempts.</li><li>On CentOS systems the log file that is used is '''/var/log/secure''' </li><li>It also logs all uses of the '''su''' and '''sudo''' commands.</li><li>Attempt to connect to all of your VM's as root and other users using both public key and password authentication. Use some '''su''' and '''sudo''' commands also. </li><li>Inspect the log to see what kind of information is logged.</li></ol>~~ ~~'''Answer INVESTIGATION 1 observations / questions in your lab log book.'''~~ ~~=INVESTIGATION 2: ADDITIONAL METHODS TO SECURE YOUR SSH SERVER =~~ ~~{|width="40%" align="right" cellpadding="10"~~ ~~|- valign="top"~~ |{{Admon/note |Storing Fingerprints | When a user connects to a host using ssh, the host sends a fingerprint or digital signature to the client to establish its identity. The first time a connection is established the identity must be stored for subsequent connections. The fingerprints are stored separately for each user in a file called <code>~/.ssh/known_hosts</code> . From now on when you connect to that host the client will compare the received fingerprint against the list of known hosts before connecting. If the fingerprint does not match it could indicate somebody had setup a system to impersonate the computer you wish to connect to and you would receive a message like this}} |}~~=== Part 1: Generating Private and Public Keys (Public Key Infrastructure) ===~~ As a system administrator, you have the ability to generate or create '''public''' and '''private''' keys to ensure safe and secure ssh connections. This will require a user to prove who they say they are in order to access a Linux server via SSH (i.e. Authentication). The system administer can generate these keys for the first time, or if the system administrator suspects that a hacker has compromised or trying to penetrate the server, they 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. ~~:'''Perform the following steps:'''~~ # ~~Switch to your '''centos3''' VM. ~~ :We can use the '''netstat''' utility as a trouble-shooting / confirmation tool to view the SSH service and determine which STATE the SSH service is performing: '''LISTENING''', '''ESTABLISHED''', '''CLOSED''' , or '''WAITING''' ~~<ol><li value="2">Run the '''netstat -atunp''' command (pipe to "grep sshd") to check the state of a possible ''ssh connection''. What is the state (i.e. LISTENING or ESTABLISHED)?</li><li>While in your '''centos3''' VM, issue the following command to connect to the same VM via ssh: <code>ssh ops235@centos3</code></li><li>Enter yes at the prompt, and enter your OPS235 password. The output should appear similar as what is shown below: :The authenticity of host 'centos3 (192.168.235.13)' can't be established. :RSA key fingerprint is 53:b4:ad:c8:51:17:99:4b:c9:08:ac:c1:b6:05:71:9b. :Are you sure you want to continue connecting (yes/no)? yes :Warning: Permanently added 'centos3' (RSA) to the list of known hosts. </li>~~ ~~<li>Issue the following command to confirm that you connected to your centos3 VM: <code>hostname</code></li></ol>~~REDIRECT [[Image:spoof.png|thumb|right|485px|If you receive a message like the one displayed above, you should investigate why it is happening as it could indicate a '''serious security issue''', or it could just mean that something on '''the host has changed'''(i.e. the OS was reinstalled)]]~~<ol><li value="7">Re-run that same '''netstat pipeline command'''. Any change to the connection status?</li><li>Log-out of your ssh connection by typing <code>exit</code>.<li>Run that same '''netstat''' command again. Wait a few minutes and then check again. Record your observations.</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 secure as anybody could decrypt it with the public key, it does establish my identity, if the host can successfully decrypt the message then it must have come from the one person in possession of the private key. ~~<ol><li value="10">Switch to your '''centos2''' VM.</li><li>Confirm you are in your centos2 VM by entering the command: <code>hostname</code></li><li>Make certain that you are in your centos you are NOT logged in as root!''' (you have been warned!)</li><li>To generate a keypair (public/private keys), issue the following command: <code>ssh-keygen</code></li><li>Press ENTER to accept the default, then enter a pass~~OPS235_Lab_7_-~~phrase used to establish your identity, and re~~_CentOS7_-~~enter the pass-phrase to verify. The output should appear similar as what is shown below:</li></ol>~~ ~~<pre style="font-family:monospace;background-color:white;border-style:none;padding-left:50px;">Generating public/private rsa key pair.Enter file in which to save the key (/home/ops235/.ssh/id_rsa):~~ ~~Enter passphrase (empty for no passphrase):Enter passphrase again:Your public key has been saved in /home/ops235/.ssh/id_rsa.pub.The key fingerprint is:ef:de:31:67:f7:15:a4:43:39:15:5d:78:1b:e8:97:74 ops235@centos3The key's randomart image is:+--[ RSA 2048]----+| .+=|| .+oE|| .+.o=|| ..++ || S o.. || . . .|| . o o o|| . . = .o|| .o . .|+-----------------+</pre>~~ <ol><li value="15"> After generating the keys it prompts you for the location to save the keys. The default is '''~/.ssh''' Your private key will be saved as id_rsa and your public key will be saved as '''id_rsa.pub'''</li><li>You will then be prompted for a pass-phrase. The pass-phrase must be entered in order to use your private key. Pass-phrases are more secure than passwords and should be lengthy, hard to guess and easy to remember. For example one pass-phrase that meets this criteria might be "seneca students like fish at 4:00am". Avoid famous phrases such as "to be or not to be" as they are easy to guess. It is possible to leave the pass-phrase blank but this is dangerous. It means that if a hacker were able to get into your account they could then use your private key to access other systems you use. </li>~~<li>Now issue the command <code>ssh-copy-id -i ~/.ssh/id_rsa.pub ops235@centos3</code></li><li>When prompted for password, enter OPS235's root password</li>~~ ~~<li>Try using ssh to now log into your '''centos3''' VM from your '''centos2''' VM. What happens? Were you required to use your pass-phrase?</li><li> Issue the '''hostname''' command to verify that you are successfully logged into your '''centos3''' VM.</li><li>Make certain to logout of your '''centos3''' system. Use the '''hostname''' command to verify you are back in your centos2 server.</li></ol>~~ ~~{|width="40%" align="right" cellpadding="10"|- valign="top"~~|~~[[Image:tunel-gedit.png|thumb|right|550px|You can use an SSH tunnel with options to allow running of applications on remote Linux servers.]]~~|} ~~=== Part 2: Securely Running Graphical Applications Between Linux Servers===~~ You can also use ssh to '''tunnel window and bitmap information''', allowing us to login to a remote desktop host and '''run a Xwindows application''' such as gedit or firefox and the application will run on the remote host but be displayed on the local host. ~~:'''Perform the following steps:'''~~ ~~# For this section, you will be using your '''c7host''' and '''centos1''' VMs.# Switch to your c7host VM, open a terminal and remain logged in as a regular user.~~# Issue the following command to connect to your '''centos1''' VM: <code>ssh -X -C yourUserID@centos1</code>   (where 'yourUserID' is your user account name on centos1) (The '''-X''' option enables the forwarding of X window information, and the '''-C''' option enables compression for better performance). ~~# Once the connection is properly established, run the command <code>gedit</code># The ''gedit'' window will display on your '''c7host''' VM, but in reality, this application is running on your '''centos1''' VM!# Enter some text and save your editing session.~~ ~~# Exit the '''gedit''' application.# In which VM was the file saved? What does that tell you about the use of tunneling for this section?# Experiment with running other GUI applications through '''ssh'''.~~ ~~'''Answer INVESTIGATION 2 observations / questions in your lab log book.'''~~ ~~=INVESTIGATION 3: MANAGING FIREWALLS FOR PROTECTION & TROUBLESHOOTING =~~ ~~{| width="40%" align="right" cellpadding="10"|- valign="top"~~|[[Image:chains.png|thumb|600px|right|When using iptables packets must pass-through "a chain of policy rules" in order to handle packets. If a packet matches a rule, then an action is taken (some examples include: '''ACCEPT''', '''DROP''', '''REJECT''', or '''LOG'''); otherwise, the packet will be directed to the default policy chain. ]]|}~~==== Linux Firewall (iptables) Concepts====~~ Since Linux servers can be connected to the Internet, it is very important to run a firewall to control what comes into the computer system, what goes out of the computer system, and what may be forwarded to another computer. A utility called '''iptables''' can be used to set the firewall rules on a Linux server. Basically, there is a list ('''chain''') of policy rules that '''packets''' must pass-through in order to handle packets. If a packet matches a rule, then an action is taken (some examples include: '''ACCEPT''', '''DROP''', '''REJECT''', or '''LOG'''). If the packet passes through the chain of rules without a match, then the packet is directed to the default policy chain (for example: ''ACCEPT'', ''REJECT'', or ''DROP''). ~~You can create your own '''customized chains''' (which you will learn in the OPS335 course) but to keep thing simple, we only deal with 3 '''common predefined chains''':~~ ~~:*'''INPUT''': Packets coming into current Linux server:*'''OUTPUT''': Packets leaving current Linux server:*'''FORWARD''': Packets being routed between Linux servers~~ ~~=== Part 1: Listing & Clearing Existing iptables Rules ===~~ ~~Let's get some practice using the iptables command as we introduce concepts such as listing CHAIN rules, and clearing the CHAIN rules:~~ ~~:'''Perform the following steps:'''~~ ~~# For the remainder of this section, use your '''c7host''' machine.# Issue the following command to list the existing iptables policy rules: <code>iptables -L</code>.# Were there already iptables policy rules that already existed by default?~~# Before we proceed, we need to understand various methods to list iptables rules: '''Listing iptables Rules:''' <table width="100%" cellpadding="10" cellspacing="0" border="1"><tr><td width="30%">'''iptables -L'''</td><td>List all iptables rules (eg. INPUT, OUTPUT. FORWARD, and any customized chains (if any)</td></tr><tr><td>'''iptables -L -v'''</td><td>Verbosely List all iptables rules including information such as total size of packets affected by rules</td></tr><tr><td>'''iptables -L CHAIN-NAME'''</td><td>List all iptables rules for that particular chain-name for less clutter (eg. INPUT or OUTPUT, etc)</td></tr></table> # Issue the following Linux command: <code>iptables -L INPUT</code> What do you notice is different with this command compared to the previous iptables command?~~# Issue the iptables command separately to display the rules for the '''OUTPUT''' chain and for the '''FORWARD''' chain.~~# Issue the following command: <code>iptables -L -v </code> What do you notice about this command as opposed to the first iptables command you issued? What sort of additional information does this command provide regarding affected packets? # Sometimes it may be useful to completely clear the rules for all or a particular chain. Note the options that can be used to clear (or flush) the iptables rules, '''Clearing (Flushing) iptables Rules:''' <table width="100%" cellpadding="10" cellspacing="0" border="1"><tr><td width="30%">'''iptables -F'''</td><td>Clears the rules for ALL of the chains</td></tr><tr><td>'''iptables -F CHAIN-NAME'''</td><td>Clears the rules for only the specified CHAIN-NAME (eg. INPUT or OUTPUT)</td></tr></table> # Issue the following command to reset the iptables rules for the INPUT chain: <code>iptables -F INPUT</code>~~# Issue the '''iptables -L INPUT''' command to verify that the iptables rules for the INPUT chain have been cleared.~~# Now, issue the command: <code>iptables -F</code> and then issue the command: <code>iptables -L</code> . What do you notice? ~~=== Part 2: Setting a Default Policy / Setting Policy Exceptions (iptables) ===~~ Usually when setting policy rules with iptables, a general "overall" policy is set (default policy chain). A good way to think about setting policies is to have a safety net to take some sort of action to prevent un-handled packets from passing through the firewall by mistake.After the default policy is set-up, then specific exceptions to the default policy can be added to control specific network traffic. An example would be to set a default policy for incoming network traffic (INPUT chain) to DROP everything, and then set an exception certain exceptions (like ssh connections). Note the following table below for policy setting examples. :'''Policy Setting Examples:''' <table width="100%" cellpadding="10" cellspacing="0" border="1"><tr><td width="30%">'''iptables -P INPUT DROP'''</td><td>Drops all incoming packets regardless of protocol (eg. tcp, udp, icmp), port numbers (eg. 22, 80) or source or destination IP Addresses. Setting a default rule to DROP all incoming traffic would make it easier to specify a few exceptions.</td></tr><tr><td>'''iptables -P INPUT ACCEPT'''</td><td>Accepts all incoming packets regardless of protocol (eg. tcp, udp, icmp), port numbers (eg. 22, 80) or source or destination IP Addresses. It would seem that setting a default rule to ACCEPT all incoming traffic would require A LOT of exceptions to help "lock-down" the server for protection! It really depends on the server set-up and what the Linux system administrator wants to accomplish.</td></tr></table> ~~:'''Perform the following steps:'''~~ ~~# Issue the following Linux command: <code>iptables -P INPUT DROP</code>~~# Issue the iptables command verify the INPUT policy has been set (look for the Policy section, NOT INPUT). After the overall default policy is set, then you can create policy rules that are "exceptions" to the default policy rules. These iptables commands are more complex since you need to determine: <ul><li>'''Where each rules appears in the chain'''? (order can be important)</li><li>'''Which protocol(s)''' are affected (eg. tcp, udp, icmp)</li><li>'''What source or destination IP Addresses''' are affected?</li><li>'''What port numbers''' are affected?</li><li>'''What action to take''' if all of the above conditions are met? (eg. ACCEPT, REJECT, DROP, or LOG)</li></ul> '''iptables Command Structure (for setting exceptions): (NOTE: If element in column is not specified in the iptables command, then rule relates to ALL elements)''' <table width="100%" cellpadding="10" cellspacing="0" border="1"><tr valign="top><td>Place Rule in Chain</td><td>Chain Name</td><td>Specify Protocol</td><td>Source/Destination IPADDR</td><td>Port Number</td><td>Action -></td><td>Target</td></tr><tr valign="top"><td>'''-A''' (add / Append to bottom of chain) '''-I''' (insert at top of chain) '''-i CHAIN-NAME 5''' (insert before line 5) </td><td>'''INPUT''' '''OUTPUT''' '''FORWARD''' '''CHAIN-NAME'''</td><td>'''-p tcp''' (tcp packets) '''-p udp''' (datagram packets) '''-p tcp,udp,icmp''' (combined) (refer to '''/etc/protocols''' )</td><td>'''-s IPADDR''' (originating IPADDR) '''-d IPADDR''' (destination IPADDR)</td><td>'''--sport 22''' (originating port 22 - SSH) '''--sport 80''' (originating port 80 - http) (refer to '''/etc/services''')</td><td>'''-j''' </td><td>'''ACCEPT''' '''REJECT''' '''DROP''' '''LOG'''</td></tr></table> ~~# Make certain you are in your '''c7host''' machine.# Determine the '''external facing address''' of your c7host machine (ip address should start with 10. - otherwise, type ip address in web-browser)# Have a lab neighbour try to ping that external facing address. Were they successful?~~# Issue the following iptables policy to DROP all incoming connections: <code>iptables -P INPUT DROP</code>~~# Have your neighbour try to ping your external facing IP Address. What happened? Why?# Have your neighbour obtain their external facing IP Address# Issue iptables command to ADD ping exception from your neighbour's IPAddress and neighbour test# Have neighbour test sshing into your c7host. Successful?# Issue iptables command to insert before rule #1 for ssh exception and neighbour test# List iptables rules for INPUT chain# Issue iptables rule at bottom of OUTPUT chain to DROP http (port 80 connections).# Open another web-browser. Can you connect to a webpage?# Issue iptables rule to flush the OUTPUT chain. Does your web-browser now work?# We will keep the rules for the INPUT chain.# Shutdown all VMs and restart your c7host Linux machine.# List the iptables rules for the INPUT chain. What happened?# Proceed to the next part to learn how to learn how to make your iptables rules persistent.~~ ~~=== Part 3: Making iptables Policies Persistent ===~~ Any changes to your iptables policy rules will be lost when you restart your Linux server, unless you make your iptables rules persistent. Failure to perform the following steps after setting up your firewall rules can cause confusion and wasted time. ~~:'''Perform the following steps:'''~~ ~~# Flush all of your iptables rules by issuing the following command: <code>iptables -F</code># Verify there are no iptables rules by issuing the command: <code>iptables -L</code># Make a backup of the file '''/etc/sysconfig/iptables''' by issuing the command: <code>iptables-save > /etc/sysconfig/iptables.bk</code>~~#To make the iptables rules '''persistent''' (i.e. keeps rules when system restarts), you issue the command: <code>iptables-save > /etc/sysconfig/iptables</code>~~# Verify that the file '''/etc/sysconfig/iptables''' exists.# Restart your iptables service and test your configuration.~~ # Before we can use this new port we must change our firewall to allow traffic through the new port number and block access to port 22 by issuing the command: <code>iptables -I INPUT -p tcp -s0/0 --dport 2200 -j ACCEPT</code># Next, we will drop any incoming traffic to port 22 by issuing the command: <code>iptables -I INPUT -p tcp -s0/0 --dport 22 -j DROP</code>~~# We have now possibly mislead a potential "hacker" to the true port for our ssh server's communication channel (port).~~ ~~'''Answer INVESTIGATION 3 observations / questions in your lab log book.'''~~ ~~= LAB 7 SIGN-OFF (SHOW INSTRUCTOR) ={{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines as well as your host machine.}}~~ ~~:'''Perform the Following Steps:'''# Make certain ALL of your VMs are running.# Switch to your '''c7host''' VM and '''su -''' into root.# Change to the '''/root/bin''' directory.# Issue the Linux command: <code>wget http://matrix.senecac.on.ca/~murray.saul/ops235/lab7-check.bash</code># Give the '''lab7-check.bash''' file execute permissions (for the file owner).# Run the shell script and if any warnings, make fixes and re-run shell script until you receive "congratulations" message.~~#Arrange proof of the following on the screen: <blockquote>✓ '''centos2''' VM:<blockquote><ul><li>have logged into centos3 VM using '''public key authentication''' (with a pass-phrase)</li></ul></blockquote>✓ '''c7host''' Machine:<blockquote><ul><li>have tunneled Xwindows application from '''centos1''' via ssh</li><li>have tunneled http through firewall using ssh (on web-browser</li><li>Run the '''lab7-check.bash''' script in front of your instructor (must have all <code> OK </code> messages)</li></ul></blockquote>✓ '''Lab7''' log-book filled out. ~~= Practice For Quizzes, Tests, Midterm & Final Exam =~~ ~~# What port does sshd use by defaults?~~ ~~# What file is used to configure sshd?# What sftp commands are used to upload/download files?# What kind of files are stored in the "~/.ssh/" directory?# How do you determine whether the sshd service is running on your system or not?# What is the purpose of the ~/.ssh/known_hosts file?# What is the purpose of the ~/.ssh/authorized_keys file?# Which system log file records each use of the sudo command?# How do you stop the sshd service?# How do you tunnel XWindows applications?# What port is the default scp port?# What port(s) is/are used by httpd service?~~ ~~[[Category:OPS235~~_SSD2]]

Msaul

Administrators

13,420

edits

Changes

OPS235 Lab 7 - CentOS7 - HD2

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

get involved with CDOT

courses

course projects

links

Tools