There is nowhere we could store that choice on the user’s machine that these greyware apps couldn’t change and plausibly claim they were acting on behalf of the user’s “choice” not to opt-out of the light grey checkbox on page 43 of their EULA. Many developers have asked why we can’t make this a runtime option or preference.
#Firebug plugin for firefox download software#
For the ones who do, we hope that modifying another program’s executable code is blatant enough that security software vendors will take action and stop letting these programs hide behind terms buried in their user-hostile EULAs.
#Firebug plugin for firefox download download#
We are sure some will take that step, but it won’t be an attractive option for a Fortune 500 plugin vendor, popular download sites, or the laptop vendor involved in distributing Superfish. By baking the signing requirement into the executable these programs will either have to submit to our review process or take the blatant malware step of replacing or altering Firefox. This is not a concern about hypotheticals, we have many documented cases of add-ons disabling the mechanisms through which we inform users and give them control over their add-ons. At least give users the ''OPTION'' of enforcing signatures for plugins defaulted to '''ON''', of course.
At least give users the OPTION of enforcing signatures for plugins defaulted to ON, of course.
0 kommentar(er)
