Difference between revisions of "Linux Services"
(→UFW) |
|||
Line 90: | Line 90: | ||
You will be familiar with compressing files in your regular operating system. In Linux it is also easy to do this via the GUI but on a server, we will need to do this via the command line. | You will be familiar with compressing files in your regular operating system. In Linux it is also easy to do this via the GUI but on a server, we will need to do this via the command line. | ||
− | Obtain the following 3 books: | + | Obtain the following 3 books; these are public domain books so this is completely free and legal: |
*https://www.gutenberg.org/files/76/76-0.txt | *https://www.gutenberg.org/files/76/76-0.txt |
Revision as of 06:00, 26 February 2020
In this lab, we will look at how command-line Linux servers can offer services. You may have heard of LAMP, which stands for Linux, Apache, MySQL, PHP and this is a very common software combination that has delivered the vast majority of Internet Services to the world. For example, this Wiki (csn.murdoch.edu.au) which is the same software stack as Wikipedia runs lamp. This page that you are looking at right now runs on a cloud-based server which does not have a Graphical User Interface (GUI).
This lab will also briefly explore networking, firewalls and command-line access. We will continue to expand your knowledge of the command line by extracting compressed files and searching for text.
Contents
Apache Web Server
Let's start by installing and configuring the Apache web server. Start by deploying the Ubuntu Operating system. Once you have booted into Ubuntu, open a terminal and type:
sudo apt update
This command will consult the repositories about the latest software available for the distribution. Type
sudo apt install apache2
This command will install the Apache web server. While we are installing software on our machines, lets install two additional pieces of software. Type
sudo apt install nmap sudo apt install openssh-server
Open up a web browser in the GUI and visit your own web page at http://127.0.0.1 Discuss with your partner what is special about the 127.0.0.1 address
Find out what your Ethernet IP address is with:
ifconfig
You'll also see a reference to the 127.0.0.1 address we used earlier. Trade IP addresses with your partner and see if you can access each others web page. Their page should look identical to yours. If you have problems then ensure that you log out of gateway.
Make some changes to the html of you apache web page with:
nano /var/www/html/index.html
OR
gedit /var/www/html/index.html
Two questions:
- What is the difference between nano and gedit?
- Did you get permissions errors when editing /var/www/html/index.html - how might you fix that?
Make some changes to your index.html page and get your partner to check your page.
Nmap
Type:
nmap [ipaddressofneighbor]
Nmap is a port scanning tool and will tell you what ports are open on a machine connected to the Internet. Have a look at the results. Can you identify any of the services that are running?
Try removing apache2 and then re-running the nmap test. What has changed and why? Reinstall Apache2.
UFW
UFW is the Ubuntu firewall. We will use sudo to make changes, why?
Try:
sudo ufw status verbose
Ask your neigbour to use nmap to scan your computer's ports.
Turn on the firewall:
sudo ufw enable
Verify that the firewall is running by issuing the "status" command again:
sudo ufw status verbose
Ask your neigbour to use nmap to scan your computer's ports. What has changed and why? Allow port 80
sudo ufw allow 80/tcp
Get your neighbour to nmap your computer again. What can they see? Can they still access your webserver? What has changed?
SSH
SSH is a program which allows you to get command line access to machines on the Internet. A username and password is required to access another machine. See if you can log into you neighbors machine via ssh with:
ssh [ipaddressofneighbor]
If this does not work, could it be a firewall problem. Can you selectively open the port required for ssh?
Dealing with compressed archives
You will be familiar with compressing files in your regular operating system. In Linux it is also easy to do this via the GUI but on a server, we will need to do this via the command line.
Obtain the following 3 books; these are public domain books so this is completely free and legal:
- https://www.gutenberg.org/files/76/76-0.txt
- https://www.gutenberg.org/files/36/36-0.txt
- https://www.gutenberg.org/ebooks/19033.txt.utf-8
First, we want to create a Tar archive from the 3 files:
Create a directory called Books
mkdir books
Then use the mv command to move the three books into the directory
tar cf books.tar books
You can now bzip this with
bzip2 books.tar
If you now do a:
ls -la
You should see books.tar.bz2 - compare the filesize of books.tar.bz2 with the sum of the three individual files. What sort of compression ratio did you observe?
If you wanted to you could decompress with:
bunzip2 books.tar.bz2 tar -xvf books.tar
Extra Work
Challenge 1
Once you have logged into your neighbor's machine, see if you can create a text file on their desktop saying Hi_[neighborsname]
Challenge 2
Try launching gedit while ssh'ed into your neighbor's machine. Was it successful? Why?
Challenge 3
scp or secure copy works similarly to the cp command that we used last week. The format is:
scp [source] [destination]
The difference between scp and cp is that scp is designed to be used over a network. It can copy a file or a set of files between any two Internet-connected Unix systems in the world.
See if you can use scp to securely copy a file between you and your neighbours PC. If you are stuck, see:
man scp
Once you have worked out how to copy a single file between machines, see if you can copy all the files in a directory to a foreign machine. Try:
scp [localpath] [ip]:/[path]
When you provide a path starting with a / this means that it is an absolute path. In this case, you would specify the entire directory structure.