# Has Mozilla just killed FireFox? (effectively) **URL:** \ **Category:** Miscellaneous and Personal Stuff I Must Share\ **Created:** [May 4, 2019, 3:09am UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457 "2019-05-04T03:09:32Z")\ **Posts on this page:** 7\ **Page:** 3
**Author:** ![ThelmaLou](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/thelmalou/32/390_2.png) [@ThelmaLou](https://boards.straightdope.com/u/ThelmaLou)\ **Post date:** [May 7, 2019, 2:02pm UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/41 "2019-05-07T14:02:31Z")
FWIW, my themes came back yesterday morning. ---
**Author:** ![Rushgeekgirl](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rushgeekgirl/32/3715_2.png) [@Rushgeekgirl](https://boards.straightdope.com/u/Rushgeekgirl)\ **Post date:** [May 8, 2019, 1:20am UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/42 "2019-05-08T01:20:39Z")
Everything is still gone for me and my work scripts won’t work on Firefox. Thankfully I have scripts for Chrome still and they’re working fine. Probably won’t even bother going back to FF after this. ---
**Author:** ![carnut](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/carnut/32/3531_2.png) [@carnut](https://boards.straightdope.com/u/carnut)\ **Post date:** [May 8, 2019, 2:02am UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/43 "2019-05-08T02:02:34Z")
Welp, I just started getting these notices this afternoon. So I’m on Chrome at the moment. Not thrilled about it but it works. ---
**Author:** ![puzzlegal](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/puzzlegal/32/3827_2.png) [@puzzlegal](https://boards.straightdope.com/u/puzzlegal)\ **Post date:** [May 8, 2019, 4:52am UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/44 "2019-05-08T04:52:10Z")
I’m using Firefox on my Android. It seems to be fine. ---
**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\ **Post date:** [May 8, 2019, 3:59pm UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/45 "2019-05-08T15:59:28Z")
Backups are irrelevant in this case. The problem is that certificates went out of date, so a back up would still have the outdated certificates. The only thing you can do to make sure it doesn’t happen again is use the Development version of Firefox and disable signing. It’s not as insecure as they make it out to be: you’ll be prompted every time something wants to install an unsigned certificate, giving you a chance to say no. The main risk is that something bad gets by the signing process, which means it won’t be disabled. What bugs me is that this happened before, a couple years ago when they were first starting. I would have assumed they’d set up at least one test that would involve having the time set forward a bit to make sure that all certificates remained valid, as well as an active list of when every certificate along the chain would expire. I don’t know why the patches are getting undone: the latest release should have fixed the issue, since they just included a new certificate. ---
**Author:** ![rowrrbazzle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rowrrbazzle/32/414_2.png) [@rowrrbazzle](https://boards.straightdope.com/u/rowrrbazzle)\ **Post date:** [May 11, 2019, 5:26am UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/46 "2019-05-11T05:26:51Z")
> [@BigT](#): > > Backups are irrelevant in this case. True. But if you deleted add-ons in a vain attempt to fix the problem, a profile backup would still have them and any data associated with them. ---
**Author:** ![SmartAleq](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/smartaleq/32/163_2.png) [@SmartAleq](https://boards.straightdope.com/u/SmartAleq)\ **Post date:** [May 11, 2019, 5:16pm UTC](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457/47 "2019-05-11T17:16:47Z")
I went ahead and updated to 64 bit 66.0.5 and things were still borked so I’m just using the about:debugging workaround and manually loading in the extensions. What a clustermonkey. [Previous page](https://boards.straightdope.com/t/has-mozilla-just-killed-firefox-effectively/833457.md?page=2)