![]() ![]() In the NSS library for example, which is the TLS library curl is typically built with on Redhat and Centos, handles the SSLKEYLOGFILE magic all by itself so by extension you have been able to do this trick with curl for a long time – as long as you use curl built with NSS. curl can be built using a dozen different TLS libraries and not just a single one as the browsers do. Just remember that if you record TLS traffic and want to save it for analyzing later, you need to also save the file with the secrets so that you can decrypt that traffic capture at a later time as well. Having done this simple operation, you can now inspect your browser’s HTTPS traffic in Wireshark. ![]() Go to Preferences->Protocols->SSL and edit the path as shown in the screenshot below. Setting the same file name path in the Master-secret field in Wireshark.set the environment variable named SSLKEYLOGFILE to a file name of your choice before you start the browser.You do this by making the browser tell Wireshark the SSL secrets: Since a long time back, the venerable network analyzer tool Wireshark (screenshot above) has provided a way to decrypt and inspect TLS traffic when sent and received by Firefox and Chrome. ![]()
0 Comments
Leave a Reply. |