To view parent comment, click here.
To read all comments associated with this story, please click here.
Speaking from tech support experience, I'd say if a user doesn't know enough to google for that switch, they have no business side-loading. The more checkboxes you give users, the more they will check out of annoyance just to avoid the alert dialogs, and then your security becomes null and void. I'd agree that having this switch is a nice compromise, and it's not as though you have to hack your browser to enable this.
darknexus,
"Speaking from tech support experience, I'd say if a user doesn't know enough to google for that switch, they have no business side-loading. The more checkboxes you give users, the more they will check out of annoyance just to avoid the alert dialogs, and then your security becomes null and void."
The spread of malware happens because users lack the tools to make informed decisions. Often the choice is between "run" and "do not run" and the only information presented is to identity the software. Even knowledgeable users will be at a complete loss to know if something is harmful, so I fully agree that this type of security model is flawed. But I disagree very strongly with the "remedy" of a walled garden (even if more savvy users can disable it). It'd be both more open and more secure to add metadata about what the extension does and then enforce it in a sandbox. Given the right tools & information, users may be even more secure than simply trusting everything in google's repository.





Member since:
2011-01-28
jasutton,
Yea, it's better than apple's control. But google is weaving precariously on the line between open and closed. I am extremely disappointed they're using a "security" excuse to justify new restrictions, which users won't know how to bypass. A better approach would have been to give users better tools to view/limit what extensions can do and just set the defaults to restrictive.