Find here-in below how to set the SSLKEYLOGFile to capture the session key in-order to decrypt the SSL traffic.
1) Launch the terminal and export the SSL Key Log File.
$ export SSLKEYLOGFILE="/Users/sdamodaran/Documents/outputkeyfile"
2) $ open /Applications/Google\ Chrome.app/
3) After opening the chrome application, you can see the "outputkeyfile" file generated. The session keys are stored under this file.
1) Start run the Wireshark Packet Capture.
2) Now reproduce the issue in the existing chrome browser.
3) Save the Wireshark Packet Capture File.
4) Go to the Wireshark -> Preferences -> Protocols -> select "TLS"
5) Point the session key file as shown in the below.
6) Click ok to view the decrypted traffic.
1) Click the Windows ICON button.
2) Enter Env
3) Edit environment variables for your account.
4) Click new user variable and set the variable name as "SSLKEYLOGFILE"
5) set the Variable value as "C:\Users\jthomas\sslkeylog.txt
6) Now reproduce the issue in the existing chrome browser.
7) Save the Wireshark Packet Capture File.
8) Go to the Wireshark -> Edit -> Preferences -> Protocols -> select "TLS"
5) Point the session key file as referred in the previous Mac OS example.
If you collect the Packet Capture, along with one time session key file with the above procedure. It will be helpful to troubleshoot the client side issues.
|Note: This is one time session key between client and server. This session key will not be valid for the next browser session.|