News for hackers. Stuff that matters.
Re:The Browser Is the Worst Sandbox Ever Designed by btrask on Friday July 15, 2016 @04:03AM (#12099509)
See the later quote:

> (It should also be possible to block or control access to each of these.)

The good news is that the capabilities of the sandbox don't need to be every-expanding, the way browsers have been. The sandbox should support everything the hardware can do, and then there are policy decisions about what capabilities web pages actually get.

Re:The Browser Is the Worst Sandbox Ever Designed by jkot on Friday July 15, 2016 @05:35AM (#12099779)
It should also be possible to disable JS. We all know how that worked out.
Re:The Browser Is the Worst Sandbox Ever Designed by btrask on Friday July 15, 2016 @05:50AM (#12099824)
A better analogy is Android permissions. These days you can fake them and apps mostly still work, right?
Re:The Browser Is the Worst Sandbox Ever Designed by jkot on Friday July 15, 2016 @06:45AM (#12100033)
I think security model on Android 6 is now different. You can grant permission to use camera for 10 minutes etc...
Re:The Browser Is the Worst Sandbox Ever Designed by coldcode on Friday July 15, 2016 @10:00AM (#12100971)
> The sandbox should support everything the hardware can do

Until you can emulate a hardware GPU in software at the same performance point, your sandbox is unusable. The web is more than text.

Re:The Browser Is the Worst Sandbox Ever Designed by TeMPOraL on Friday July 15, 2016 @05:56AM (#12099842)
At this point the sandbox is indistinguishable from your OS.
Re:The Browser Is the Worst Sandbox Ever Designed by btrask on Friday July 15, 2016 @07:35AM (#12100253)
The difference is priorities. By separating them, your OS can be fast and featureful, and your sandbox can be secure. Better yet if there are several competing, portable sandboxes, so you can choose the best OS and best sandbox separately.