Why unsigned extensions are not allowed to be shared

Talk about add-ons and extension development.
New Member
Posts: 1
Joined: February 8th, 2018, 10:48 pm

Post Posted February 8th, 2018, 11:31 pm

Hi, MozillaZine community. I used to browse using Firefox and had tons of addons that modified the browser for convenience use but recently I came back from Chrome and realized most addons are now obsolete because they required mozilla to sign the extensions. Whats the reason for Mozilla to take this step?

Posts: 1
Joined: July 11th, 2010, 7:21 pm

Post Posted February 18th, 2018, 9:35 am

Malicious extensions, malware, malvertising, hijacked addons, data mining, bitcoin mining, impact to browser performance, advertising, keyloggers, botnets, to name a few reasons. Chrome has a similar process for the same reasons. When a user installs an add-on hosted on a Mozilla server they have a reasonable expectation that some level of security is being implemented to minimize the risk of hostile code. There have been alot of extensions found to be hostile and removed from both Mozilla and Chrome stores. Now that were seeing cross browser extension evolve due to Quantum, it only makes sense to protect the servers and users alike. S3 Translator is an amazing add-on that now works in any Chrome based browser, but with it's origin being Mozilla only.
I think this is really the rebirth of Firefox.

Return to Extension Development

Who is online

Users browsing this forum: No registered users and 1 guest