After the collapse of Mozilla Firefox's browser add-ons system at the end of last week, the company announced its commitment to better track its resources and create a way to quickly roll out updates when necessary.
By posting on her blog, Mozilla detailed some initial plans and revealed that next week will publish a list of all unexpected changes in the browser. "The error in browser add-ons was due to the expiration of the certificate used to sign these add-ons, which caused most of these additions to be disabled," said Eric Riscorella, chief technology officer at Firefox.
Eric Riccurla said the company noticed the problem last Friday afternoon. However, its security team noted that not all users encountered failure to run plugins, as they are verified every 24 hours, and the time changes according to each user.
Apparently, when Firefox started checking in plugins installed for each user, the add-on signature certificate expired, disabling all additions to the signature, which in theory were the majority. When users complained that Mozilla had taken too long to solve the problem, Eric Rescorala replied that the team had responded in less than 9 hours and that the solution reached all those affected within 12 hours after the incident. For CTO, this is very positive.
Eric Riscorella acknowledged that the solution did not reach all users, including those who used earlier versions of Firefox. In the case of these people, we recommend that you update to the latest version of your web browser, not just to receive the solution, but because it's a more secure version.
By posting on her blog, Mozilla detailed some initial plans and revealed that next week will publish a list of all unexpected changes in the browser. "The error in browser add-ons was due to the expiration of the certificate used to sign these add-ons, which caused most of these additions to be disabled," said Eric Riscorella, chief technology officer at Firefox.
Eric Riccurla said the company noticed the problem last Friday afternoon. However, its security team noted that not all users encountered failure to run plugins, as they are verified every 24 hours, and the time changes according to each user.
Apparently, when Firefox started checking in plugins installed for each user, the add-on signature certificate expired, disabling all additions to the signature, which in theory were the majority. When users complained that Mozilla had taken too long to solve the problem, Eric Rescorala replied that the team had responded in less than 9 hours and that the solution reached all those affected within 12 hours after the incident. For CTO, this is very positive.
Eric Riscorella acknowledged that the solution did not reach all users, including those who used earlier versions of Firefox. In the case of these people, we recommend that you update to the latest version of your web browser, not just to receive the solution, but because it's a more secure version.
0 Comments