4 ms·
Both of those things (unsigned plugins causing permanent warnings and/or only being enabled for a developer edition) happen because not doing them means leaking
by derefr 10y ago
Both of those things (unsigned plugins causing permanent warnings and/or only being enabled for a developer edition) happen because not doing them means leaking open the one last (huge) hole malware can infect computers through
The modern browser 1. is its own OS, but 2. doesn't have any concept of a privilege-level separation. That means any random program running as user X is free to install an extension into user X's Chrome or Firefox profile without needing to ask permission. And then said extension can harvest your social-network profiles, replace ads with their own, etc.
- vetinari 10y ago> Both of those things (unsigned plugins causing permanent warnings and/or only being enabled for a developer edition) happen because not doing them means leaking open the one last (huge) hole malware can infect computers through Modern operating systems have a concept of users, groups of users and dedicating one of these to the role of administrator. I see no problem in not enforcing signing rule for the extensions installed by administrator (at system-wide locations, not user profile) - they are read only for the rest of the users anyway, so they couldn't be installed by drive-by malware. Power users are happy, naive users are protected. If there is a malware that looks like installed by administrator, you have much bigger problems anyway. That malware could patch the firefox binary in the same way as it could deploy the extension, so you gained exactly nothing. But the current situation just makes power users unhappy. This policy killed some extensions that were shipped by Linux distributions.
- lima 10y ago> But the current situation just makes power users unhappy. This policy killed some extensions that were shipped by Linux distributions. I though this change was only about Windows? Chrome on Linux lets me load unsigned extensions just fine.
- vetinari 10y agoSorry, I don't know about Chrome, I was talking about Firefox. AFAIK only Firefox extensions were shipped by distributions.
- johnny22 10y agoFedora uses a patch to allow system installed addons.
- Karunamon 10y agoAny random program running as user X, if malicious, can do far worse things to the user than install plugins into the browser. Apparently the major browser vendors' solution to the problem of things running as users breaking the browser is to remove the ability for users to do things. This is a bogus solution. See: Firefox's chrome-ification of the plugin system.