https://discourse.mozilla.org/t/certificate...o-install/39047
https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

Possible workaround: about:config, xpinstall.signatures.required, set to false.

I got a message just now that I had not certified plugins. But when I clicked it I was told I didn't have any such plugins.

Update: https://blog.mozilla.org/addons/2019/05/04/...ons-in-firefox/

Seems FF has an extra sub menu for Unsupported extensions.

A day like this I'm happy for my extensive Hosts file blacklist.

I don't understand a thing. Is the warning a mistake? There's nothing wrong with the plugins?

And how does your blacklist come into it?

The extensions are OK, but Mozilla/Firefox has apparently messed up the certificates that are used to check that extensions are legitimate (these certificates are frequently updated in the background by browsers). It's not just a warning, Firefox refuses to run most extensions without the certificates, for security reasons: https://wiki.mozilla.org/Add-ons/Extension_Signing (unless you disable the certificate requirement, which is not recommended in the long run --then the extensions should work, but with a warning label).


For blocking ads and trackers. Without it I would be drowned in ads, now that extensions used for blocking ads and tracking no longer work.

Alas Tor browser bypasses the Hosts file, so I wonder if it's safe to use right now.

Depends on your level of paranoia, I guess.

Thanks, then I understood moz crew right. They use so many words I have no idea what they mean.

The workaround I posted in the threadstart works with Tor 8.0.8, but not for Firefox 66.0.3. But now FF 66.0.4 is released, and after updating, my extensions work again.