Login in to the server where the private key is stored. That is quite easy as long as you have access to the server where it is stored. The private key is essentially the secret decoder ring that allows us to view what is in the packets as if they were not encrypted. Just know there is a key piece of information we need to do decryption in Wireshark and that little bit of goodness is a private key. I'm not going to go in to the detail of why and how certificates are used. If you have ever installed OCS/Lync you are quite familiar with Certificates. This blog post aims to give you the tools necessary to see exactly what is on the wire, even when those packets are encrypted.
Good news is that when I recently checked on a new version of Wireshark, this process is immensely easier. Since I have a love for Wireshark already. I would also argue that Fiddler became so popular because doing Wireshark decrypting in the past was not for the faint of heart and it got the job done. It also doesn't work well if you want to see other packets along side the web services to correlate issues with STUN in Lync Web App. Now you are probably thinking this isn't anything special, I can do this with Fiddler.Īlthough Fiddler is a great tool, it doesn't work if you want to see what is happening with web services on Lync Phone Edition. Lync has some great debugging tools, but there are times, especially with web services, where I wish I could see more of what is being transmitted back and forth. There is nothing quite like being able to see exactly what is on the wire. If you have never decrypted SSL/TLS using Wireshark. Some of the newer ciphers make this blog post impossible without removing them (Diffe Hellman for example and leaving RSA). There is a sister blog post to this that shows how to decrypt HTTPS without using a private key.
0 kommentar(er)
