Users should not remove affected extensions from their installations the issue will resolve itself once Mozilla fixes it. I'd expect Mozilla to do that soon as the issue is widespread and affecting lots of Firefox users. The organization needs to renew the certificate or create a new one to resolve the issue.
The issue can only be resolved on Mozilla's end. You could change the system date to the previous day to resolve it temporarily as well, but that can lead to other issues. You need to set the preference to false on about:config to disable signing. Nightly, Dev and Android users may be able to disable signing of extensions some users reported that this resolved the issue temporarily on their end. Please check your connection" errors when they attempt to download any extension from the official repository. Related issues have been reported: some users cannot install extensions from Mozilla's official Add-ons repository. Firefox will block the installation of extensions with invalid certificates (or none), and that is causing the issue on user systems. I just won't be including Firefox next year.All Firefox extensions need to be signed since Firefox 48 and Firefox ESR 52. I can do that - I make the damn images for them every year. If Firefox can't do this for me, I will be uninstalling it from my PC and all 1000+ PC's in my workplace. I need to connect to this device, and this is non-negotiable.
Did at any point in the development of this newer version did someone stop and say "Hey, maybe some of our users don't want us shutting down these connections in their browser?" It is disgusting to me that a handful of developers can take an open-source program that masses of people use and take it in a direction that causes grief to these masses of users - without any input from them. I am not the only user having this problem, and as a user I should be able to configure my browser however I want, and if I want to connect to places with bad SSL certs, I have every right to do so. If there is an option to do so, please let me know.īut if there is not, just let me say that this is ridiculous. I used to be able to bypass this by disabling PKIX verification in about:config, but that doesn't seem to be working anymore. I don't know if it's self-signed, or expired, or what, but I *NEED* to connect to it - it's part of my job.Īn error occurred during a connection to *********.
I want to connect to a site that has an issue with it's SSL certificate.
0 kommentar(er)
