![]() ![]() Pale Moon forum • View topic – Warning: signed add-ons crash Pale Moonīy the way, hats off to the Pale Moon team for their rapid and effective response to a crisis that was not of their making. Pale Moon’s developers explain most of it in more detail here: ![]() I can’t personally vouch that that is the case, since I don’t have any corrupted extensions on hand to try it out with, but compatible AMO-hosted extensions signed with Mozilla’s new, non-corrupting signing routine do install just fine.Īnyway, that’s the best I can figure out what happened. Within maybe 36 hours, Pale Moon released and pushed a Pale Moon update that would supposedly no longer crash when users or the browser attempted to install extensions corrupted by Mozilla’s initial extension-signing routine. Within maybe 24 hours, Mozilla apparently fixed their signing process, and updating/installing extensions started working again in Firefox. Attempting to update extensions hosted at AMO simply returned a “no updates available” message (whether updates were available at AMO or not). Within maybe 12 hours, I believe Pale Moon’s developers stopped forwarding extension update requests from Pale Moon’s addons site to AMO, as an emergency measure. ![]() In my Pale Moon (the latest stable 圆4 release), attempting to update/install extensions would crash Pale Moon each and every time the attempt was made. In my Firefox (the latest stable release), attempting to update/install extensions would yield errors and installation would fail. When Mozilla started serving signed extensions from “AMO” (), around maybe 48 hours ago, its signature process apparently corrupted the extensions. I wonder if it didn’t depend on when you tried. ![]() Pale Moon didn’t crash when updating extensions….” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |