In this exercise, you are going to capture live traffic from your email service. Begin by opening up your email service and preparing an email from you to yourself – you can use a subject line of “Homework” and a body of “Homework” if you chose. Don’t hit the send button yet.
Open up Wireshark, go to the “Capture” menu and tell it to “Start” capturing data. Now return to your email service and hit the send button. After the email is sent, tell Wireshark to “Stop” capturing data.
Look in the protocol column and see what protocol your email server uses.
What protocol did your system use?
The system I had used was a local client. It does not support secure communication and hence, I could only see TCP. But it used SSL while logging in to my email account. So as a conclusion, the user login is secure but not the data of email.
Open up Wireshark, go to the “Capture” menu and tell it to “Start” capturing data. Now return to your email service and hit the send button. After the email is sent, tell Wireshark to “Stop” capturing data.
Look in the protocol column and see what protocol your email server uses.
What protocol did your system use?
The system I had used was a local client. It does not support secure communication and hence, I could only see TCP. But it used SSL while logging in to my email account. So as a conclusion, the user login is secure but not the data of email.
As we can see above figure, after hitting “Send” button, the email is sent to the server in smaller packets. In frame 8, the email is finally received by the server. If we see further inside the HTTP part, we can find the encapsulated data. We can use the “binary view” to view this encapsulated data.
Above diagram shows the email has finally been sent to the destination address. This occurred in frame 17 which sends “successful” message to client.
No comments:
Post a Comment