"Firefox disabled all add-ons because a certificate expired (updated)"

[kane_magus]

Huh. So that's what the issue is. Guess I won't be using Firefox again, at least until they fix this issue. (Note, this includes things like ad blocking and NoScript.)

(EDIT) Okay, so apparently, there already is a fix for it, but it requires temporarily turning on the "Options -> Privacy & Security -> Allow Firefox to send technical and interaction data to Mozilla -> Allow Firefox to install and run studies" setting, which I had the "Allow Firefox to send technical and interaction data to Mozilla" turned off. However, once the add-ons are working again, it looks like you can turn that back off again. (/EDIT)

Comments

[owsf2000]

Depending on your version of firefox, you can get a fix almost instantly.

In Tools->Options->Privacy&Security scroll down to firefox data collection and use.

Enable the "Allow Firefox to install and run studies."

I sat with that going for a minute then restarted firefox and my plugins were enabled soon after again. I then promptly turned off that shit again.

Earlier versions of firefox doesn't have that option (might be 55 and up, I didn't see it on 54 so I ended up updating firefox.)

If I were any more cynic I'd almost believe mozilla let the certificates expire to get people to update with this quick fix. As they plan on having a fix for it without people needing to resort to studies "eventually".

Certainly sounds like one of those "Nice browser ya got there..." scenarios.

[kane_magus]

Heh, yeah, I saw that on another site and edited my post with it, which occurred before your comment here showed up for me. ^^;

If I were any more cynic I'd almost believe mozilla let the certificates expire to get people to update with this quick fix. As they plan on having a fix for it without people needing to resort to studies "eventually".

Yeah, I thought the exact same thing, when I saw what the fix was. If that was indeed the case (and we'll likely never know for certain, either way), then that's some Microsoft-level horseshittery.

[kane_magus]

And, huh, it looks like the fix was actually mentioned in the initial article I linked to as well, though I didn't see it there for some reason. Oh well. *shrug*