EEET2424/2427 Computer &Network SecurityLab 3:Sniffing and SSL
Aim:In this exercise,you are required to try some Information gatheringmethods. You need to have good background knowledge on networkssecurity protocol SSLfor this practice. You can searchthe Internet for help in answering some of the questions. However, direct cut and paste are not allowed.
Part A:
Intercept user names and passwordsin network connection without security protection.
Assume ahacker has connected his laptop to a hub andhassniffedthenetwork. Example.dat(in libpcap format)is thetracefileproduced.Answerthefollowingquestionsreferringto the trace file.
1.Name one softwarewhichcan open the Example.dat2.Thenodes of thenetworkare connected byhubs.If switches are used instead of the hubs in the network, can the hacker sniffler all the nodes?Elaborate your answer. 3.Some services,usernamesand passwords can be found outin thetrace file. What arethey(Hint: At least 2 usernames and services).Explainhow you find out the usernamesand passwords in detail.
Part B:
Explore SSL/TLSprotocol with Wireshark
Modified based onJ.F. Kurose, K.W. Ross’s SSL lab.
In this lab, you will investigate the Secure Sockets Layer (SSL)/ Transport Layer Security (TLS)protocol,focusing on theSSL/TLSrecordssent over a TCP connection. You will do soby analyzing a trace of the SSL/TLSrecords sent between your host and anspecified SSL enabled webserver.Investigate the variousSSL/TLSrecord types as well as the fields in the SSL/TLSmessages.
Use wireshark andcarry thefollowingactivities. Answer the following questions referringto your trace file.
1.Start your sniffing software2.Open your web browser and visit
https://www.rmit.edu.au/students/student-essentials/class-timetables3.Loginto youraccount4.Click on any link as you like5.Log out6.Stop your sniffing software
A look at the captured trace
Your Wireshark GUI should be displaying only the Ethernet frames that have SSL/TLS
records. It is important to keep in mind that an Ethernet frame may contain one or more
SSL/TLSrecords. (This is very different from HTTP, for which each frame contains either onecomplete HTTP message or a portion of a HTTP message.) Also, an SSL/TLSrecord may not completely fit into an Ethernet frame, in which case multiple frames will be needed to carry the record.
4.Find out the protocol name of thisSSL/TLSversion and version numbers(major and minor)
5.Locate the packet which contains the Certificate of the server? (There is special name for that packet in the protocol)
6. For each of the first 8 Ethernet frames, specify the source of the frame (client or
server), determine the number of SSL/TLSrecords that are included in the frame, and
list the SSL record types that are included in the frame. Draw a timing diagram
between client and server, with one arrow for each SSL record.
7. Each of the SSL/TLSrecords begins with the same three fields (with possibly differentvalues). One of these fields is “content type” and has length of one byte. List all
three fields and their lengths.
ClientHello Record:
8. Expand the ClientHello record. (If your trace contains multiple ClientHello
records, expand the frame that contains the first one.) What is the value of the
content type?
9. Does the ClientHello record contain a nonce (also known as a “challenge”)? If so,
what is the value of the challenge in hexadecimal notation?
10. Does the ClientHello record advertise the cyber suites it supports? If so, in the
first listed suite, what are the public-key algorithm, the symmetric-key algorithm,
and the hash algorithm?
ServerHello Record:
11. Locate the ServerHello SSL record. Does this record specify a chosen cipher
suite? What are the algorithms in the chosen cipher suite?
12. Does this record include a nonce? If so, how long is it? What is the purpose of the
client and server nonces in SSL/TLS?
13. Does this record include a session ID? What is the purpose of the session ID?
14. Does this record contain a certificate, or is the certificate included in a separate
record. Does the certificate fit into a single Ethernet frame?
Client Key Exchange Record:
15. Locate the client key exchange record. Does this record contain a pre-master
secret? What is this secret used for? Is the secret encrypted? If so, how? How long
is the encrypted secret?
Change Cipher Spec Record (sent by client) and Encrypted Handshake Record:
16. What is the purpose of the Change Cipher Spec record? How many bytes is the
record in your trace?
17. In the encrypted handshake record, what is being encrypted? How?
18. Does the server also send a change cipher record and an encrypted handshake
record to the client? How are those records different from those sent by the client?
Application Data
19. How is the application data being encrypted? Do the records containing
application data include a MAC? Does Wireshark distinguish between the
encrypted application data and the MAC?