Last Updated on April 13, 2021 by Admin
16.3.12 Lab – Examining Telnet and SSH in Wireshark Answers
Lab – Examining Telnet and SSH in Wireshark (Answers Version)
Answers Note: Red font color or gray highlights indicate text that appears in the instructor copy only.
Part 1: Examine a Telnet Session with Wireshark
Part 2: Examine an SSH Session with Wireshark
Background / Scenario
In this lab, you will configure a router to accept SSH connectivity and use Wireshark to capture and view Telnet and SSH sessions. This will demonstrate the importance of encryption with SSH.
Security Workstation virtual machine
Part 1:Examining a Telnet Session with Wireshark
You will use Wireshark to capture and view the transmitted data of a Telnet session.
Step 1:Capture data.
- Start the Security Workstation VM and log in with username sec_admin and password net_secPW.
- Open a terminal window and start Wireshark.
[sec_admin@secOps ~]$ wireshark &
- Start a Wireshark capture on the Loopback: lo interface.
- Open another terminal window. Start a Telnet session to the localhost. Enter username sec_admin and password net_secPW when prompted. Note that it may take several minutes for the “connected to localhost” and login prompt to appear.
[[email protected] ~]$ telnet localhost
Connected to localhost.
Escape character is ‘^]’.
Linux 5.10.14-arch1-1 (localhost) (pts/2)
Last login: Tue Feb 16 15:07:23 on pts/2
[[email protected] ~]$
- Stop the Wireshark capture after you have provided the user credentials.
Step 2:Examine the Telnet session.
- Apply a filter that only displays Telnet-related traffic. Enter telnet in the filter field and click Apply.
- Right-click one of the Telnet lines in the Packet list section of Wireshark, and from the drop-down list, select Follow > TCP Stream.
- The Follow TCP Stream window displays the data for your Telnet session with the Security Workstation VM. The entire session is displayed in plaintext, including your password. Notice that the username that you entered is displayed with duplicate characters. This is caused by the echo setting in Telnet to allow you to view the characters that you type on the screen.
- After you have finished reviewing your Telnet session in the Follow TCP Stream window, click Close.
- Type exit at the terminal to exit the Telnet session.
[sec_admin@secOps ~]$ exit
Part 2:Examine an SSH Session with Wireshark
In Part 2, you will establish an SSH session with the localhost. Wireshark will be used to capture and view the data of this SSH session.
- Start another Wireshark capture using the Loopback: lo interface.
- You will establish an SSH session with the localhost. At the terminal prompt, enter ssh localhost. Enter yes to continue connecting. Enter the net_secPW when prompted.
[sec_admin@secOps ~]$ ssh localhost
The authenticity of host ‘localhost (::1)’ can’t be established.
ECDSA key fingerprint is SHA256:1xZuV8NMeVsNQPRrzVf9nXHzdUP+EtgVouZVbWH80XA.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added ‘localhost’ (ECDSA) to the list of known hosts.
Last login: Sat May 23 10:18:47 2020
- Stop the Wireshark capture.
- Apply an SSH filter on the Wireshark capture data. Enter ssh in the filter field and click Apply.
- Right-click one of the SSHv2 lines in the Packet list section of Wireshark, and in the drop-down list, select the Follow > TCP Stream.
- Examine the Follow TCP Stream window of your SSH session. The data has been encrypted and is unreadable. Compare the data in your SSH session to the data of your Telnet session.
- After examining your SSH session, click Close.
- Close Wireshark.
Why is SSH preferred over Telnet for remote connections?
Type your answers here.
Answers may vary.
Similar to Telnet, SSH is used to access and execute commands on a remote system. However, SSH protocol allows users to communicate with remote system securely by encrypting the communications. This prevents any sensitive information, such as usernames and passwords, from being captured during the transmission.