News for hackers. Stuff that matters.

A comment on Firefox 42 will not allow unsigned extensions. Parent comment

Re:Firefox 42 will not allow unsigned extensions by _lce0 on Tuesday August 11, 2015 @12:07PM (#10042098)
> We see many copies of Firefox infested with rogue add-ons the user didn't ask for or isn't even aware of.

GoogleUpdate?

why Firefox could not remove these extension itself? I needed to remove some files from the harddisk --I doubt john.doe will be able to remove such evils

Please excuse the rant tone, these things make me feel my intimacy raped

[ Parent | on HN ]
Re:Firefox 42 will not allow unsigned extensions by kbrosnan on Tuesday August 11, 2015 @04:55PM (#10044321)
Mozilla does this from time to time for really egregious cases [1]. There is a high cost to staging the block. If the author is known there is a delay to try to get the author to ship a fix [2]. If it is unknown then the block can proceed rather quickly but the cost of changing the extension to avoid the block is usually cheap [3].

[1] https://addons.mozilla.org/en-US/firefox/blocked/ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=527135 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=937405

You can still use Dev Edition or Nightly with an about:config pref set.

[ Parent | on HN ]