4 ms·
There will be ways to bypass those checks. The easiest is to wait a week after installation before doing anything bad. Or extension could download and execute c
by codedokode 10y ago
There will be ways to bypass those checks. The easiest is to wait a week after installation before doing anything bad. Or extension could download and execute code from remote server that would serve one version of code for users from Mountain View and another version to everyone else. Or the code could check whether it is run on a real device.
- nitrogen 10y agoThis is where the classification heuristics and fine-grained permissions come in. Code that does anything conditioned on dates is higher risk. Code that uses location services is higher risk. Also, many of these checks can be done by the browser in situ, so an extension that suddenly changes its behavior can be flagged for review. And pre-release malware scans can be run on banks of actual hardware that simulates different dates and locations. Sure, there will be an arms race, but that's better than an anarchical free for all.