Click the button promising to be careful. (A) In a new tab, type or paste '''about:config''' in the address bar and press Enter/Return. Or maybe Qustodio can do the setup automatically after a reboot or in some other way. If that doesn't work, there is an export/import method. Once Firefox has picked up on the new "man in the middle" try switching the preference back to normal and see whether the education is permanent. I guess you'll know if you visit an HTTPS address and Firefox no longer objects. I'm not sure whether that will start working immediately or after the next time to exit Firefox and start it up again. (C) Double-click the security.enterprise_roots.enabled preference to switch the value from false to true (B) In the search box above the list, type or paste root and pause while the list is filtered (A) In a new tab, type or paste about:config in the address bar and press Enter/Return. Yes, Qustodio is intercepting your connection and presenting fake site certificates to Firefox, and Firefox is none too happy.Ĭould you try this temporary settings change to see whether this works: Well, the filter needs time to process what you're sending and retrieving, so that's not a huge surprise.ĭit antwoord in context lezen 👍 2 Alle antwoorden (3) Sites seem to load slower when value is at true. The alternative involves numerous steps I'll link to a thread that lists them for reference: The main negative is, in the situation that malware has injected a certificate into the Windows certificate store (rather than software you actually trust to read all your browsing connections), Firefox will play along rather than generating error screens. Setting that preference to "true" tells Firefox to trust sites that are trusted in the Windows certificate database, too.
Normally, Firefox relies on its own certificate file to assess whether it can trust what websites (or intermediaries) present to it. What is the disadvantage of leaving it at true? Thanks, changing the value to true worked but changing it back to false I get the same error.
0 kommentar(er)
