Hello, I have tried the latest developers edition (2.0.0rc1), 1.99 and the latest stable, 1.12.8 and I am unable to decrypt traffic from one particular certificate. I am able to decrypt traffic from another website with another key so I believe my wireshark settings are set to a working state. The certificate was created in IIS and exported to a PFX file. I have extracted the key with openssl and removed the password. I created a test site in a new windows server install and bound the certificate. The site is a basic IIS under construction page. My debug shows these messages (edited down):
asked 26 Oct '15, 14:45 Sandyw edited 26 Oct '15, 14:47 Kurt Knochner ♦ |
2 Answers:
That's a possible sign, that you have the wrong private key for the certificate. Please check the Modulus of the private key and the public key (cert). See my answer to a similar question: BTW: What's the Wireshark version that created the ssl debug file? 2.0.0rc should have some code to match the private/public key based on the Modulus. See the comment of @Lekensteyn in the following question.
Regards answered 26 Oct '15, 14:49 Kurt Knochner ♦ edited 26 Oct '15, 15:06 |
Ok I feel rather stupid about that..I thought I fixed that yesterday I originally posted that it didn't work but it just did! Doesn't work with 1.12.5 but it just worked with the latest dev release. The strange part is that I was testing a similar but different certificate, bought from the same place but just a few months prior, also SHA256 and I was able to decrypt with 1.12.5 of Wireshark. Same web server, same client. Thank you so much! answered 28 Oct '15, 14:25 Sandyw edited 28 Oct '15, 14:31 |
Thanks so much for responding Kurt
Regarding the modulus, I ran the following commands as per another post I saw before yours (https://ask.wireshark.org/questions/22813/not-able-to-decrypt-ssl-data-with-private-keys):
The two outputs were identical which tell me I’m using the right private key.
I’ve gone between the latest stable release and the latest dev release so I can’t remember which release I was on when I posted the debug but I’ll re-post as I’ve re-installed 2.0.0rc1. The capture was done with 1.12.8 but the debug logs is from opening the file with 2.0.0rc1.
Went back to Edit this so its readable..I’m not used to the formatting in this forum..
I was looking for that line! 0xC014 is a cipher with Diffie Hellman key exchange (TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) and that means you cannot decrpyt it by using the RSA key of the server. That’s why DH is being used.
So, unless you can convince the browser (or server) to export the session keys, there is no way to decrypt this session.
See here:
and my answer to a similar question:
Regards
Kurt