I had set the API trace level to info, also set other traces to info. Here the logs had been displayed, but nowhere i found the session key of either the server or the client.

I had set the "WRITE TRACE TO FILE" option, then to which file the Log Trace will be written.

If iam getting a page cannot be displayed error during an ssl session, will the unsniffer is capable of delivering the logs for the cause of failure.

Hi Ashok,

I checked with the developer yesterday. We do not write the session key (the master secret) to the log for security reasons. The log is permanent unlike capture files/key files. Moreover, the session key is not very important.

Unsniff can help you debug the "page cannot be displayed error". One obvious cause could be, you are sending a GET request and nothing is coming back in return. To debug these kinds of higher layer problems, enable the "Analyze Upper Layers" option in the TLS plugin. To do it.

1. Plugins->Customize
2. Locate the TLS option
3. Set the "Analyze upper layers" to TRUE

Next,
Import your capture file or start a new capture.
Then switch to the Sessions sheet. You will find a decrypted HTTPS session. Open it.

You will find all the HTTP requests that went out on the TLS session. See if any error is returned by the server, or whether it is not responding.

You mentioned a proxy server, does it forward TLS ? Is it a "transparent proxy" ? If so, it will not forward TLS. This is where I would look first.

Hope that helps,
Vivek