If the color is green, that means it’s safe. That system sources reviews and reputation scores to return a traffic color for each clickable page. As of writing, the behind-the-scenes hotfix should be working so no updates will be needed on users' side.WOT works by sending clickable webpages to a central system while the user browses the internet. Mozilla have been updating their customers via their Twitter, and Saturday morning confirmed they had identified the problem and gave assurances that a hotfix was about to be deployed. To their credit nonetheless, they have leapt into action to tried and resolve the situation immediately. Certificates such as this are pretty straightforward to renew, so it's a terrible oversight on their part. The same thing happened about three years ago but apparently Mozilla didn't learn from their mistake. This is particularly embarassing for Mozilla, not least because it's not the first time this has happened. In a statement to Engadget, Mozilla's Product Lead, Kev Needham, said "we know what the issue is and are working hard to restore add-on functionality to Firefox as soon as possible." It transpired that an intermediate signing certificate had expired, which is pivotal to the verification process for extensions and add-ons. But yesterday, Firefox users with any add-on installed found their beloved browser had reverted to its 'vanilla' form, as an expired security certificate meant all add-ons couldn't be verified and thus were disabled.Ĭonfused users headed to the Firefox subreddit and Mozilla's own 'bugzilla' forums where confirmation was given of the problem. You would think that a company whose main product is a browser would know a thing or two about security certificates. Mozilla have ascertained that an expired security certificate is to blame and a hotfix is being deployed now. What just happened? On Friday night as the clocks struck midnight, users of Mozilla's Firefox browser discovered that any add-ons they had installed no longer worked.
0 kommentar(er)
