Hello, I've been reading through the documentation and various forum posts related to this issue. This thread seems to be the most relevant to my situation. Here's some of the specifics of my setup:
1.) Windows 8.1 (VM) & Fiddler 4.6.2.32002
2.) I've tried just about every permutation, but the version that allows me to see specific error message in the LOG is HTTPS protocols of "<client>;ssl2;ssl3;tls1.0;tls1.1;tls1.2"
3.) Certificate Maker: CertEnroll engine
4.) Trying to reach:
a.) https://sslanalyzer.comodoca.com/?url=https%3A%2F%2Frecon-rest.net.wwe.com
b.) https://sslanalyzer.comodoca.com/?url=https%3A%2F%2Fs3.amazonaws.com
c.) https://sslanalyzer.comodoca.com/?url=https%3A%2F%2Fsecure.net.wwe.com%2F
5.) LOG statements:
a.) 11:50:32:0159 fiddler.network.https> HTTPS handshake to recon-rest.net.wwe.com (for #15) failed. System.ComponentModel.Win32Exception The client and server cannot communicate, because they do not possess a common algorithm
b.) 12:08:23:0180 fiddler.network.https> HTTPS handshake to s3.amazonaws.com (for #745) failed. System.ComponentModel.Win32Exception The client and server cannot communicate, because they do not possess a common algorithm
c.) 11:55:03:2740 fiddler.network.https> HTTPS handshake to secure.net.wwe.com (for #203) failed. System.ComponentModel.Win32Exception The client and server cannot communicate, because they do not possess a common algorithm
I think C (secure.net.wwe.com) may be a lost cause until they update the cert on on the server (as I see there is no matching algorithm), but A and B seem like there is actually a matching algorithm (0xA), and that algorithm seems to be supported in Windows 8.1: https://msdn.microsoft.com/en-us/library/windows/desktop/mt767781(v=vs.85).aspx.
Please let me know if there is anything I'm missing in setting up Fiddler to be able to successfully decrypt this traffic.
Thanks,
-Sam
