An attacker can use a method named Port Scanning to examine which ports are open on a given host, learning details about which software the server is running on publicly-addressable interfaces. This information helps the attacker to gain a better understanding of where and how to attack the victim server. Port scanning takes advantage of conventions in TCP and ICMP that seek to provide a sender with (perhaps too much!) information on why their connection failed. In this part, you will use the Nmap tool* to scan the server scanme.nmap.org. By doing so, you should be able to see the powerful information that a simple scan can reveal. In your scan, make sure to: 1. Only scan scanme.nmap.org DO NOT scan any other servers. You should only scan a server if you have explicit permission from the server operator to do so. 2. Record the traffic with Wireshark (see part 2) 3. Use a TCP SYN scan. (Hint: Read the nmap man pages to find the appropriate flag to use) 4. Enable OS detection, version detection, script scanning, and traceroute. (Hint: This is a single flag) 5. Do a quick scan (-T4). 6. Scan all ports. Answer the following questions briefly based on the results of the scan: 1. What is the full command you used to run the port scan (including arguments)? 2. What is the IP address of scanme.nmap.org? 3. What ports are open on the target server? What applications are running on those ports? (For this part, you only need to report the service name printed by nmap.) 4. The target machine is also running a webserver. What webserver software and version are being used? What ports does it run on?