And you have just located the password and username you have entered on the unprotected login page - whether or not the password and username are correct are irrelevant. Once you get there look in the red text paragraphs and try to find what I was able to locate in the picture. Then you will right click on it and go down to "FOLLOW" then to "TCP STREAM".
You can see exactly what I am talking about if you follow the pictures above. Then at the far right of the packet in the info section you will see something like ".login" or "/login". This drastically narrows the search and helps to slow down the traffic by minimizing what pops up on the screen. Cloudshark also tweeted to say: in CloudShark you can keep your keys secure decode without sharing. Click the Browse button to the right of (Pre)-Master-Secret log filename and select the session key filename that you also sent to them.
By filtering this you are now only looking at the post packet for HTTP. Select and expand Protocols, scroll down (or just type ssl) and select SSL. Wireshark comes with the option to filter packets. HTTP (Hyper Text Transfer Protocol) is the protocol we will be dealing with when looking for passwords. The second step to finding the packets that contain login information is to understand the protocol to look for.
0 kommentar(er)
