Full corrective releases published ΠΈ that suggest a replacement fix and restore disabled add-ons. However, there are several unresolved side effects:
- Some add-ons, such as Epubreader, in about:addons after a certificate renewal, or remain in an unsupported state. The issue concerns add-ons without an identifier in the manifest.json file, which were removed if the digital signature verification failed. Such additions reinstall (data will be restored, as they remain in the directory with the profile);
- loss of data and settings in add-ons that use the functionality (Containers), such as in the Multi-Account Containers and Facebook Container add-ons. Users from scratch reconfigure these add-ons in about:addons;
- design themes. Users re-install them with ;
- to default values ββmodified by add-ons settings for the home page and search engines. The user needs to re-
homepage and search engine.
For older versions (Firefox 56.0.2 and older) that do not include (a component to support research, conduct a survey and unscheduled activation of new features), by enthusiasts solving the problem by extracting the certificate from with a fix. Extracted write to a pem file and import this file through the Options/ Privacy & Security/ Certifcates/ View Certifcates/ Authorities/ Import dialog.
In addition, it can be noted the issue of Tor Browser's dependency on the Mozilla infrastructure. Recall that users of Tor Browser due to a problem with the certificate the bundled NoScript add-on that provides an additional layer of protection. To restore, it is enough to set the xpinstall.signatures.required = false setting in about:config, but the very fact that users' installations of Tor Browser depend on a third party, whose actions can disable additional levels of anonymity, raises questions.
Source: opennet.ru