I apologize for the inconvenience, but I believe that the new certificate generator will help ensure smooth debugging with current and future clients. If you are using Fiddler to capture secure traffic from a mobile device or Firefox, you will need to remove the old Fiddler root certificate from that device ( or Firefox) and install the newly-generated Fiddler certificate. Do you want to trust this root certificate) Accept all of the prompts that appear (e.g.Re-check the Decrypt HTTPS traffic checkbox.(Optional) Click the Fiddler.DefaultCertificateProvider link and verify that the dropdown is set to CertEnroll.Do you want to delete these certificates, etc) Fiddler has a support for this, but when I clicked Tools Compare Sessions, it prompted me to install Windiff.exe. Accept all of the prompts that appear (e.g. I use the awesome Fiddler2 to debug HTTP, and I needed to compare sessions.Click the Remove Interception Certificates button.Uncheck the Decrypt HTTPS traffic checkbox.Ensure that the text says Certificates generated by CertEnroll engine.
Please perform the following steps to recreate the Fiddler root certificate: Unfortunately, this change can cause problems for users who have previously trusted the Fiddler root certificate the browser may show an error message like NET::ERR_CERT_AUTHORITY_INVALID or The certificate was not issued by a trusted certificate authority. The biggest of the Fiddler changes is that CertEnroll is now the default certificate generator on Windows 7 and later. I’ve made changes to the latest versions of Fiddler to improve the performance of certificate creation, and to avoid problems with new certificate validation logic coming to Chrome and Firefox.
0 kommentar(er)
