https://mail.google.com/mail/u/0?ui=2&ik=fb1036a398&attid=0.1&permmsgid=msg-f:1611220453590653037&th=165c3477471d586d&view=att&disp=safe https://www.latindex.org/latindex/ficha?folio=28152

Comentários do leitor

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

por Sandy Travers (2019-07-23)


-text c-gray-1" >Many Firefox users around the world are browsing without their usual set of extensions after they suddenly stopped working earlier this evening. The event occurred as the clock rolled over on UTC (Coordinated Universal Time, aka GMT or Greenwich Mean Time), and impacted users quickly narrowed it down to "expiration of intermediate signing cert" -- as it's described on Mozilla's bug tracker.

This same problem almost happened three years ago, but "armagadd-on" 2.0 has torn things up once again. In a statement provided to Engadget, Product Lead Kev Needham said:

We're sorry that there is currently an issue where existing and new add-ons are failing to run or be installed on Firefox. We know what the issue is and are working hard to restore add-on functionality to Firefox as soon as possible. We'll continue to provide updates via our Twitter channels. Please bear with us while we get the problem fixed.

For now, there is at least one workaround, but it only applies if you're using the Firefox Developer or Nightly build. If you look under "about:config" (if you don't know what this is, you probably shouldn't try it) and set the " 77-725 dumps xpinstall.signatures.required" value to False, then your extensions will start working again.

Update: If you're on another version of Firefox, there is a way to temporarily fix it, but you'll have to repeat it every time you reopen the browser. It involves enabling add-on debugging and manually loading each extension's .xpi file.

Update 2 (5/4, 4 AM ET): While the Mozilla team continues to work on resolving the issue, security researcher Kevin Beaumont mentions that anyone using the Tor browser will want to make sure they keep the NoScript extension enabled to browse securely. This issue has affected the installed-by-default extensions in that browser as well, and going without it could expose your information.

Update 3 (5/4, 7:30 AM ET): The team has announced a hotfix is rolling out now. It's applied in the background, so you shouldn't have to do anything to receive it. However, to make sure you get it right away, you can follow these instructions:

In order to be able to provide this fix on short notice, we are using the Studies system. You can check if you have studies enabled by going to Firefox Preferences -> Privacy & Security -> Allow Firefox to install and run studies.

You can disable studies again after your add-ons have been re-enabled.

We rolled out a hotfix that re-enables affected add-ons. The fix will be automatically applied in the background within the next few hours.
For more details, please check out the update at website

- Mozilla Add-ons (@mozamo) May 4, 2019So sorry for the issue we're having with add-ons right now!

We're working hard to fix it and will keep you updated.

- Firefox 🔥 (@firefox) May 4, 2019No ETA for the fix yet; we're waiting on test results before making decision.

- Mozilla Add-ons (@mozamo) May 4, 2019