News for hackers. Stuff that matters.
Re: Facebook Timeline Remover: Works, but Malicious by tptacek on Thursday September 06, 2012 @03:39PM (#4485813)
You're obviously right (by approximately a factor of 50) but let me add:

There is a way to make app review "for safety" scale at this price point: be ultra restrictive about what apps are allowed to do, and review them not as much for security as for compliance to API guidelines.

•Cough•.

Re: Facebook Timeline Remover: Works, but Malicious by saurik on Thursday September 06, 2012 @06:34PM (#4486647)
I would love to hear what restrictions you think you can place on a Turing complete brower extension (a model that already has tons of permissions that apparently aren't enough) would let you know that a sufficiently large subset are sufficiently safe to allow $5/app to be enough to subsidize screening the rest.

In this case, this is a browser extension, and the goal is to edit the page: there are tons of such extensions; while a couple of these had obvious "talks to the wrong server" problems, various of them were correctly only editing pages on Facebook, but were doing so maliciously.

The price point we are talking about here is simply so low: $5 is only going to purchase 40 minutes of a minimum wage employee... we aren't even talking a junior supervisor at a fast food restaurant, we are talking about the entry-level "try to get the orders in the computer right" position.

At these prices, even just reading the description and figuring out "oh, this should only be able to edit pages on this one website" is already going to be expensive. Figuring out "should only be using DOM to remove nodes and not add script elements" is impossible.

Re: Facebook Timeline Remover: Works, but Malicious by tptacek on Thursday September 06, 2012 @08:32PM (#4487101)
Honestly, I was just making a snarky point about the iOS App Store.
Re: Facebook Timeline Remover: Works, but Malicious by jaredsohn on Thursday September 06, 2012 @03:49PM (#4485862)
>be ultra restrictive about what apps are allowed to do

Chrome does this on some level via host permissions (http://developer.chrome.com/extensions/manifest.html#permiss...) and a content security policy (http://developer.chrome.com/extensions/contentSecurityPolicy...) and is setting a more strict default security as manifest v2 gets phased in.