See hueristics posts:
https://www.velvetbug.com/benb/icfix/
This SOLVED IT. FF 56.0.2 Linux 32b.
Quit waiting on moz, they don’t care, and not going to fix.
Thanks
I understand
less so - isn’t the blog that thing I linked to and which I said did not appear to have been updated for several days? Not even an “older ESR fix is in QA - please watch this space” announcement.
And as for “etc” - well this is not aimed at you personally but some parts of this community may sometimes fall into the trap of assuming everyone knows where everything is or may be. I can count the number of times I have ever had to come to the Mozilla site on the fingers of one hand. It took a lot of googling and linking here and there to get to this thread. A lot of the discussion around this certificate mess-up topic is arcane (in the extreme) to the average FF user. Most information seems aimed at developers or the very technically adept. Where is the public page for the millions of users who just want to know the nature of the issue and likely timescale and method for fixing whatever just severely broke their browser? “Studies”? Not an effing clue, mate. Hey-ho. More fool me for refusing to have things fixed that aint broke (i.e. staying religiously on ESR 52!)
/rant 
Anyway, holding my breath for a fix because LastPass, AdBlockPlus, ClassicThemeRestorer, ClassicToolbarButtons are things without which I will not use FF. Newer versions repel me. Sorry.
Interesting. What if I just wanted to import that .prem file and not run those two commands. Should not the existence of that certificate in the system be enough once FF is restarted? BTW… I am Windows 7 not Linux.
It should let you install new, but Firefox won’t immediately re-verify the existing disabled extensions. It would be approximately 24 hours after the time stamp in this preference in about:config
app.update.lastUpdateTime.xpi-signature-verification
To trigger re-verification sooner, you can right-click > Reset that preference, then do a normal Exit/Quit and restart of Firefox. Within about 60 seconds that should run and validly signed extensions should be re-enabled.
Also, I don’t know what a .prem file is, so you might get the certificate from a Mozilla site I’ve linked over here: https://www.jeffersonscher.com/sumo/intermediate-cert.html
At this point, the extensions are baked but still in QA. If you want to be a volunteer tester, you can go to the following bug, scan down a bit to the Attachments section, and install the extension for your version. Please report back on whether it works or not.
1 Like
Hi, @jscher2000, do you know how to convert that date-time format of about:config entry to mm-dd-yyyy?
For instance, here I have this:
app.update.lastUpdateTime.xpi-signature-verification = 1557482561
What does it means?
I want to know that to better control the time to trigger verifications and to better understand FF automatic procedure for that.
Thats a *NIX epoch date
Open your terminal and enter:
$ date -d @1557482561
Fri May 10 06:02:41 EDT 2019
1 Like
Nice!
Thank you, rec9140. 
One more question: FF will re-check certifications 24 hours after the last one?
Or when does it will do that?
How often?
Owh, here I’m using Windows, not Linux.
No terminal available.
How to do that on Windows 7?
No you need to run the commands.
Nothing will happen till then.
This what triggers the program to reactivate things… Soon as the 2nd one is run… my Ghostery button came back, my ad block… and all the the cookies that had gotten through erased.
Can’t speak to non Linux systems. Works here. 32B Linux FF 56.0.2
This is THE SOLUTION.
Or you can wait and wait and wait for a “trust chain” verified solution from moz… we are 8+ days and counting? You want to risk it that long on non Linux? I don’t even on Linux. I had to move to another browser till this solution came up, and no its not spyrome either.
Fix it, move on with life, and get back on track.
To all the others on V56 or less FOLLOW HEURSTICS POST! Save your self the grief, get your browser back. Move on… Don’t matter what OS Linux or non OS you are using don’t risk it with the garbage out there.
I already have the solution here.
My extensions are working fine.
I just want to better understand how and when FF makes its checks.
Thanks anyway.
Yes, I’ve found that minutes ago.
Thx.
I have imported this, followed by the two commands in the console from the other post.
As of now, my addons are back and I hope it stays this way.
Thank you for your effort and help!
https://bugzilla.mozilla.org/show_bug.cgi?id=1550793#module-attachments-title
For anyone who might prefer an extension:
- the top three at https://addons.mozilla.org/search/?q=epoch&type=extension
Very good! 
Jefferson,
Thank you so much for your post. That did the trick for me. Even tho’ the “studies” didn’t successfully install the updated certificate, following your instructions, it’s all good. I found the Mozilla cert which was not there previously.
FF did NOT disable after add-ons after 24 hours. So far, so good.
And I was able to install an update to an add-on which could not previously.
1 Like
I installed the extension from the bugzilla attachment for my version (52-60)…my version is 56.0.2, and all add-ons are back up and running again! I had to restart Firefox to get them enabled after I installed the hotfix, but all is good now. I’ll report back if it doesn’t hold or if I notice any other issues, but for now looks like all is well. 
1 Like
Affected users may wish to subscribe to this:
– I’m about to add a comment there …