Wpis z mikrobloga

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.


#firefox
  • 9
  • Odpowiedz
  • Otrzymuj powiadomienia
    o nowych komentarzach

@asdasdce2w:

Summary: Firefox marked addons due signing as unsupported, but doesn't allow re-downloads from AMO → All extensions disabled due to expiration of intermediate signing cert


The dates on the cert in question were:

Not Before: May 4 00:09:46 2017 GMT

Not After : May 4 00:09:46 2019 GMT
  • Odpowiedz
https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047/13

12:50 p.m. UTC / 03:50 a.m. PDT: We rolled-out a fix for release, beta and nightly users. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps.

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
  • Odpowiedz
via Wykop Mobilny (Android)
  • 0
@CeZiK_: Tyle, że problem z certyfikatem to oddzielna sprawa. Ja u siebie zaktualizowałem i jest ok. Tzn dodatki nadal nie mogę updejtnąć, wiadomo.. Trzeba poczekać ;-)
  • Odpowiedz