In this 3 weeks old post by the mad ppl at moz i read
Untrusted Certificates: Your browser might not recognize revoked or fraudulent security certificates, putting you at risk when visiting websites.
https://support.mozilla.org/en-US/kb/root-certificate-expiration
and I am finding a few thousand posts on ppl asking how to bypass this for testing etc.
No “solution” i found works and FF does not allow (unlike Chrome, Edge or any other sane browser) to simply proceed. There is “advanced options” and all…but no proceed.
The thousands and thousands of posts asking for this for over a decade are bummed out too.
- “Query OCSP responder servers to confirm the current validity of certificates” disabled is not working
- about:config anything with SSL,security.ssl.enable_ocsp_stapling, security.ssl.enable_ocsp etc no longer have an impact.
I know hardly anyone still uses the greedy slob machine but you die hards might know: how to allow to proceed ony ANY ssl cert in FF?
This question makes zero sense. If you want to use some kind of test or internal certificate, just go and buy one. And if you don’t want to buy one, just sign one yourself and make it trusted on your machine. Or better yet, configure your own CA, make that trusted and generate certificates to your hearts content.
Disabling certificate certification is not something that anybody should ever need or want.
While all websites should have valid certificates, I did run into a case a week ago of the Sears Home Services website seemingly having an invalid one.
In trying to cancel my grandma’s account with them, I found that their website wasn’t well mobile-optimized, and Firefox refused to load it, so I ended up having to use Chrome to load the website and cancel the service.
Loading such a website should be allowed, perhaps with a warning about phishing and/or other security risks. Given that there are valid websites with invalid certificates, their inaccessibility risks discouraging people from using Firefox.
Both Chrome and Firefox have the option to accept the certificate error and proceed to the site anyways. And do in fact show warnings not to do that, except if you know what you are doing.
You don’t really want to do that, but cases like you describe do exist. However you do want to double check what the issue is, because the error could also be due to some malware on the computer. It could have replaced the valid correct site with its own phishing site to get your credentials.
So please double and triple check, before your grandma asks why she had a $5000 credit card bill.
invalid argument according to ff die hards. maybe if we opt into more telemetry it would work ;-)
BS
i’d even go further: there are more request for this feature that ff users.
you just follow the moz doctrine: everybody who sees it different is wrong. chrome would not have the featurw of you were right.
maybe lets continue the discussion once ff is below 0.5% market share.